What Is HTTP 504 Gateway Timeout?

HTTP 504 Gateway Timeout explained, and what it means when you see it in CI/CD and deployments.

HTTP 504 means a gateway or proxy did not get a timely response from an upstream server.

What it means

A 504 is transient and network-related: a load balancer or reverse proxy timed out waiting for the backend. It often clears on retry.

When you see it in CI/CD

CI deploy checks and API calls hit 504 when a backend is slow or scaling. Retry with backoff. Persistent 504s point to a slow upstream that needs tuning.

Key takeaways

• 504 means an upstream timeout.
• Usually transient.
• Retry with backoff; persistent 504s need tuning.

Related guides