HTTP troubleshooting
504 Gateway Timeout
A gateway did not receive an upstream response before its timeout expired.
What 504 means for a monitor
Statixoup records an incident when 504 does not match the monitor's expected status code. Confirm the response before changing monitor rules.
Troubleshooting checklist
- 1.
Check 1
Find the slow upstream in timing logs.
- 2.
Check 2
Check database and external API calls.
- 3.
Check 3
Compare gateway, app, and monitor timeouts.
- 4.
Check 4
Fix the slow dependency and confirm recovery.
After the service is fixed
- Confirm the URL returns the expected status without a browser session.
- Review response-time and incident history for the recovery.
- Change Expected status code only when the different response is intentional.
Avoid hiding a real outage
Changing the expected code can make an unhealthy response appear operational. Fix the service first whenever the response is unexpected.