BrokenAI

An independent reliability ledger for the major model providers. Built because their status pages weren't enough.

Pages
ScoreboardAbout & scoringSLA compliance30-day report
Providers
ClaudeOpenAIMistralGrokDeepSeekKimiCohere
Integrate
Status badgellms.txtSitemaprobots.txt
© 2026 BrokenAI · Independent · Not affiliated with any provider · See a number that looks wrong? @threatner_v2.1.0
BrokenAI
30-day reportSLAEmbedAbout
30-day reliability report

How did the major AI providers behave this month?

Numbers come straight from each provider's official Statuspage, recomputed on every visit. The greener cell on a row is the provider that came out ahead; ties get no tint. Hover a row for the metric's definition.

Metric
Claude
OpenAI
Mistral
Grok
DeepSeek
Kimi
Cohere
  1. Reliability
    1. Composite reliability score
      36.3
      53.6
      100.0
      97.1
      100.0
      85.5
      100.0
    2. Uptime
      92.467%
      99.340%
      100.000%
      100.000%
      100.000%
      99.868%
      100.000%
    3. Total downtime
      54h 14m
      4h 45m
      0m
      0m
      0m
      57m
      0m
    4. Active right now
      1
      0
      0
      0
      0
      0
      0
  2. Incidents
    1. Total incidents
      11
      46
      0
      3
      0
      9
      0
    2. Major + critical
      8
      7
      0
      0
      0
      9
      0
    3. Minor
      1
      30
      0
      3
      0
      0
      0
    4. Longest single incident
      134h 12m
      70h 39m
      —
      28m
      —
      ▲27m
      —
    5. Longest clean streak
      7d 11hSep 22–29
      4d 12hSep 17–22
      30dSep 13 – Oct 13
      14d 17hSep 22 – Oct 6
      30dSep 13 – Oct 13
      9d 12hSep 19–28
      30dSep 13 – Oct 13
  3. Time to fix
    1. Median fix time
      1h 13m
      1h 5m
      —
      26m
      —
      ▲2m
      —
    2. On a bad day
      6h 16m
      9h 23m
      —
      28m
      —
      ▲27m
      —
    3. Closed vs still open
      10 closed1 still open
      46 closedall wrapped up
      0 closedall wrapped up
      3 closedall wrapped up
      0 closedall wrapped up
      9 closedall wrapped up
      0 closedall wrapped up
  4. Patterns
    1. What broke most
      Claude Cowork6 incidents · 100h 47m attributed
      Conversations17 incidents · 85h 44m attributed
      —
      Grok (Web)2 incidents · 32m attributed
      —
      Search7 incidents · 29m attributed
      —
    2. Most common failure type
      Elevated errors7 of 11
      Elevated errors22 of 46
      —
      Other2 of 3
      —
      Other9 of 9
      —
    3. Busiest day of week
      Tuesday4 incidents on this day
      Tuesday11 incidents on this day
      Too few to call
      Tuesday2 incidents on this day
      Too few to call
      Friday4 incidents on this day
      Too few to call
    4. Busiest hour of day
      1 PM UTC2 incidents started here
      4 PM UTC5 incidents started here
      Too few to call
      12 AM UTC1 incident started here
      Too few to call
      10 PM UTC3 incidents started here
      Too few to call
What this report doesn't cover
  • No synthetic API probing — we only see what each provider publishes on their Statuspage. Quietly degraded responses that never get acknowledged on the status page are invisible here.
  • No regional breakdown — Statuspage feeds don't reliably expose region-level impact, so a US-only outage and a global one count the same.
  • No request-volume weighting — “1 incident” means one acknowledged incident, regardless of how many calls it actually affected.