Status
Ninety days of measured availability for the website, the app and the API, each one's state right now, and any incident we have marked. The same checks that wake us up.
One moment.
This page reads its numbers from the API. If this website answers but the API does not, the API is what is down, and that is the outage. The API serves its own copy of this page, without any script, which is the place to look next.
Incidents
An incident is a sentence we write while something is wrong, with when it started and when it ended. Open ones first, then those resolved in the last 90 days.
Loading.
How availability is measured
Every five minutes a checker outside Beacon's own hosting asks the website and the app's sign-in page for a page (twice, 15 seconds apart) and the API's readiness check, which runs a database query (three times over about 45 seconds), before counting a failure. A day's availability is the share of those checks that got a good answer; the 90-day figure is the same share over all of that period's checks. When the checker cannot record a result, the five-minute slots until its next recorded check count against the API. Days are UTC.
The District plan carries a written 99.9% monthly availability commitment measured at the API, with service credits; the terms and the security whitepaper say how it is defined. A bar here is one UTC day: green at 99.9% or better, amber below that, red below 95%, grey with no checks recorded. Hover or tap a bar for the day's figure.