Twilio Voice, SMS Disruptions
No internet-wide outage today. Most major providers are running normally, with a few contained incidents and one large recent outage still finishing its recovery.
Twilio is the main active incident. The company reported voice call failures from a subset of Twilio phone numbers to multiple countries in Europe, identified at 03:24 PDT, with engineers working on a fix. Separately, Twilio is tracking SMS and MMS delivery delays across several carriers: C-Spire and Dish in the US, Three in the UK, long code traffic in the Netherlands, and Algar Telecom in Brazil. Several of those show recovery underway. Message Logs also saw elevated latency on a small share of traffic. The impact is limited to voice and messaging on the affected routes rather than the platform as a whole. Details are on the Twilio status page (status.twilio.com).
Microsoft 365 is still closing out the outage that began August 31 and ran into September 2. Microsoft traced it to a misconfiguration in a core authentication configuration shared by several Microsoft 365 services, which stopped authentication components from deploying correctly to part of the infrastructure. Exchange Online, Outlook, Teams, SharePoint Online, OneDrive for Business, Purview, Defender XDR, Copilot, the Microsoft 365 Admin Center and Universal Print were all affected. Mailbox connectivity returned roughly 12 hours after Microsoft first acknowledged the problem, and by September 2 the company reported availability stable above 99 percent with most users no longer seeing impact. Search was the last component still recovering. A small number of Outlook reports are still trickling in today. Background: BleepingComputer (bleepingcomputer.com) and TechCrunch (techcrunch.com).
Cloudflare is showing a minor incident: an HTTP/3 problem affecting R2 custom domains, where a fix is being implemented, and incorrect geolocation for some WARP users. Scheduled datacenter maintenance is also running in San Diego, Denver, Chicago, Montreal and Nashville. Neither issue is global (cloudflarestatus.com).
Slack is still carrying a long-running incident, open since August 13, covering trouble accessing historical messages on workspaces that have custom data retention policies enabled. Every other Slack function is reported normal.
The rest of our watch list is clear. Google Cloud reports no broad severe incidents and Azure shows no active events. GitHub, Akamai, OpenAI, Anthropic, Discord, Atlassian, Zoom, Vercel, Heroku, DigitalOcean and Stripe are all operational. The AI platforms we track (Cursor, Groq, Replicate, ElevenLabs, Cohere and Stability AI) report no issues, and Meta's platforms show no active disruption. One caveat worth stating plainly: we could not load Amazon's official health dashboard directly on this run, and a single third-party aggregator flagged elevated AWS error rates. No news coverage, no substantive customer reports and no other source corroborated that, so we are treating AWS as normal while noting we could not confirm it at the source.
Resolved in the past 72 hours: Discord fixed two issues on September 2, one with voice endpoint selection that could prevent calls from starting and one causing degraded performance on some servers. Anthropic cleared a 14-minute stretch of elevated errors on Claude Sonnet 5 plus a credit purchase delay, both on September 2. Cursor resolved service degradation affecting its automation and cloud agent features in early September.
One thing we checked and ruled out: searches for current submarine cable damage surface articles about Red Sea cable cuts that read as recent but actually describe earlier events, including one traced to February 2024. We found no evidence of new subsea cable damage today.
Overall status: incidents detected, no widespread outage. The internet is up.