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
Does OpenAI or Anthropic owe you an SLA credit when the API goes down?
OpenAI prints a 99.9% uptime SLA on its Scale Tier and Fast mode pages — for Enterprise customers only — but publishes no credit schedule, no uptime definition and no claim window. Anthropic publishes nothing at all and disclaims uninterrupted service by name. Here is what each one actually owes you.
Why do SLA credit claims get denied? The six exclusions that void a claim
A real outage is not the same thing as claimable downtime. Six exclusion families — plan tier, scheduled maintenance, your architecture, minimum-duration floors, third-party carve-outs and your own configuration — decide whether a vendor pays. Here is how each one works, with the vendors that use it.
DigitalOcean SLA credit: how the 99.99% Droplet guarantee pays out (and how to claim it)
DigitalOcean's CPU Droplet SLA commits to 99.99% monthly uptime per Droplet and pays a 100% service credit below it — no tiers. Here is what counts as downtime, what the credit covers, the two-billing-cycle deadline and the exact email to send.
Does Salesforce pay SLA credits? What its agreement actually commits to
Salesforce publishes no uptime percentage, no credit schedule and no filing window — its agreement promises only commercially reasonable efforts. Here is where your Salesforce SLA actually lives, and what to do after an outage.
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