500 vs 504: Internal Server Error vs Gateway Timeout
500 and 504 can look similar in logs, but they tell clients, crawlers, and API consumers different things.
| Aspect | HTTP 500 — Internal Server Error | HTTP 504 — Gateway Timeout |
|---|---|---|
| Definition | The server encountered an unexpected condition that prevented it from fulfilling the request. Unlike 4xx errors, this is not a client mistake — it is a server-side failure that needs investigation. | Your reverse proxy (nginx, Cloudflare, etc.) gave up waiting for the origin server to respond within the configured timeout. The origin may be overloaded, slow, or hung. |
| Plain-language summary | An unexpected condition on the server prevented the request from being fulfilled. This is the generic server-side error catch-all. The problem is always on the server, not the client. The request may have been valid; the server simply failed to process it. | A gateway or proxy timed out waiting for a response from an upstream server. The upstream received the request but did not respond within the allowed time window. This is different from 502 (upstream sent a bad response) — 504 means the upstream sent no response at all within the timeout. |
| When to use | Use 500 as the default when no more specific 5xx code applies. Use 502 for gateway/proxy errors from upstream, 503 for deliberate unavailability, 504 for gateway timeouts. Do not use 500 for client errors — those are 4xx. | Gateways and proxies emit 504 automatically. As an application developer, tune upstream timeout configurations and optimize slow processing paths to avoid 504s. Always implement request timeouts on all outbound HTTP calls. |
| Client behavior | May retry after a delay (the server may recover). Automated clients should implement bounded retry with exponential backoff. After a threshold of retries, surface the error to the user or alert. | May retry — the upstream may be temporarily slow. Implement bounded retry with exponential backoff. After repeated 504s, surface the error and alert. |
| Caching behavior | Not cached. | Not cached. |
| SEO / crawler impact | Search crawlers interpret 500 (server-errors) for indexation and link equity accordingly. | Search crawlers interpret 504 (server-errors) for indexation and link equity accordingly. |
| API / backend impact | API clients branching on 500 expect Internal Server Error semantics. | API clients branching on 504 expect Gateway Timeout semantics. |
| Safe to retry? | Yes, with backoff — server may recover | Yes, with backoff — server may recover |
Common real-world scenarios
When you see HTTP 500
500s are the most critical alert trigger in server monitoring. Always alert on 500 rate spikes. Correlate 500s with: recent deployments, upstream dependency health, resource utilization (memory/CPU), and database error rates. A 500 that appears only for specific users or request patterns indicates a bug in request-specific code paths rather than an infrastructure failure.
When you see HTTP 504
In Nginx: "upstream timed out." In Cloudflare: <a href="/guides/cloudflare-524/">Cloudflare error 524</a> (a Cloudflare-specific timeout code). Common causes: database query that ran over the timeout threshold, external API call that was slow or hung, application code in an infinite loop or deadlock, or upstream server under high load and processing slowly.
Decision rule
Use 500 when the response should communicate internal server error behavior; use 504 when gateway timeout is the accurate protocol signal.
A frequent mistake is swapping 500 and 504 for convenience; that causes client retry bugs, incorrect cache signals, and misleading monitoring data.
Use 500 when the correct protocol signal is Internal Server Error. Use 504 when the correct signal is Gateway Timeout. Returning either code for the wrong reason breaks client expectations, cache behavior, and monitoring accuracy.
FAQ
What is the biggest difference between 500 and 504?
500 communicates Internal Server Error, while 504 communicates Gateway Timeout. Choosing the right one keeps clients and intermediaries predictable.
Do 500 and 504 have SEO or caching impact?
Yes. Search engines and caches interpret status classes differently. Use each code according to its semantics to avoid accidental indexing, stale responses, or crawl inefficiency.
Can APIs safely return 500 instead of 504?
Only when it matches contract semantics. API clients often branch logic by exact code, so swapping them can break retries, auth handling, or user-facing errors.
Full guides
HTTP 500 Internal Server Error — full guide · HTTP 500 status reference · HTTP 504 Gateway Timeout — full guide · HTTP 504 status reference · All comparisons