Every vendor's outages, day by day
Aug 25, 2026 to Nov 22, 2026 · 3,716 incidents · 1,083 major or critical · tick 2 to 4 to compare them
Every vendor
| Vendor | Incidents | Downtime | Worst day |
|---|---|---|---|
| 239 | 2h 22m | Sep 8 Major · 2 incidents · 17h 53m open | |
| 547 | 9h 54m | Aug 25 Minor · 13 incidents · 24h open | |
| 237 | 4h 23m | Oct 20 Critical · 2 incidents · 22h 47m open | |
| 185 | 37m | Sep 13 Minor · 1 incident · 4h open | |
| 87 | 6h 32m | Aug 25 Critical · 2 incidents · 24h open | |
| 148 | 33h 9m | Nov 19 Critical · 4 incidents · 4h 1m open | |
| 46 | 11h 47m | Aug 30 Critical · 2 incidents · 24h open | |
| 54 | 4d 22h | Oct 31 Critical · 1 incident · 24h open | |
| 70 | 11h 37m | Aug 27 Critical · 1 incident · 19h 44m open | |
| 93 | 3d 22h | Nov 12 Critical · 2 incidents · 14h 37m open | |
| 79 | 6h 19m | Sep 3 Critical · 5 incidents · 5h 23m open | |
| 91 | 3h 26m | Oct 14 Major · 2 incidents · 3m open | |
| 71 | 1h 44m | Oct 27 Critical · 2 incidents · 4h 42m open | |
| 45 | 2d 3h | Oct 24 Critical · 2 incidents · 54m open |
Downtime, added up
- 1
Sail Research4d 22h
- 2
OpenAI3d 22h
- 3
Replit2d 18h
- 4
Tenable2d 3h
- 5
Anthropic2d 3h
- 6
Databento2d 2h
- 7
Supabase2d 2h
- 8
ESET34h 9m
- 9
Fireworks AI33h 9m
- 10
Black Duck25h 29m
- Bars: minutes with any incident open. Right: weighted downtime. Minor Major Critical
Sail Research: 4d 22h weighted downtime in range.
Ranked on weighted downtime: minutes times the share of the vendor affected times severity. How it is weighted
Vendor leaderboard
All 186 vendors- 1
Sail ResearchAI54 incidents · 4d 22h weighted · 94.5% · 5d ago5d ago
- 2
OpenAIAI93 incidents · 3d 22h weighted · 95.6% · 2d ago2d ago
- 3
ReplitApps and SaaS25 incidents · 2d 18h weighted · 96.9% · 3d ago3d ago
- 4
TenableSecurity33 incidents · 2d 3h weighted · 97.6% · 2d ago2d ago
- 5
AnthropicAI45 incidents · 2d 3h weighted · 97.6% · 2d ago2d ago
- 6
DatabentoData and observability15 incidents · 2d 2h weighted · 97.6% · 41h ago41h ago
- 7
SupabaseData and observability54 incidents · 2d 2h weighted · 97.7% · 31h ago31h ago
- 8
ESETSecurity15 incidents · 34h 9m weighted · 98.4% · 4d ago4d ago
- 9
Fireworks AIAI148 incidents · 33h 9m weighted · 98.5% · 22h ago22h ago
- 10
Black DuckSecurity10 incidents · 25h 29m weighted · 98.8% · 32d ago32d ago
What caused them
All causes- Dependency124in 12 monthsMedian 2h 29m · 46 major
- Capacity121in 12 monthsMedian 1h 32m · 37 major
- Config change115in 12 monthsMedian 1h 5m · 48 major
- Network95in 12 monthsMedian 1h 34m · 33 major
- Database75in 12 monthsMedian 59m · 30 major
- Deployment39in 12 monthsMedian 1h 28m · 20 major
- Storage31in 12 monthsMedian 5h 57m · 11 major
- Bug29in 12 monthsMedian 1h 21m · 9 major
Learn from failures
83 postmortems- Increased wait time for Machine and Remote Docker jobs
CircleCINov 3, 2026 · 54m 2 weeks ago
Teams should configure diverse instance types and expand into multiple cloud regions to ensure sufficient capacity during sudden demand spikes.
- Avatar Outage
DescriptNov 2, 2026 · 5h 37m 2 weeks ago
Teams should conduct decision first post mortems and pre mortems to turn failures into actionable learning and build trust.
- Disruption with GitHub services
GitHubOct 30, 2026 · 32m 3 weeks ago
Engineering teams should integrate security into every stage of the developer lifecycle and design platforms for high availability and performance.
- Disruption with some Copilot services
GitHubOct 28, 2026 · 1h 15m 3 weeks ago
Teams can improve productivity and reliability by shifting security left across the developer lifecycle and building software collaboratively.
- Multiple services were experiencing issues in the europe-west2 region.
Google CloudOct 20, 2026 · 6h 8m 4 weeks ago
Teams should monitor regional service status dashboards and contact support if they encounter unlisted issues.
- Google Cloud Storage (GCS) customers experienced elevated latencies and error rates when performing upload or write operations.
Google CloudOct 8, 2026 · 29h 46m 6 weeks ago
Breaches disclosed to the SEC
All breachesQuestions
Where does this data come from?
From each vendor's own public status page (Atlassian Statuspage and incident.io JSON, Google Cloud's incidents feed, AWS Health history, Slack's status API), the postmortems vendors publish, and SEC Form 8-K Item 1.05 filings for material cybersecurity incidents. Times are as the vendor reported them, converted to UTC.
How often is it updated?
Status feeds are re-read every two hours, so the ongoing list is at most about two hours behind the vendor. The full refresh runs every day at 03:30 UTC: history is filled in a few vendors at a time, and the charts and counts are rebuilt.
How is the root cause assigned?
Only from the vendor’s own words. A rule reads the sentences where the vendor explains why ("caused by", "due to", "root cause") and maps them to one of fourteen categories. When the vendor has not said, the cause is "Not disclosed". Landmark postmortems are categorized by hand.
What do minor, major and critical mean?
The vendor’s own impact rating. On Statuspage pages, minor is degraded performance or a partial problem, major a partial outage, critical a full outage. Google Cloud’s low, medium and high and AWS’s informational, degraded and disruption levels are mapped to the same three.
Is this the same as uptime?
No. This is what vendors chose to post. Some post every blip, some only large outages, so compare a vendor with itself over time rather than one vendor with another. For what vendors promise and how they did, see Uptime (uptime.fru.dev).
Why are breaches here?
Since December 18, 2023, US public companies must disclose material cybersecurity incidents on Form 8-K, Item 1.05, within four business days of deciding they are material. Those filings are the most reliable public record of corporate breaches.