Incidentsby IbisWho is down right now
16 ongoing incidents across 12 vendors · 156 this week · 74 vendors so far, +12 in the last 30 days
Ongoing now
Checked 8m ago- ElevenLabsInvestigating3h 43mEU Agents disruption in SIP calls
2h agoWe are still investigating. We will continue posting updates as more information becomes available
- Circle · USDC - LINEA - MintingInvestigating22h 42mUSDC on Linea , Delayed mints and burns (technical difficulties)
21h agoUSDC mints, burns and standard transfers via CCTP on Linea are experiencing temporary delays. We are currently investigating the cause and working to resolve the issue.
- Circle · Circle Mint - SandboxInvestigating4d 23hXDC Testnet network outage
4d agoThe XDC Testnet is currently experiencing a network outage affecting all XDC Testnet operations. Operations will be possible once the XDC Testnet network has been restored.
- Databento · HistoricalInvestigating4h 16mDelay in Batch Jobs processing
4h agoOur batch job processing system is fell behind, and slowly catching up. (There is no need to re-submit any jobs.) We are currently investigating the issue.
- Twilio · CARRIER NETWORK - SMS, APACMonitoring4h 38mSMS Delivery Delays and Delivery Receipt Delays from Twilio to Chunghwa Telecom Taiwan
2h agoWe have observed a recovery in SMS delivery and delivery receipts from Twilio to Chunghwa Telecom network subscribers in Taiwan and are monitoring service stability. We will provide another update in 2 hours or as soon...
- ElevenLabsInvestigating5h 2mincrease in latency
5h agoWe are investigating elevated latency affecting a small percentage of text-to-speech (TTS) requests. We will share an update as soon as we have more information.
- Grafana Labs · Incident Management and Response (IRM)Identified21h 53mIRM Unable to Send SMS to Austrian Numbers
16h agoThe issue has been identified. We are working on a resolution, but do not have an ETA at this time. We will provide another update as soon as we have more information to share. Users should configure mobile push or...
- Snyk · Snyk ContainerMonitoring2d 18hIssues API V3 Service - Degraded
7h agoWe have deployed a fix, and success rates have returned to normal, with requests no longer timing out. Response times have also improved significantly. We are monitoring to make sure the service remains stable.
- Supabase · API GatewayMonitoring6d 21hIntermittent latency in Eastern US
19h agoA fix for this issue has been implemented and our data shows recovery for users on projects that have previously been affected. We expect this situation to be resolved, but will keep monitoring for a while until fully...
- HashiCorpMonitoring2d 13hHCP Vault Azure: Cluster Updates and Creation
9h agoOur Engineering team has implemented a fix to resolve the issue. We are monitoring the situation closely and will post an update as soon as the issue is fully resolved.
- Circle · Circle Mint - SandboxInvestigating19 daysNoble Testnet network outage
6d agoThe Noble Testnet is still experiencing a network outage affecting all Noble Testnet operations. Operations will be possible once the Noble Testnet network has been restored.
- Twilio · CARRIER NETWORK - MMS Long Code, North AmericaInvestigating10 daysMMS Delivery Delays from a Subset of Twilio Long Codes to GCI United StatesDegradedCARRIER NETWORK - MMS Long Code, North Americastarted 10 days ago, Sep 26, 03:16 UTCStatus page
27h agoTwilio customers may be experiencing MMS delivery delays from a subset of Twilio Long Codes to GCI network subscribers in the United States. Our team is actively investigating this issue. We will provide another update...
- Zoom · Zoom Phone - Global - Devices (Softphones/Deskphones)Identified10 daysService Degradation Affecting Customer Using Polycom Devices Going OfflineDegradedZoom Phone - Global - Devices (Softphones/Deskphones)started 10 days ago, Sep 25, 17:45 UTCStatus page
12h agoWe are continuing to work with our underlying provider to address the subset of remaining devices that are showing offline. We will keep you informed with timely updates as progress is made. Thank you for your patience.
- Cloudflare · Cloudflare Sites and Services - Cloudflare One ClientIdentified13 daysCloudflare One Clients are incorrectly challenged on some sitesDegradedCloudflare Sites and Services - Cloudflare One Clientstarted 13 days ago, Sep 22, 19:23 UTCStatus page
13d agoThe issue has been identified and a fix is being implemented.
- Snowflake · Snowpark Container ServicesIdentified39 daysINC20000150
4d agoCurrent status: Since our last update, we have seen periods of improved provisioning performance while preserving available compute resources and coordinating closely with our third-party cloud provider. Resource...
- New RelicInvestigating11 daysPotential Service Interruption
11d agoWe are investigating a potential service interruption that may impact some customers. Please continue to monitor this page for updates.
13 more still marked open by the vendor, no update in 14+ days
Coinbase · Delayed Sends and Receives - EGLD (MultiversX)opened 17 days ago
Circle · Circle is discontinuing support for USDC and CCTP V1 on Noble in a phased transitionopened 25 days ago
MongoDB · Impaired Cluster operations in AWS me-central-1 and AWS me-south-1opened 32 days ago
Check Point · Infinity XDR is unavailable in UAE regionopened 216 days ago
AWS · Region Availabilityopened 218 days ago
Resolved this week
All this weekTwilio: 6 incidents in the last 24 hours, 23h 15m total23h 15mlast 3h 18m ago
Vercel · Elevated Sandbox error rates in Paris (cdg1)25mfixed 4h 34m ago
Cloudflare: 3 incidents in the last 24 hours, 12h 28m total12h 28mlast 5h 5m ago
Supabase · Increased errors on management api leading to project operation failures1h 10mfixed 5h 7m ago
Databento · GLBX.MDP3 delayed in the Historical API6h 11mfixed 6h 47m ago
OpenAI: 6 incidents in the last 24 hours, 19h 42m total19h 42mlast 10h 54m ago
GitHub · Disruption with some GitHub services1h 45mfixed 12h 38m ago
Expo · Website and services partially unavailable due to high database load2h 13mfixed 14h 49m ago
Zoom · Service Degradation Affecting ZoomMate25mfixed 15h 49m ago
Fireworks AI: 3 incidents in the last 24 hours, 51m total51mlast 18h 56m ago
Every vendor, day by day
65 vendors
Jul 9, 2026 to Oct 6, 2026 · 1,974 incidents · 438 major or critical · 65 vendors · tick 2 to 4 to compare them
| Vendor | Incidents | Downtime | Worst day |
|---|---|---|---|
| 549 | 2h 29m | Aug 3 Major · 12 incidents · 24h open | |
| 82 | 2d 10h | Jul 21 Critical · 6 incidents · 8h 51m open | |
| 47 | 10h 12m | Aug 30 Critical · 2 incidents · 24h open | |
| 84 | 19h 3m | Jul 29 Critical · 2 incidents · 6h 4m open | |
| 69 | 12h 24m | Aug 27 Critical · 1 incident · 19h 44m open | |
| 71 | 2h 2m | Jul 20 Critical · 1 incident · 9h 59m open | |
| 70 | 1h 37m | Jul 9 Critical · 3 incidents · 9h 26m open | |
| 92 | 1h 12m | Jul 20 Major · 1 incident · 1h 6m open | |
| 51 | 23h 37m | Aug 14 Critical · 2 incidents · 21h 37m open | |
| 78 | 1h 7m | Oct 2 Critical · 2 incidents · 5h 53m open | |
| 64 | 21m | Sep 26 Minor · carried over from an earlier day · 24h open | |
| 23 | 8h 28m | Jul 22 Major · carried over from an earlier day · 24h open | |
| 23 | 17m | Aug 31 Critical · 1 incident · 23h 59m open | |
| 25 | 1h 9m | Jul 20 Critical · 1 incident · 5h 46m open |
Downtime, added up · Jul 9, 2026 to Oct 6, 2026
- 1
Anthropic2d 10h
- 2
- 3
- 4
- 5
- 6
Cursor19h 3m
- 7
Confluent15h 38m
- 8
dbt Labs13h 43m
- 9
- 10
Snyk11h 11m
- Bars: minutes with any incident open. Right: weighted downtime. Minor Major Critical
Anthropic: 2d 10h weighted downtime in range.
Ranked on weighted downtime: minutes times the share of the vendor affected times severity. How it is weighted
Vendor leaderboard · 90 days
All 74 vendors- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
What caused them
All causes- Capacity85in 12 monthsMedian 1h 26m · 27 major
- Config change77in 12 monthsMedian 1h 3m · 33 major
- Dependency65in 12 monthsMedian 1h 47m · 27 major
- Network65in 12 monthsMedian 1h 20m · 24 major
- Database43in 12 monthsMedian 1h 14m · 17 major
- Deployment33in 12 monthsMedian 1h 22m · 15 major
- Storage18in 12 monthsMedian 5h 56m · 8 major
- Bug18in 12 monthsMedian 21m · 5 major
Learn from failures
66 postmortems- Multiple products in us-central1-b are experiencing network service degradation.
Google CloudSep 1, 2026 · 4h 8m 5 weeks ago
Teams should check service health dashboards when regional network service degradation affects cloud products.
- Incident with Copilot AI Model Providers
Engineering teams should monitor provider health when using third party AI model services.
- Incident with Actions
Teams should monitor service status when experiencing issues with automated workflow systems.
- We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region.
Teams should monitor regional health alerts when experiencing elevated latencies and errors across cloud products.
- Body parsing change for a React Server Components fix causes 25-minute outage
Urgent security mitigations still need a staged rollout; speed of response is exactly when a global config push is most dangerous.
- Partial downtime for Asana's MCP server
AsanaNov 18, 2025 · 0m 10 months ago
Teams should monitor server components to detect partial downtime affecting backend servers.
Breaches disclosed to the SEC
All breaches| Started | Vendor | Incident | Impact | Duration |
|---|---|---|---|---|
| Sep 2300:00 UTC13 days ago | Astrana Health discloses a material cybersecurity incident | Breach | 8-K | |
| Sep 800:00 UTC4 weeks ago | Boston Scientific | Boston Scientific discloses a material cybersecurity incidentBoston Scientific | Breach | 8-K |
| Sep 100:00 UTC5 weeks ago | Park Dental Partners discloses a material cybersecurity incident | Breach | 8-K | |
| Aug 3100:00 UTC5 weeks ago | Nutex Health discloses a material cybersecurity incident | Breach | 8-K | |
| Jul 3100:00 UTC2 months ago | Amgen discloses a material cybersecurity incident | Breach | 8-K |
Questions
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.