What Does HTTP Status 504 Mean? (Gateway Timeout)
What HTTP 504 (Gateway Timeout) Means In Plain English
A 504 status (Gateway Timeout) means a gateway/proxy timed out waiting for an upstream server response.
If you want the broader context across all status code families, use the full HTTP Status Codes Guide (2xx, 3xx, 4xx, 5xx).
Quick Navigation
- What HTTP 504 (Gateway Timeout) Means In Plain English
- How to Read HTTP 504 in WebsiteDown Results
- Most Common Root Causes
- What to Do Next
- What to Avoid During Triage
- Real-World Examples
- HTTP 504 FAQ
How to Read HTTP 504 in WebsiteDown Results
If regions return 504, the request path is reachable but upstream response time exceeded timeout budgets. Focus on latency and queue pressure across tiers.
If you see this code only in one region, compare with official provider status and retest from another network. Mixed regional results often indicate routing, policy, or edge differences rather than full global outages.
For deeper triage, compare this with the HTTP 502 guide, HTTP 408 guide, and the API downtime investigation playbook.
Most Common Root Causes
- Slow upstream services under load.
- Database or dependency latency cascades.
- Timeout settings too strict for current workload.
- Regional routing path degradation increasing round-trip latency.
What to Do Next
- Correlate 504 spikes with p95/p99 latency and queue depth.
- Find first-hop timeout boundary (CDN, LB, gateway, service).
- Reduce heavy queries/calls and prioritize essential endpoints.
- Tune timeout and retry settings with strict caps and jitter.
What to Avoid During Triage
- Do not increase retries without limits; this often worsens congestion.
- Do not assume origin is down when it is actually slow and overloaded.
Real-World Examples
- Example: API gateway waits 30s on upstream and returns 504.
- Example: one region shows 504 due to congested edge-to-origin path.