Cloudflare R2 Outage Resolved
No widespread internet disruption is in progress as of 10:30 UTC on September 5, 2026. The overnight period was quiet, and the largest single event had already closed before the North American morning.
Cloudflare R2 object storage returned elevated 503 errors in Eastern North America starting at 21:10 UTC on September 4. Cloudflare identified the cause within about 20 minutes and marked the incident resolved at 00:42 UTC on September 5, roughly three and a half hours end to end. A shorter R2 incident hit Western North America earlier on September 4, from 02:58 to 03:28 UTC. Both are closed. One minor Cloudflare issue stays open: incorrect geolocation for some WARP users, unresolved since August 27 and low impact. Details on the Cloudflare status page: https://www.cloudflarestatus.com/
Twilio is carrying three open incidents this morning, all narrow in scope: SMS delivery failures to Africell and Qcell in Gambia, an elevated authentication API failure rate affecting one identity gateway partner in the United States, and voice call failures from a subset of Twilio numbers to Switzerland. These affect specific carrier routes rather than the platform as a whole. See https://status.twilio.com/
Slack still lists a long-running issue with access to historical messages for workspaces on custom data retention policies, open since August 13 and unchanged.
Everything else came back clean. AWS, Google Cloud and Azure all show no active events. GitHub, Akamai, OpenAI, Anthropic, Discord, Atlassian, Zoom, Vercel, Heroku, DigitalOcean, Stripe, Cursor, Groq, Replicate, ElevenLabs, Cohere and Stability AI are operational. Meta platforms are up. No BGP hijacks, route leaks or submarine cable faults of note were reported in the past 24 hours.
Resolved in the past 72 hours: Akamai lost a network component in Atlanta on September 4, disrupting certificate provisioning and some edge traffic between 12:21 and 14:19 UTC, alongside a separate Application Load Balancer reporting fault the same day that ran about eight hours. September 3 brought a cluster of AI provider errors, with Anthropic, Cursor and GitHub Copilot each logging degraded model availability inside the same window; all recovered that evening. No common upstream cause has been confirmed by any of the three. Zoom cleared regional phone audio problems and North American SMS delays on September 3, and Discord resolved repeated server availability incidents on September 2 and 3.
One standing note that predates this window: AWS me-central-1 (UAE) and me-south-1 (Bahrain) have been unavailable since April 30 following conflict damage, and AWS still expects recovery to take months. Nothing changed there today, but it remains the longest-running regional outage on the board.
Verdict: incidents detected, none widespread. The internet is up.