536 HTTP Response Timeout

The HTTP 536 HTTP Response Timeout status code is an unofficial server error specific to Edgio (formerly Layer0). The Edgio platform returns this code when the origin server accepts a TCP connection but does not deliver an HTTP response within the allowed timeout window.

Table of Contents

Usage

Edgio enforces a response timeout on upstream connections. After establishing a TCP connection (and completing TLS negotiation when applicable), the platform waits for the origin to begin sending an HTTP response. If the origin remains silent past the timeout threshold, Edgio terminates the connection and returns a 536 to the client.

The 536 differs from 531 in a critical way: a 531 means no TCP connection was established, while a 536 means the connection succeeded but the origin did not respond in time.

Common causes include:

  • Long-running server-side operations such as heavy database queries, report generation, or large data processing tasks.
  • The origin application is deadlocked, stuck in an infinite loop, or waiting on an unresponsive downstream dependency.
  • Resource exhaustion on the origin server (high CPU, memory pressure, or I/O contention) preventing timely response generation.
  • Network congestion between the Edgio POP and the origin slowing packet delivery below the timeout threshold.

Note

Edgio also returns 534 when a serverless function fails to produce a response at all, and returns a separate code (539 Serverless Timeout) when the project's own serverless code exceeds its execution time limit. A 536 specifically targets origin-side HTTP response delays.

SEO impact

Search engines treat Edgio 536 responses as server errors. Persistent response timeouts reduce crawl rate and prevent indexing of affected URLs. Speeding up the origin response restores normal crawling.

Example

A client requests a resource through Edgio. The origin connects but does not respond within the timeout window. Edgio returns a 536.

Request

GET /reports/quarterly HTTP/1.1
Host: www.example.re
Accept: application/json

Response

HTTP/1.1 536 HTTP Response Timeout
Date: Mon, 02 Mar 2026 14:35:00 GMT
Content-Type: text/html
Server: ECAcc (dce/26A1)

<html>
<head><title>536 Response Timeout</title></head>
<body>
<h1>536 HTTP Response Timeout</h1>
<p>The origin server did not respond in time</p>
</body>
</html>

How to fix

Profile the slow origin endpoint. Identify long-running database queries, blocking API calls, or CPU-intensive processing consuming the full timeout window. Optimize these operations to return a response faster.

Move long-running tasks to a background worker (a queue system like Celery, Sidekiq, or BullMQ). Return an immediate 202 Accepted response with a task ID, and have the client poll a status endpoint for the result.

Add timeout handling to downstream dependencies called by the origin. If the origin waits on a third-party API or database stalling, set explicit timeouts on those calls and return a partial or error response rather than blocking indefinitely.

Monitor origin server resource usage. High CPU load, memory pressure, or disk I/O contention delay response generation. Scale the origin horizontally or optimize resource-intensive operations to reduce response latency.

Allowlist Edgio IP addresses on the origin's firewall and hosting provider. Some providers throttle or deprioritize traffic from CDN networks, artificially inflating response times. Confirm Edgio traffic receives the same priority as direct client traffic.

Takeaway

The 536 HTTP Response Timeout is an Edgio-specific status code generated when the origin server establishes a connection but fails to deliver an HTTP response within the platform's timeout window, most commonly caused by slow origin-side processing or resource exhaustion.

See also

Last updated: March 6, 2026