HTTP troubleshooting
408 Request Timeout
The server did not receive or finish the request in the allowed time. 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 408 means for a monitor
Statixoup records an incident when 408 does not match the monitor's expected status code. Confirm the response before changing monitor rules.
Troubleshooting checklist
- 1.
Check 1
Check server load and request logs.
- 2.
Check 2
Review slow dependencies and database queries.
- 3.
Check 3
Confirm the monitor timeout is appropriate.
- 4.
Check 4
Prefer a lightweight health endpoint.
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.