System Status
Live public telemetry for route freshness, browser reachability, and ingestion drift.
Reading Status
The page is a public reliability view, not an operator console. It favors signals that affect readers and API consumers: freshness, public probes, incident runway, and whether cache-backed data is still inside its expected age window.
For API integrations, combine this page with response headers such as X-Data-Age, Warning, Retry-After, and the endpoint-specific cache profile in the API reference.
System Status FAQ
What does System Status monitor?
System Status monitors public Pharos health, cache freshness, endpoint probes, circuit-breaker state, and recent status transitions. It is the public view of whether the dashboard and data API are serving fresh enough information.
Why can status differ from a single endpoint response?
The status page blends cache freshness, Worker health, browser reachability probes, and incident history. A single endpoint can be slow or stale while the overall system remains available, or the aggregate can degrade when several public data lanes drift together.
How often should I refresh the status page?
Manual refresh is enough for most users. Public status data is cached on short intervals, and external integrations should rely on API response headers, Retry-After, and endpoint-specific polling guidance instead of aggressively refreshing this page.