Twilio MMS Delivery Delays
No internet-wide outage is in progress. The major cloud and CDN platforms are reporting normal service, and the issues we can confirm today are narrow ones affecting specific features rather than whole networks.
**Active, provider-confirmed**
Twilio is the most substantial open incident. The company reports MMS delivery delays and failures from a subset of its US short codes to multiple carrier networks, with the cause identified and a fix in progress. Separately, Twilio lists MMS delivery failures on Telstra in Australia affecting a subset of Australian Twilio numbers, and is monitoring recovery on SMS delivery to Robi subscribers in Bangladesh. This is a messaging-delivery problem, so the visible effect is one-time passcodes, alerts and picture messages arriving late or not at all on affected routes rather than any loss of connectivity. Source: https://status.twilio.com/
Cloudflare is carrying three minor incidents, none of them affecting content delivery or DNS resolution. A Networking Routes UI problem in the dashboard began at 15:32 UTC and a fix is being implemented; Browser Isolation session failures affecting Browser Isolation and Gateway started at 14:25 UTC and are in monitoring after a fix; and a WARP geolocation error open since 27 August is still being worked on. Source: https://www.cloudflarestatus.com/
Slack continues to carry a long-running minor incident, open since 13 August, in which customers with custom data retention policies enabled have trouble accessing historical messages. Everything else on Slack's board is clear. Source: https://slack-status.com/
**Consumer ISP reports**
Crowd-sourced trackers logged report spikes at two large consumer ISPs in the early hours, both of which have since settled. AT&T reports climbed from roughly 03:20 ET, weighted toward 5G Home Internet, broadband and Wi-Fi, with complaints concentrated in Texas including a fibre fault in north Dallas. Virgin Media in the UK saw reports rise from roughly 07:00 BST, weighted toward landline internet and email. Neither company published a status-page notice, and by the afternoon istheservicedown showed no problem detected at AT&T, so these look like regional faults rather than national outages. Report-volume data is a crowd signal, not a measurement, and we are treating the scope of both as unconfirmed.
**Clear on checks**
AWS, Microsoft Azure, Google Cloud, GitHub, Akamai, Discord, Atlassian, Zoom, Vercel, Stripe, DigitalOcean and Heroku all report normal service. On the AI side, OpenAI, Anthropic, Cursor, Groq, Replicate, ElevenLabs, Cohere and Stability AI are all operational. Meta's status page renders client-side and could not be read directly, but no Facebook, Instagram or WhatsApp disruption surfaced in outage reporting today. No large-scale BGP hijack, route leak or submarine cable incident was reported.
**Recently resolved (past 72 hours)**
Cursor had login and account errors between 12:12 and 13:08 UTC today, affecting the CLI, Cloud Agents and the IDE, now fixed. Cloudflare resolved a TURN service degradation and Workflows instance-creation errors earlier today, plus a Registrar display problem and connectivity issues in its Canberra location on 6 September. On 4 September, Akamai worked through an Application Load Balancer reporting and availability issue (06:15 to 14:20 UTC) and a network component failure in Atlanta that took down its Certificate Provisioning System for about two hours, while GitHub cleared a Copilot Code Review disruption and a repository contents API degradation.
For wider context, the week's two larger events both fall outside the 72-hour window: a Google Cloud zonal failure in us-central1-b on 1 September that touched 15 products for just over four hours, and a roughly 90-minute window on 3 September in which several major AI assistants degraded at once.
**Assessment:** incidents detected, no widespread outage. Scope is single-provider and feature-level in each case, and the trajectory is stable to recovering.