Home > Error > 502
502 Bad Gateway
The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
This typically means the upstream service is unavailable, restarting, or returning malformed responses. The edge proxy could not parse what it received and gave up.
Request flow
client
→
edge
⊘
upstream
Timing breakdown
| +0.00s | request received at edge | OK |
| +0.02s | upstream selected | api-cluster-3 |
| +0.04s | connection established | — |
| +0.18s | upstream sent partial response | truncated |
| +0.42s | upstream closed connection mid-stream | reset |
| +1.20s | retries exhausted (3/3) | give up |
What this usually means
- The upstream service may be temporarily down or restarting
- A misconfigured proxy header caused the upstream to reject the request
- The connection between edge and upstream timed out unexpectedly
- An upstream code deploy is in progress and brief blips are expected
- The upstream returned an HTTP envelope the proxy could not parse
Diagnostic snapshot
request_id = req_8a72-0021-bb91
edge_node = edge-04 (ams)
upstream = api-cluster-3 (10.42.0.7:8080)
attempts = 3 / 3
status = 502 Bad Gateway
last_ok = 14:08:21 UTC
Request information
Status:502 Bad Gateway
Edge:edge-04.eu
Upstream:api-cluster-3
Retry attempts:3/3 — failed
Request ID:req_8a72-0021-bb91
Time:Tue, 19 May 2026 14:18:02 GMT
Tip: Most 502 errors clear within 30-60 seconds. If you are using an API client, implement exponential backoff and the issue will usually resolve on the next attempt.
Please retry the request in a few seconds. If it persists, contact the operator with the request ID above.
nginx/1.24.0 — running at edge-04.eu — IPv4/IPv6