Which of the 144 SaaS vendors we monitor had the most incidents (last 60 days)
The SaaS and cloud vendors with the most public incidents over the last 60 days, scored from their own status feeds — with the reliability caveats spelled out.
Over the last 60 days, Kraken logged the most public incidents of the 144 SaaS and cloud vendors Ontracko monitors — 48 of them, for 64 hours of impact-weighted downtime. Here's the full picture, drawn entirely from vendors' own public status feeds.
The most incident-prone vendors of the last 60 days
Across the 144 vendors we monitor, these logged the most public incidents:
| # | Vendor | Incidents | Weighted downtime | Score |
|---|---|---|---|---|
| 1 | Kraken | 48 | 64h | 38.5 (F) |
| 2 | Anthropic | 47 | 75h | 21.2 (F) |
| 3 | Twilio | 45 | 59h | 41.8 (F) |
| 4 | Zoom | 40 | 34h | 60.2 (C) |
| 5 | Cloudflare | 39 | 53h | 47.2 (D) |
| 6 | Grafana Cloud | 38 | 207h | 9.7 (F) |
| 7 | GitHub | 37 | 37h | 38.9 (F) |
| 8 | BrowserStack | 36 | 12h | 57 (D) |
| 9 | DocuSign | 35 | 24h | 67.3 (C) |
| 10 | Supabase | 28 | 42h | 52.1 (D) |
Incident count is the raw number of distinct incidents each vendor published on its own status page — a transparent vendor that posts every minor advisory can rank high here even while scoring well overall, which is exactly why our reliability score (last column) caps per-incident duration by severity.
Where the outages were actually severe
Raw incident count doesn't tell you severity. These vendors logged the most critical incidents in the window:
- BrowserStack — 34 critical, 12h weighted downtime (status & history)
- Brex — 8 critical, 17h weighted downtime (status & history)
- GitHub — 8 critical, 37h weighted downtime (status & history)
- Snowflake — 7 critical, 119h weighted downtime (status & history)
- Expensify — 5 critical, 33h weighted downtime (status & history)
The other end: the most reliable vendors right now
For contrast, the highest-scoring vendors this window:
- Amazon Web Services — score 100 (A+), 0 incidents (details)
- Atlassian — score 100 (A+), 0 incidents (details)
- Bugsnag — score 100 (A+), 0 incidents (details)
- Cohere — score 100 (A+), 0 incidents (details)
- Doppler — score 100 (A+), 0 incidents (details)
See the full ranking on the reliability leaderboard.
Methodology & caveats
Every number here comes from each vendor's own public status feed, measured over a 60-day window ending 2026-07-10. "Incidents" counts distinct events the vendor published; "weighted downtime" applies severity weights (full outage 100%, major 75%, minor 25%) and caps each incident's counted duration by severity so a transparent status page isn't penalized. These are public reliability signals, not account-specific SLA measurements — your own impact depends on the regions and services you use. Requested vs. omitted: any claim we couldn't back with this data was left out.
*Ontracko monitors 144 SaaS & cloud vendors' public status feeds and recovers the SLA credits when they miss. Free — 8% only on recovered credits. See live reliability rankings.*
Related reading
How to claim an SLA credit from MongoDB Atlas (99.995% uptime)
MongoDB Atlas commits to 99.995% uptime on M10+ dedicated clusters — about two minutes of allowed downtime a month. Miss it and you're owed 10% to 100% of that cluster's fee, but only if you log a ticket within 24 hours. Here's the credit table and the two-stage claim.
What does a 99.9% SLA actually allow? Uptime, downtime, and your credit
A 99.9% SLA allows about 43 minutes of downtime a month; 99.99% allows about 4. Here's the full uptime-to-downtime cheat sheet, when downtime becomes a breach, and how to calculate the SLA credit you're owed.
How to claim an SLA credit from Microsoft Azure
Azure owes you a service credit when Virtual Machines, SQL Database, App Service and other resources miss their SLA. Here's the exact credit schedule, the deadline, the evidence you need, and how to file the support request.
How to claim an SLA credit from Atlassian (Jira, Confluence, Bitbucket)
Atlassian Premium and Enterprise owe a service credit when Jira, Confluence, or Bitbucket miss their uptime SLA — but you have only until the 15th of the next month to file. Here's the credit schedule and how to claim.
Or browse the SLA glossary and the reliability rankings.
Stop leaving SLA credits on the table
Ontracko monitors your vendors, catches every SLA breach, and drafts the claim. Free — 8% only on recovered credits.
Start monitoring free