Cloudflare Workers AI Degraded
No internet-wide outage today. The backbone and the major clouds are healthy, but several named provider incidents were open as of 19:30 UTC.
Cloudflare has two open incidents, both rated minor impact. Workers AI has shown increased error rates since 14:25 UTC, and Workers Cron Triggers have been degraded since 19:17 UTC. Both sit at "identified" with a fix being implemented, so scheduled Workers jobs and AI inference calls may fail or run late until they close. A separate burst of HTTP errors at Cloudflare's Philadelphia location ran 16:40-16:54 UTC and is fully mitigated. Details: https://www.cloudflarestatus.com/
Twilio has several carrier-level problems open at once: SMS delivery failures from certain long codes to AT&T subscribers in the US (identified), voice call failures to Verizon in the US (recovering, under monitoring), and MMS delivery delays to Australian numbers (under investigation). These are last-mile carrier issues rather than a Twilio platform outage, but they affect real message and call delivery. Details: https://status.twilio.com/
Consumer outage trackers logged report spikes at several North American providers through the day, none of which the providers have confirmed as a broad network failure: Rogers in Canada (surges near 02:13 and 11:13 ET), CenturyLink (07:37 ET), Frontier (11:45 ET), plus YouTube (03:35 ET) and Amazon's retail site (10:52 ET). Spikes of this size are usually regional or short-lived.
One unconfirmed signal is worth naming rather than burying. IODA flagged a critical-level connectivity anomaly for Iowa at 13:20 UTC, measuring roughly an 85% drop against baseline. That reading comes from a single measurement source with low corroboration, so treat it as unverified. Drake University in Des Moines separately reported brief, repeated internet interruptions the same day, which is consistent with a localized problem but does not establish its scale.
Smaller items: DigitalOcean lost power redundancy in its ATL1 datacenter, briefly affecting GPU droplet performance, and has since restored it. ElevenLabs is investigating a broken MCP connection in ElevenCreative, with ElevenAgents unaffected. Slack is still working an issue open since August 13 in which workspaces with custom data retention policies have trouble loading historical messages. Zoom's September 8 degradation of Phone, Contact Center and Meetings is resolved and being monitored.
AWS's Middle East regions remain the longest-running item in cloud infrastructure. ME-CENTRAL-1 (UAE) and ME-SOUTH-1 (Bahrain) have been unavailable since physical damage earlier this year, and AWS still advises recovering those workloads from backups held in other regions. AWS's public feed updates slowly, so the absence of a new entry there is not by itself proof of an all-clear.
Resolved in the past 72 hours: AT&T had a 57-minute backbone disruption centered on nodes in Ashburn, Virginia early on September 6. Akamai fixed an Application Load Balancer availability problem and a certificate provisioning issue tied to Atlanta network connectivity on September 4. GitHub resolved elevated failures in Copilot code review and a Repository Contents API degradation, also on September 4. Cursor cleared login and Grok Bot errors on September 7.
Everything else we checked reports normal operation: Google Cloud, Azure, GitHub, Akamai, OpenAI, Anthropic, Discord, Atlassian, Vercel, Heroku, DigitalOcean, Groq, Replicate, Cohere and Stability AI. Meta's platforms are serving normally, with a modest trickle of user reports about slow loading rather than hard failures. Two checks were inconclusive: Stripe's and Meta's own status pages did not render for our automated request, so neither is independently confirmed here.
Bottom line: the internet is up. If you are seeing failures today, the most likely candidates are Cloudflare Workers, SMS and voice delivery through Twilio to AT&T or Verizon, or a regional ISP problem at your own provider.