Status
This page says what is running and what is not. It carries no uptime percentage, because a figure nobody computes is a figure that is wrong the day after it is written.
The site
This site is served from a static build with no database behind it, so the pages you read do not go down with anything else. If something we owe you is late, the answer comes from us by email rather than from a dashboard.
What runs on a timer
Three agents run on their own timers and hold the claims desk. The deadline watch walks every open window every thirty minutes and escalates at three days, one day and two hours left; inside the last window it cannot be quieted and it does not clear until the item is filed. The chase schedule runs every four hours and works out which manager questionnaires are overdue. The outcomes job runs once a day and records determinations and protest outcomes, writing every denial into the corpus with the reason the state gave.
A job that fails three times in a row carrying the same error is taken out of service rather than left retrying, which is why the deadline watch stamps a heartbeat on every successful tick and the other two jobs refuse to do anything until they have read it. A heartbeat older than three hours raises a page from a different job on a different timer.
None of those jobs files anything to a state and none of them mails an employer. The approval step is yours, and the code fails closed on it in four separate ways.
Jurisdictions sourced
49 states have a rules row today, and 41 of those carry a charge-protest window read from that state’s own statute, with the citation on the page. A state appears on this site the moment its row lands and never before, so the board in the footer is the current answer rather than a roadmap. Rows are still being added, and so are the windows on rows that already exist.
The gap between those two figures is printed rather than hidden: the board marks a state we have not sourced a window for with a question mark, and a state whose own law provides no charge protest at all with an em dash. Those are different facts and the second one is sourced, which makes it the answer most likely to be quietly wrong elsewhere.
Incidents
There have been none to report. If an incident ever affected a filing deadline, you would hear it from us directly, in time to act on the window that was still open, and it would be recorded here afterwards. Reporting a vulnerability is a different path and it is on the security page.