HTTP troubleshooting
503 Service Unavailable
The service is temporarily unable to handle requests because of overload, outage, or maintenance.
What 503 means for a monitor
Statixoup records an incident when 503 does not match the monitor's expected status code. Confirm the response before changing monitor rules.
Troubleshooting checklist
- 1.
Check 1
Confirm whether maintenance mode is intentional.
- 2.
Check 2
Check capacity and healthy instances.
- 3.
Check 3
Review dependency and connection-pool availability.
- 4.
Check 4
Restore healthy instances before changing expectations.
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.