Checks run live from your browser against production — no synthetic status theater. REST checks the public read surface; the gateway check expects its auth wall (a 403 without a key means it is alive); MCP performs a real tools/list; freshness reads the newest finished match and the live board's last publish.
These browser checks only run when you open this page. Between visits there is one scheduled monitor: since 6 August 2026 a smoke check runs every six hours, performs the same reads a first-time visitor's browser performs with the published anon key, and files a tracking issue when they break. It is an alarm, not a meter — it measures neither availability nor latency over time, which is why we still publish no uptime percentage. What is backed up, what else is monitored, and what happens if the operator is unavailable are all stated in the continuity statement.