Internet Status — August 4, 2026: Core Providers Operational, AWS Middle East Regions Still Impaired
No widespread internet disruption is in progress. Checks across crowd-sourced outage trackers, the major cloud and CDN providers, and the main developer and communications platforms show normal operation for the vast majority of users.
What we are tracking:
• AWS Middle East (UAE, me-central-1) and Middle East (Bahrain, me-south-1) — still impaired. Both regions sustained physical infrastructure damage in late April 2026 as a result of regional conflict, including structural damage, disrupted power delivery, and water damage from fire suppression activity. Two of three Availability Zones in me-central-1 remain significantly impaired, and me-south-1 remains unavailable. AWS continues to advise customers to back up data and direct traffic to alternate regions. This is a long-running regional situation, not a new event.
• Akamai — a reporting-data issue affecting "Traffic by Hostname" metrics ran from August 3 into August 4. A fix was implemented at 00:20 UTC and Akamai is monitoring to confirm the impact is fully mitigated. Content delivery itself was not affected.
• Twilio — several carrier-specific SMS delivery delays and voice call failures remain open, including routes to Bell Canada, Telenor Pakistan, Metfone Cambodia, Unitel Angola, and Reliance Jio in India. These are narrow, per-carrier routing issues rather than a platform outage.
• Fastly — traffic remains rerouted around Port Blair (IXZ), India, following an event on July 28. Impact is limited to that location.
Clear elsewhere: Google Cloud reports no broad severe incidents. Microsoft Azure shows no active events across all regions. Cloudflare has three scheduled maintenance windows in progress (Chicago, Miami, Berlin) that may raise latency for some traffic, but no unplanned degradation. GitHub, OpenAI, Discord, Slack, Atlassian, Zoom, Vercel, Heroku, DigitalOcean, Stripe, and Google Workspace all report normal operation.
Recently resolved in the past 72 hours: a GitHub Copilot degradation (resolved August 3) and a DigitalOcean Cloud Control Panel access issue (resolved August 3). Neither is ongoing.
A note on data quality: the AWS public status RSS feed was stale at check time, and Downdetector, ThousandEyes, IODA, and Meta's status dashboard could not be retrieved during this run. The AWS Middle East assessment above draws on AWS's own published statements and press reporting rather than the live feed. We found no crowd-sourced or press signal of a Meta platform problem today, but we could not confirm it from Meta's dashboard directly.
Bottom line: the internet is up. Unless you depend on the affected AWS Middle East regions or the specific carrier routes noted above, you are unlikely to notice anything today.
Sources: [Google Cloud Status](status.cloud.google.com), [Azure Status](azure.status.microsoft), [Cloudflare Status](cloudflarestatus.com), [Akamai Status](akamaistatus.com), [Fastly Status](fastlystatus.com), [GitHub Status](githubstatus.com), [Twilio Status](status.twilio.com), [AWS on the Bahrain Region](aboutamazon.com)