Uptime Monitor Shows Incorrect Status
Last updated 22 hours ago
Common causes
- Monitor URL returns redirects: The monitor follows redirects, but some redirect chains may cause issues. Use the final destination URL instead.
- Firewall blocking: Your service might block requests from our monitoring IPs. Ensure
statusforge.netis whitelisted. - SSL certificate issues: Expired or invalid SSL certificates cause check failures. Renew your certificate.
- Rate limiting: If your service rate-limits requests, the 5-minute check interval might trigger it.
What counts as "up"
A successful check is any HTTP response with a 2xx or 3xx status code. 4xx and 5xx responses count as downtime.
Check frequency
Monitors run every 5 minutes. There may be a slight delay between a real outage and the status page updating.
