Provider status pages & polling guides
All 9 monitored providers with their snapshot status, plus the 2 we can't probe. Each guide documents the status-API format that actually works — endpoint, response shape, and the redirect gotchas we hit verifying it.
Snapshot: Aug 31, 2026 9:30 AM ET · Statuses shown are build-time snapshots — they refresh on each site rebuild. Live auto-refresh ships post-launch.
All Systems Operational
Components: 34/34 · polling guide →
All Systems Operational
Components: 6/6 · polling guide →
All Systems Operational
Components: 20/20 · polling guide →
All Systems Operational
Components: 30/30 · polling guide →
2 active incident(s): Vibe Code Web is failing to provision a sandbox in new sessions (157 incidents in page history)
Components: no component feed (incident history only) · polling guide →
Page status: UP
Components: 3/3 · polling guide →
Aggregate state: operational
Components: 22/22 · polling guide →
All Systems Operational
Components: 15/15 · polling guide →
0 ongoing incidents in feed; 0 affecting Vertex/AI products
Components: no component feed (incident list only) · polling guide →
Unmonitorable from our probe
Unmonitorable from our probe — check directly: https://status.x.ai
Probe error: HTTP 403 (Cloudflare challenge; blocks non-browser clients)
Unmonitorable from our probe — check directly: https://status.deepseek.com
Probe error: TLS connection reset by peer (host unreachable from this network)
How this data is gathered, and why an absent probe is not an "operational" badge: methodology.