System Status
Current state of Pharos pages, the public API and each data feed, with 30 days of incident history.
System Status FAQ
What does System Status monitor?
System Status shows each public Pharos component, such as the website and API, stablecoin prices, charts, Safety Scores, risk signals and event feeds, with its current state and 30 days of history. A day is coloured only when a problem lasted an hour or more that day; shorter blips are listed in the day's tooltip. Notices, such as one input a data feed could not refresh, leave a component operational. Safety Scores are graded by the age of the last accepted scores; a held publication is shown as a notice while those scores stay inside their freshness budget. History before a component began being monitored is unknown, not operational.
Why can status differ from a single endpoint response?
Each component is graded against its own freshness budget: Delayed past the first budget, Degraded past the stale limit, and Outage only once the data has stayed stale for a further grace period. A single endpoint can be slow or stale while its component stays inside budget. The probes and cache tables under For integrators show the raw readings.
How often does the status page update?
The page re-reads public health on the same schedule as the underlying check, so a manual refresh is rarely needed. External integrations should rely on API response headers, Retry-After, and endpoint-specific polling guidance instead of polling this page.