Uptime Monitor Shows Incorrect Status
Last updated 13 days ago
How a check works
Every 5 minutes, the monitor sends a HEAD request to your monitor URL. If that gets a 403 or 405, it tries once more with GET. A check is up when the response has a 2xx or 3xx status code. A 4xx or 5xx response, an SSL error, or no response within 10 seconds counts as down.
Common causes
- Redirects: The monitor doesn't follow redirects, and any 3xx counts as up, even if the page it redirects to is down. Use the final destination URL.
- Firewall or bot protection: Your server, firewall or CDN may block the checker. Allow requests with the User-Agent
StatusForge-Uptime/1.0 (+https://www.statusforge.net). - SSL certificate issues: An expired or invalid certificate makes checks fail. Renew your certificate.
- Rate limiting: If your service rate-limits requests, the 5-minute checks might trigger it.
- Slow responses: Anything slower than 10 seconds counts as down.
Status doesn't match the uptime bar
The uptime bar shows the share of checks that passed each day (UTC). The status next to the service changes less often:
- After three failed checks in a row, about 10 to 15 minutes, the monitor sets the service to Major Outage. It also opens an incident titled
Automated: <service name> is downand emails your subscribers and the account owner. - When a check passes again, the monitor resolves that incident and sets the service back to Operational.
A single failed check lowers that day's bar but doesn't change the status.
Service never goes down, or stays down
- New monitor URL: If a URL has never passed a check, the monitor never opens an outage incident for it. Make sure the URL is right.
- Already in Major Outage: If you set the service to Major Outage yourself, the monitor doesn't open an incident for it.
- Stuck in Major Outage: The monitor only resets services through its own
Automated:incident. If you or a manual incident changed the status, resolve that incident or change the status yourself.
Check frequency
Monitors run every 5 minutes. The public status page is cached for up to 30 seconds, so changes can take a moment to show.
