HTTP troubleshooting
429 Too Many Requests
A rate limiter rejected the monitor because too many requests reached the service.
What 429 means for a monitor
Statixoup records an incident when 429 does not match the monitor's expected status code. Confirm the response before changing monitor rules.
Troubleshooting checklist
- 1.
Check 1
Inspect rate-limit headers and edge logs.
- 2.
Check 2
Allow expected monitoring traffic where safe.
- 3.
Check 3
Review check interval and other callers.
- 4.
Check 4
Keep abuse protection while defining a health-check policy.
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.