How AIDownCheck works
Most outage trackers answer one question: is it down? AIDownCheck answers four more: why, who else is affected, what can I use instead, and how sure are we.
Two independent signals
For each service we combine two sources that fail in different ways:
- Official status pages. We read the vendor's own status feed (OpenAI, Anthropic, Cursor, ElevenLabs and others publish a public status API). It's authoritative — but often lags the first minutes of an incident.
- Independent checks. We run our own reachability check from our servers. It catches problems before a status page updates — but a single vantage point can be noisy, so we treat it conservatively.
The confidence engine
We never claim certainty we don't have. Every verdict carries a confidence level and shows the evidence behind it:
- High — both sources agree (e.g. the vendor confirmed an incident, or both say healthy).
- Medium— sources conflict, like an official page still showing green while our checks fail. That's the early-warning window.
- Low / Unconfirmed — we only have one usable signal, so we say so plainly.
Dependency intelligence
Modern AI tools are built on a handful of model providers. Cursor and Bolt run on Anthropic's Claude; many apps run on OpenAI. When a provider has an incident, the products built on it often degrade too — frequently before their own status pages admit anything. We map those public relationships so you can see the blast radius, always framed as likely impact, never confirmed causation.
Honest by default
We don't invent uptime percentages or outage durations. Historical statistics appear only once our database has accumulated real measurements — and until then we tell you exactly what we do and don't know. AIDownCheck is independent and not affiliated with any AI provider.