HTTP troubleshooting
402 Payment Required
Reserved for future use; some services return this to indicate billing or quota issues. In simple terms, this guide helps you understand why the response may make a monitor appear unhealthy and what to check before changing your monitor settings.
What 402 means for a monitor
Statixoup records an incident when 402 does not match the monitor's expected status code. Confirm the response before changing monitor rules.
Troubleshooting checklist
- 1.
Check 1
Confirm whether the service uses 402 for billing-related access control.
- 2.
Check 2
Review your account or API billing settings.
- 3.
Check 3
Contact the API provider or service owner if you believe access should be allowed.
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.