# HTTP/1.1 504 Gateway Timeout
$ upstream did not respond within deadline
▮ Snapshot
upstream: api-cluster (10.42.0.5) deadline: 30s elapsed: 30.0s status: no_response · giving_up retries: 3 of 3 failed request_id: req_42b9-fa07-1c30 trace_id: tr_8c41-1a44 cache: BYPASS edge_node: edge-04 / ams
Hint: Most 504s are transient — the upstream is busy or briefly unreachable. Retrying after a short delay usually succeeds.
▮ Actions