| Previous | Next |
| HTTP_STATUS_SERVICE_UNAVAIL | HTTP_STATUS_VERSION_NOT_SUPPORTED |
HTTP_STATUS_GATEWAY_TIMEOUT
The timeout occurs while the gateway is waiting for a dependency needed to complete the request. It is distinct from 408, where the server waited too long for the client request.
Measure each hop: DNS, connect, TLS, request upload, application execution, and upstream response. Align timeout settings deliberately; raising only the proxy timeout can hide a blocked or overloaded backend.
Operational meaning of HTTP 504 for HTTP_STATUS_GATEWAY_TIMEOUT
HTTP 504 (HTTP_STATUS_GATEWAY_TIMEOUT) is a server-error response. AllStat records its meaning as “504 Gateway Timeout”. For HTTP_STATUS_GATEWAY_TIMEOUT, interpret it with the request method, selected representation, response headers, and the specification or product that defines the code; the number alone does not prove that application work completed.
Client and server handling for HTTP_STATUS_GATEWAY_TIMEOUT
- Correlate HTTP_STATUS_GATEWAY_TIMEOUT with origin, gateway, load-balancer, and dependency logs to locate which hop generated it.
- For HTTP_STATUS_GATEWAY_TIMEOUT, record request and trace identifiers, upstream timing, retry count, and the health of the selected backend.
- For HTTP_STATUS_GATEWAY_TIMEOUT, use bounded retries with backoff only for idempotent work and only when the service policy permits them.
For telemetry, record HTTP 504, method, authority, route template rather than secrets, response headers relevant to caching or retry, latency, upstream identity, and whether the response originated at the application or an intermediary.
Looking for a different code? Search another status or error code.