Status.

Whether the panel is healthy right now, from probes we run on a schedule — and deliberately nothing about how much anyone is using it.

Loading components…

What this page does not show

No traffic. No request counts, no customer counts, no volume of any kind, anywhere on this page or in the endpoint behind it.

That is possible because the signal here is synthetic. We call each engine on a schedule to see whether it answers, and those probes run whether or not a single person used Quorum today. So the health of the panel can be reported honestly without the board doubling as a traffic counter. Engine counts do appear — how many models are in rotation is a statement about capability, not about how busy we are.

How each light is decided

StateMeans
Operational Every engine in rotation for that provider passed its most recent probe, and that probe is recent.
Degraded Some engines are failing and the panel is serving from the rest — or everything is passing but the last probe is more than 48 hours old.
Down No engine in rotation for that provider passed its last probe.
Unknown We could not read the signal. Shown as unknown rather than assumed good.

Engines already marked degraded or disabled are excluded, because they have been taken out of rotation and are not serving anything. Counting them would paint every provider red while the panel runs perfectly well on the rest.

Why “stale” can turn a green light amber

The recovery job probes broken engines constantly, because its whole purpose is to bring them back. It re-probes healthy ones far less often. So a passing result can be a day or two old, and presenting that as live would be a small lie told continuously. Instead, every component carries the time it was last verified, and anything older than 48 hours is downgraded to amber no matter how good the result was.

What is not covered yet

This board watches the panel engines and the scheduled jobs. It does not yet carry the HTTP surface itself — a synthetic call against /v1/chat/completions and /v1/estimate on a schedule — and it has no incident history. Both are worth building; neither exists, and the page says so rather than implying broader coverage than it has.

If something looks wrong here and you are affected, get in touch — a person reads it.