HTTP 504 Gateway Timeout — Upstream Server Slow
Critical5xx server error
Overview
HTTP 504 Gateway Timeout means the gateway did not receive a timely response from the upstream server.
Key Details
- Status: 504 Gateway Timeout
- Category: 5xx Server Error
- Upstream server did not respond in time
- Proxy/gateway gave up waiting
Common Causes
- Backend server is too slow to respond
- Database query taking too long
- Upstream server is overloaded
- Network issues between proxy and backend
Steps
- 1Wait and retry — the backend may be temporarily overloaded
- 2Check backend server performance
- 3Optimize slow database queries
- 4Increase proxy timeout settings if appropriate
Tags
http-status5xx-server-errorhttp-504httpstatus-code
More in 5xx Server Error
http-500-internal-server-errorHTTP 500 Internal Server Error — What It Means & How to Fix It
Criticalhttp-501-not-implementedHTTP 501 Not Implemented — What It Means & How to Fix It
Criticalhttp-502-bad-gatewayHTTP 502 Bad Gateway — What It Means & How to Fix It
Criticalhttp-503-service-unavailableHTTP 503 Service Unavailable — What It Means & How to Fix It
Criticalhttp-504-gateway-timeoutHTTP 504 Gateway Timeout — What It Means & How to Fix It
Criticalhttp-505-http-version-not-supportedHTTP 505 HTTP Version Not Supported — What It Means & How to Fix It
CriticalFrequently Asked Questions
504 is gateway-to-upstream timeout. 408 is client-to-server timeout.