Fallback — UptimeRobot fetch: timeout after 5s. External monitor is temporarily not responding; showing an internal self-report instead. Figures may lag and come from a single region.
All systems operational
Uptime · 24h
100%
1994 samples total
Uptime · 7d
100%
1994 samples total
Last incident
None
in the last 7 days
Last self-report check: 4m ago — HTTP 200 in 87ms
How this page works
Primary source is UptimeRobot: an external HTTP probe of www.freightutils.com/ every 5 minutes from multiple regions. That covers end-to-end path (DNS → CDN → edge → serverless → data) and is independent of our own infrastructure.
A fallback internal self-report (/api/cron/status-ping) runs every 5 minutes and writes to Vercel KV with 30-day retention. It only renders if UptimeRobot's API is unreachable — the banner names the concrete reason so regressions aren't opaque.
Page cache is 60 seconds.
Something looks wrong?
If an endpoint is returning unexpected errors or stale data and the page up here says everything's fine, email contact@freightutils.com with the request URL and a timestamp. That's the fastest path to getting the monitor fixed as well.