Status
System status
Live checks of the AZRouter website and API. The page refreshes every 30 seconds and marks any check it can't confirm as unknown.
Checking status…
Reading the latest checks…
Monitoring methodology
- The website (azrouter.dev must answer 200), the www redirect (any redirect passes) and API readiness (api.azrouter.dev/health must report ok) are checked every minute. An answer slower than 3 seconds counts as degraded.
- Per-model checks are not running yet; models appear here once they do.
- “No data” and “Status unavailable” mean we can’t confirm, never that everything is fine: the monitor hasn’t reported for 2 minutes, a check is older than 2 minutes, the check itself was refused, or this page couldn’t load an answer less than a minute old.
- Each bar is one UTC day of checks that were actually recorded: green when at least 90% of that day’s checks ran and all passed, amber when one was slow, red when one failed, grey when there are too few checks or none. Days before monitoring began are grey. Uptime is the share of recorded checks that got an answer over the last 90 days; minutes without a check don’t count either way.
- All checks run from one location, our own server. This page and its data are served by Cloudflare, so they stay up when that server is down.
- Times show in your time zone; hover one for UTC. Hover a bar for its date.