Internet Status — August 2, 2026: No Widespread Outages, Routine Provider Incidents
No widespread internet disruption is in progress today. Checks across crowd-sourced outage trackers, the major cloud and CDN providers, and platform status pages show normal service, with a small number of localized or long-running incidents worth noting.
**Core infrastructure: healthy**
All of the big providers report normal operation. [Google Cloud](status.cloud.google.com) shows no broad severe incidents across its 200+ services. [Azure](azure.status.microsoft) reports no active events across every region. [Cloudflare](cloudflarestatus.com) lists its services as operational — the "minor" flag on its dashboard reflects a routine handful of edge locations in re-route mode, which is normal background behavior, not a customer-facing outage. [Fastly](fastlystatus.com), [Akamai](akamaistatus.com), [GitHub](githubstatus.com), [OpenAI](status.openai.com) and [Discord](discordstatus.com) are all operational.
We also checked the second tier of platforms today: [Atlassian](status.atlassian.com), [Slack](slack-status.com), [Zoom](zoomstatus.com), [Vercel](vercel-status.com), [Heroku](status.heroku.com), [DigitalOcean](status.digitalocean.com) and [Stripe](stripestatus.com) all report all-clear.
**AWS Middle East regions remain unavailable**
AWS global services are healthy, but two regions are still offline. The [AWS status feed](status.aws.amazon.com) continues to report that ME-SOUTH-1 (Bahrain) and ME-CENTRAL-1 (UAE) are unavailable following physical damage tied to the conflict in the Middle East. Recovery is expected to take several months, billing for the affected regions is suspended, and creation of new resources there is disabled. AWS is advising customers with Middle East workloads to migrate to alternate regions. This is a continuation of a months-long situation rather than a new event today, but it remains the single largest piece of cloud capacity currently out of service.
**Twilio carrier incidents**
[Twilio](status.twilio.com) is tracking several open carrier-level incidents. The most notable for U.S. users is voice call failures to Core Communications subscribers, updated today. Others are carrier-specific and regional: voice failures on Reliance Jio in India (open since July 17), SMS delays on Metfone in Cambodia and Unitel in Angola, delayed SMS receipts on Liberty Puerto Rico, and a recovering voice issue on Claro Guatemala. These affect specific calling and messaging routes rather than general internet access.
**Recently resolved (past 72 hours)**
Akamai resolved an Edge Delivery issue that produced HTTP 400 errors on August 1. GitHub resolved a Copilot AI model provider degradation, also on August 1, caused by an upstream provider. Neither is ongoing.
**Routing, DNS and physical infrastructure**
No significant BGP hijacks or route leaks surfaced in today's checks. On the subsea side, the PEACE cable remains cut in the Red Sea with a repair timeline measured in months, but that fault dates to earlier in 2026 and is not causing new disruption today.
**One note on completeness:** Downdetector and Cloudflare Radar both blocked automated requests this run, and the Azure DevOps and Meta status pages returned no readable content. Broad crowd-sourced signal was cross-checked through secondary sources instead and showed nothing at outage scale, but our visibility into per-service report spikes was thinner than usual today.
**Bottom line:** the internet is working normally. Outside of the AWS Middle East regions and some Twilio carrier routes, we found no meaningful disruption.