HTTP troubleshooting
302 Found
The resource is temporarily at a different URL; clients may follow the redirect but the original URL remains valid. 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 302 means for a monitor
Statixoup records an incident when 302 does not match the monitor's expected status code. Confirm the response before changing monitor rules.
Troubleshooting checklist
- 1.
Check 1
Confirm whether the redirect is temporary and expected.
- 2.
Check 2
If temporary, keep monitoring the original URL and ensure the redirect target is healthy.
- 3.
Check 3
Use the final response location only if the service owner confirms permanence.
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.