Skip to content
Free tool

504 Gateway Timeout

The proxy waited for the application and it didn't answer in time.

Why it happens

  • A slow database query or an external API the page waits on.
  • The application is stuck or overloaded.
  • A proxy timeout set lower than the page needs.

What to do

  • Find the slow part: database, external calls, or CPU. Raise the proxy timeout only as a last resort.

In monitoring

Counts as down. If two checks in a row see it, you're alerted with this code as the cause.

Catch the next 504 before a customer does.

heyUptime checks your site every 30 seconds, confirms a failure before alerting, and tells you the code and the likely reason.

Start watching free

All status codes · Not sure what your site returns right now? Check it.

Next time, be the first to know.

Let someone else watch the shop. If anything breaks, you will hear it from us, not from a customer.

Start your 14-day free trial No credit card needed