Internet & cloud outages — August 2026

The internet is up. No widespread outages today — just a handful of minor, isolated incidents at individual providers. DigitalOcean is investigating degraded performance in its MKC1 region (https://status.digitalocean.com), affecting GPU workloads and some Kubernetes worker nodes across multiple racks since 11:10 UTC. The issue is contained to that single region. Slack is still working through an incident open since August 13: users in workspaces with custom data retention policies may be unable to load older messages (https://slack-status.com). Core messaging is unaffected. Twilio reports carrier-level SMS delivery delays or failures to a few networks in Belgium, Canada, and Brazil (https://status.twilio.com) — narrow in scope and typical day-to-day carrier churn. Recently resolved: GitHub had a major incident on August 17 lasting nearly 8 hours, with roughly 20% of web and API requests failing at peak due to network saturation on its Central US load balancers; it was fully resolved the same day and GitHub has been stable since (https://www.githubstatus.com). Cloudflare resolved two minor issues in the past day (Durable Objects errors in Hong Kong, elevated CDNJS errors), and Akamai closed out a multi-day Miami latency issue on August 18. Everything else checks out: AWS, Google Cloud, Azure, Cloudflare, Akamai, OpenAI, Discord, Atlassian, Zoom, Vercel, Heroku, and Stripe all report normal operations. No BGP, DNS, or routing anomalies detected today. Crowd-sourced outage trackers show only routine, scattered ISP reports.

Google's Home and Nest smart-home platform suffered a global outage today. Users across multiple regions reported Nest Hub displays and Google Nest/Home speakers failing to respond to voice commands, routines and automations not running, timers failing, and devices stuck on loading screens or returning 'Hmm, something went wrong.' Crowd-sourced reports pointed at Google's cloud backend rather than the devices themselves — roughly 74% of Downdetector complaints cited server connection problems. The incident does not appear on the Google Cloud status dashboard (consumer Home/Nest services aren't tracked there), and Google had not issued a statement at the time of writing, but user reports indicate service is recovering. Coverage: https://phandroid.com/2026/08/18/its-not-just-you-google-home-and-nest-suffers-global-outage-as-users-report-problems/ GitHub has two minor active incidents this morning: intermittent failures loading runner-group and runner-permission pages (monitoring) and an investigation into degraded performance for some services (https://www.githubstatus.com/). This follows yesterday's larger, now-resolved incident involving Copilot authentication failures and broader service degradation. Smaller ongoing items: Slack is still working through a narrow issue (since Aug 13) where workspaces with custom data-retention policies have trouble accessing historical messages (https://slack-status.com/). Akamai continues to implement a fix for connection drops in Miami, with no customer impact reported. Twilio shows routine regional SMS carrier degradations (UK, Brazil, French Caribbean). Spectrum shows only scattered, localized user reports — normal background noise, not a network event. Everything else checked is clear: AWS, Google Cloud, Azure, Cloudflare, Fastly, OpenAI, Discord, Atlassian, Vercel, Heroku, DigitalOcean, Stripe, Zoom, and Meta all report normal operations, and there are no signs of BGP, DNS, or undersea-cable problems. Core internet infrastructure is healthy.

GitHub spent most of Sunday working through a critical incident. Starting at 13:40 UTC, error rates hit roughly 20% across the GitHub.com website and API, with archive and raw-file downloads failing at closer to 50%. Pull Requests, Issues, Actions, Webhooks, Git Operations, Pages, Copilot, and SAML/OIDC sign-in were all degraded. GitHub identified the problematic component and applied corrective actions, and most services recovered between 17:00 and 19:00 UTC — but the incident was still open as of 20:20 UTC, with sporadic authentication failures lingering for Copilot in some applications (githubstatus.com). AWS is in the final stretch of a multi-day repair in Frankfurt. A facility infrastructure failure at the Equinix FR5 colocation site has impaired AWS Direct Connect connectivity in eu-central-1 since August 15. As of 18:00 UTC today AWS reports broad recovery, with the majority of affected hardware restored and only a small number of customers still impacted; customers with redundant Direct Connect locations were never affected (health.aws.amazon.com). Elsewhere, a cluster of smaller issues: Vercel had a partial disruption of its dashboard, observability, analytics, firewall, and login from 14:30 UTC — services recovered by about 16:45 UTC and missing observability data is being backfilled (vercel-status.com). Cloudflare's Lists service is degraded (changes to URL Lists delayed; existing lists and the edge network unaffected) per cloudflarestatus.com. Twilio is seeing elevated Verify Silent Network Auth failures for AT&T users in the US (status.twilio.com). Slack is still working a lingering issue from August 13 where users with custom data-retention policies may be unable to load older messages (slack-status.com). Core infrastructure is otherwise healthy: AWS (outside Frankfurt), Google Cloud, Azure, Azure DevOps, Akamai, Stripe, OpenAI, Discord, Atlassian, Zoom, Heroku, and DigitalOcean all report normal operations. No BGP, DNS, or undersea-cable incidents detected. Fastly's status page was unreachable from our monitoring vantage, but no third-party signals suggest any Fastly issues.

No internet-wide disruption today. Core cloud, CDN, and platform providers are largely healthy, with a handful of regional and service-specific incidents worth knowing about. The most notable active issue is AWS Direct Connect at the Equinix FR5 facility in Frankfurt, Germany. A facility infrastructure problem (reported as a cooling outage) has caused packet loss and connectivity degradation for customers whose Direct Connect circuits terminate solely at that site since roughly August 15. AWS says customers with redundant connections at other locations are unaffected, and remediation is underway pending replacement network hardware. Details: https://health.aws.amazon.com/health/status Separately, AWS's Middle East (UAE) region, me-central-1, remains impaired — the long-running aftermath of physical damage to two availability zones on March 1. AWS continues to advise affected customers to run workloads in other regions, with full recovery expected to take months. This is ongoing background, not a new development. Elsewhere: Twilio is working through several regional issues, including elevated errors on Interconnect at its Frankfurt edge, SMS delivery delays to networks in Colombia and Brazil, voice call delays to Iraq, and elevated Microsoft 365 IP blocks affecting some SendGrid email senders (https://status.twilio.com). Slack has an active incident, ongoing since August 13, affecting access to historical messages for workspaces with custom data retention policies (https://slack-status.com). Akamai is implementing a fix for connection drops and latency in Miami, though it reports no current customer impact (https://www.akamaistatus.com). Resolved in the past 72 hours: Cloudflare closed out a minor Durable Objects error-rate incident this morning; GitHub had several brief degradations on August 12–13 (webhooks, pull requests, logins) that were all resolved; Discord fixed a call-setup issue on August 13; and DigitalOcean resolved a volume attach/detach issue in FRA1 on August 13. Google Cloud, Azure, Heroku, Vercel, Zoom, Atlassian, OpenAI, Discord, and DigitalOcean all report normal operations. A few status pages (Fastly, Stripe, Meta, X) could not be read during this check, but no outage signals for those services appeared in crowd-sourced reports or news searches.

The internet is operating normally today. No widespread outages, routing failures, or DNS problems are detected across the major cloud, CDN, and platform providers we monitor. Core infrastructure is healthy. Amazon Web Services, Google Cloud, Microsoft Azure, Cloudflare, Fastly, GitHub, OpenAI, Discord, Atlassian, and Vercel all report normal operations with no active incidents. A few minor, localized issues are worth noting but none affect the broader internet: - Akamai has an identified networking issue in its Miami region (elevated latency / connection drops) that it says customers should not currently see impact from. - Twilio shows degraded performance on some carrier routes and two narrow active incidents (SMS delivery delays to a Brazilian carrier, and elevated Microsoft 365 IP blocks affecting some SendGrid email delivery). - Slack has an ongoing incident affecting access to historical messages only for workspaces using custom data-retention policies. Recently resolved (past 72 hours): DigitalOcean cleared a Block Storage issue in its FRA1 (Frankfurt) region on August 13, and Discord resolved a brief call-establishment issue the same day. The multi-hour GitHub Actions outage from August 6–7 remains fully resolved. Bottom line: the internet is up and stable. Sources: cloudflarestatus.com, health.aws.amazon.com, status.cloud.google.com, azure.status.microsoft, githubstatus.com, akamaistatus.com, status.twilio.com, slack-status.com.

All major internet infrastructure is operating normally as of August 15, 2026. The big cloud and CDN providers — AWS, Google Cloud, Microsoft Azure, Cloudflare, and Fastly — are reporting healthy status, and there is no sign of widespread routing, DNS, or undersea-cable disruption. Core platforms are green: GitHub, OpenAI, Discord, Vercel, Atlassian, and DigitalOcean all report all systems operational. A few minor, localized items are open but carry little to no user impact: Akamai is tracking connection drops in Miami (a fix is being implemented, with no customer impact reported), Slack has a narrow issue accessing historical messages for workspaces using custom data-retention policies, and Twilio has its usual set of region-specific SMS delivery delays across a handful of carriers. AWS shows some component alerts confined to its UAE region. None of these rise to an internet-wide event. Crowd-sourced reports show only scattered regional ISP complaints (Converge, Toob, Turknet) and a brief overnight uptick in Facebook reports that did not develop into a confirmed outage. Recently resolved in the past 72 hours: GitHub mitigated brief Copilot, Team Sync, and webhook issues on August 13, and DigitalOcean cleared a block-storage event in its Frankfurt region the same day. Bottom line: no meaningful internet-wide issues detected. The internet is up and running normally.

No widespread internet disruption today — core cloud platforms are healthy, and the day's activity is limited to a handful of minor, regional incidents at infrastructure and SaaS providers. The most notable active issue is at Akamai, which has been working since August 13 (16:39 UTC) on connection drops and increased latency for traffic served through its Miami location; the cause is identified and a fix is being implemented (akamaistatus.com). Akamai is also investigating delays in its Certificate Provisioning System (domain validation) that began August 11. Elsewhere, Slack has an ongoing issue where workspaces with custom data-retention policies may have trouble accessing historical messages (slack-status.com). Twilio is monitoring recovery on several regional carrier routes — SMS and voice to Sky UK subscribers and voice calls to Colombia — while delivery receipts for some short-code MMS to T-Mobile US remain delayed (status.twilio.com). Resolved in the past 72 hours: Cloudflare cleared brief regional HTTP 5xx errors affecting Kuwait, Bangkok, Jakarta and Dammam plus a network-performance issue in Queretaro, Mexico (August 13–14); GitHub resolved short disruptions to webhooks, pull requests and login (August 12–13); DigitalOcean fixed a block-storage volume issue in its FRA1 region (August 13); Discord resolved a call-connection issue (August 13); and Akamai cleared a 35-minute edge-delivery issue in India (August 12). AWS, Google Cloud, Microsoft Azure, Stripe, Vercel, Heroku, Atlassian, Zoom, DigitalOcean, OpenAI and Discord all report normal operations. One caveat: the AWS health dashboard and Fastly's status page could not be read by our monitors this run; no outage signals for either appeared in crowd reports or searches, so we treat both as healthy with lower confidence.

No meaningful internet-wide issues detected today, August 13, 2026. Core cloud and CDN providers — AWS, Google Cloud, Microsoft Azure, Cloudflare, Fastly, and Akamai — report normal operations, as do GitHub, OpenAI, Discord, Slack, Zoom, Atlassian, Vercel, Heroku, DigitalOcean, Stripe, and Meta's business platforms. Crowd-sourced outage trackers show no unusual report activity, and there are no indications of BGP, DNS, or routing problems. Two narrow, vendor-level items are ongoing, neither affecting general connectivity: Akamai is working through delays in TLS certificate provisioning (domain validation in its CPS system, ongoing since August 11 — status.akamai.com), and Twilio is monitoring recovering voice-call delivery to Peru while investigating an IP-retrieval API issue affecting some EU email customers (status.twilio.com). Recently resolved over the past 72 hours: Cloudflare restored Email Security delivery on August 12 after an upstream Spamhaus listing briefly disrupted mail flow (cloudflarestatus.com); GitHub fixed two short-lived issues on August 12 — login and release-asset download errors, and 500 errors on some pull request and issue pages (githubstatus.com); Fastly resolved elevated errors in its API and configuration management on August 11; and Akamai cleared a brief edge-delivery disruption in India on August 12. Bottom line: the internet is up and running normally.

The internet is running normally today. Checks across major cloud providers, CDNs, and platforms — AWS, Google Cloud, Microsoft Azure, Cloudflare, Fastly, Akamai, GitHub, OpenAI, Discord, Vercel, Heroku, DigitalOcean, Stripe, Slack, Zoom, and Atlassian — show no active incidents, and crowd-sourced outage trackers show no unusual spikes in problem reports. Minor items worth noting: Twilio is investigating an IP-retrieval API issue affecting EU regional customers and lists degraded performance on a few carrier-network components (MMS short code and toll-free in North America, voice in Middle East & Africa) plus the SendGrid API (status.twilio.com). Akamai is investigating delays in its Certificate Provisioning System's domain validation (akamaistatus.com). Neither affects general internet connectivity. Recently resolved (past 72 hours): DigitalOcean cleared a major incident affecting account registration and Droplet provisioning on August 9 (status.digitalocean.com). On August 11, Cloudflare resolved brief connectivity errors in London along with minor analytics delays (cloudflarestatus.com), and Fastly resolved elevated errors on its API and configuration management services. Bottom line: no meaningful outages detected today. The internet is up.

No major internet-wide disruptions today. Core cloud platforms — AWS, Google Cloud, Azure, and Cloudflare — are operating normally, with two minor vendor-level incidents active. Akamai is investigating degraded performance in its Certificate Provisioning System (CPS), causing delays in domain validation and enrollment status mismatches in its UI (akamaistatus.com). Impact is limited to customers provisioning TLS certificates; content delivery is unaffected. Twilio is working several regional carrier-level issues: voice call failures to Telefonica subscribers in Germany, SMS delivery delays to Claro subscribers in the Dominican Republic, and voice quality degradation on calls to Colombian landlines (status.twilio.com). These are carrier routing issues rather than a Twilio platform outage. Recently resolved: Verizon restored wireless voice service after a disruption on Saturday, August 8 that drew more than 12,000 Downdetector reports; a brief spike in user reports early this morning has subsided and report volumes are back in the normal range. Cloudflare resolved R2 availability issues on August 9, and GitHub resolved two short-lived issues on August 10 (Copilot model access and fine-grained token creation). Everything else checked — Slack, Zoom, Discord, OpenAI, Stripe, Vercel, Heroku, DigitalOcean, Atlassian, Fastly, and Meta platforms — reports all systems operational, and no notable BGP or routing anomalies were observed.

No widespread internet disruption is being reported today. The major cloud providers, CDNs and developer platforms we track are operating normally, with two narrow provider-specific incidents open and one long-running regional impairment still unresolved. ## Active incidents **Cloudflare — 1.1.1.1 public resolver, Tel Aviv.** Cloudflare identified problems with its 1.1.1.1 public DNS resolver in Tel Aviv (TLV) at 12:03 UTC. A fix has been implemented and the incident is in monitoring, though the Recursive DNS Service is still listed as degraded performance. Impact appears limited to that location rather than the resolver globally, and Cloudflare's proxy and authoritative nameservers are unaffected. Source: [Cloudflare Status](https://www.cloudflarestatus.com/) **Twilio — voice quality to Colombia and Philippines landlines.** Twilio reports degraded audio quality on calls from network subscribers to its Colombia and Philippines landline numbers. Root cause has been identified and a fix is in progress as of 05:04 PDT. Bulk Export and several regional carrier network services are also listed as degraded. Source: [Twilio Status](https://status.twilio.com/) ## Still ongoing: AWS Middle East regions AWS's Middle East (UAE) Region (me-central-1) and Middle East (Bahrain) Region (me-south-1) remain impaired following physical damage sustained during the regional conflict earlier this year. Two of three Availability Zones in me-central-1 are significantly impaired, and AWS has said full restoration will take several months; reporting from late July indicated Bahrain was still offline. AWS continues to advise customers with workloads there to back up data, consider migrating to alternate regions, and exercise disaster recovery plans. This is a pre-existing condition rather than a new event, but it is worth flagging because several third-party status aggregators currently roll these two regions into their global per-service health, showing AWS services such as S3, EC2, Lambda, Route 53 and DynamoDB as "degraded" worldwide. AWS's own health feed shows no new global incident today, and AWS-dependent platforms including GitHub, Vercel, Heroku and DigitalOcean are all reporting normal operations. Treat those aggregator warnings with care. Source: [AWS Health](https://health.aws.amazon.com/health/status) ## All clear Google Cloud, Microsoft Azure, Azure DevOps, Akamai, GitHub, OpenAI, Discord, Atlassian, Slack, Zoom, Vercel, DigitalOcean, Stripe and Heroku all report normal operations. Fastly shows scheduled maintenance on its Security Console and API with delivery services unaffected. Cloudflare, Zoom and Stripe each have routine maintenance windows in progress or scheduled — planned work, not outages. ## Recently resolved (past 72 hours) - **DigitalOcean (Aug 9):** account registration, Droplet creation and Reserved IPs were affected; fully resolved. - **Discord (Aug 7):** message send failures for users and bots; resolved at 16:02 PDT. - **X (Aug 9):** users reported a period of intermittent access; the platform is operational again. X publishes limited official status detail, so this rests on crowd-sourced reports. ## Bottom line The internet is up. Today's new issues are regional and provider-specific, and both are being actively worked.

No widespread internet disruption is in progress today. The major cloud platforms, CDNs and developer services we track are reporting normal operations, and there is no evidence of a global routing, DNS or backbone problem. Active incidents Twilio is the only tracked provider with open incidents, and all five are rated minor and confined to specific carrier networks rather than to Twilio's platform as a whole. As of this report: SMS delivery delays and failures to Rakuten in Japan (monitoring), SMS delivery failures to Airtel in India (monitoring), SMS delivery delays and failures from long codes to multiple networks in South Africa (investigating), voice call audio quality degradation on Colombian landline numbers (identified), and SMS delivery receipt delays on Liberty Mobile in Puerto Rico (monitoring). These affect messaging and voice traffic into those specific networks; most Twilio customers elsewhere are unaffected. See status.twilio.com for live updates. Recently resolved Verizon saw a spike of user-reported problems on August 8, peaking at roughly 13,000 reports on Downdetector beginning around 3:30 PM Eastern. Reports centred on New York, Los Angeles and Boston, with a smaller number of AT&T and T-Mobile users also reporting call failures. Report volumes have since returned to normal and the carriers have not published a formal incident. All clear Google Cloud, Microsoft Azure, Azure DevOps, Cloudflare, GitHub, OpenAI, Discord, Atlassian, Slack, Zoom, Vercel, Heroku, DigitalOcean and Stripe are all reporting normal service. Cloudflare's status page lists a number of edge locations in maintenance windows — Istanbul, Kyiv, Kolkata, Baghdad and others — but these are planned, routine, and automatically routed around; Cloudflare has no unresolved incidents. One note on context AWS's public event feed continues to surface its Middle East (UAE) me-central-1 event, which dates from March 1, 2026, when physical damage to facilities took two of the region's three availability zones offline. That is a months-old event still in long-term recovery, not a new disruption, and it does not affect other AWS regions. We were unable to reach the Fastly and Akamai status pages during this check, so those two are unverified rather than confirmed clear; we have no independent signal of problems at either. Overall: a quiet day. Some regional carrier-level messaging and voice issues, nothing approaching an internet-wide outage.

Most of the internet is operating normally today. The main open issue is a regional Cloudflare network fault in Istanbul, alongside a smaller storage incident and some carrier-level voice and SMS degradation at Twilio. No widespread, internet-scale outage was detected. Ongoing incidents Cloudflare — Istanbul network performance: Cloudflare reported a loss of dark fiber in the Istanbul region at 08:25 UTC and is working with its vendors to restore connectivity. The Network component is listed as degraded. Impact is regional and limited to traffic served through Istanbul; the rest of Cloudflare's global network is operating normally. Status: investigating. See https://www.cloudflarestatus.com/ Cloudflare R2 — bucket availability: Writes to a small set of R2 buckets in the ENAM region were impacted between 14:52 and 17:02 UTC on August 7. Cloudflare has identified the root cause and is still working to restore normal availability for the affected buckets. The scope is a subset of buckets rather than the service as a whole. Twilio — carrier-level degradation: Twilio lists degraded voice performance on some Latin America, Europe, and Middle East / Africa carrier routes, including audio quality problems on calls to Colombian landlines. SMS delivery receipts to Liberty Mobile Puerto Rico are recovering and under monitoring, and AT&T carrier maintenance in the US may cause intermittent SMS delays through August 9. See https://status.twilio.com/ Operating normally AWS, Google Cloud, Microsoft Azure, GitHub, OpenAI, Discord, Akamai, Fastly, Atlassian, Slack, Vercel, Heroku, DigitalOcean, and Stripe all report normal service. Zoom has several scheduled maintenance windows in progress, including datacenter and Zoom Phone work, with no operational impact expected. Resolved in the past 72 hours - GitHub Actions (Aug 7): Actions Runner Controller pods became stuck in an idle state, delaying workflow trigger events. Resolved. - Discord (Aug 7): message sending failures for users and bots that briefly expanded to affect all interactions. Resolved by 16:02 PDT. - Cloudflare (Aug 7): network performance issues in Chicago and a Workers Observability problem, both resolved. - Stripe (Aug 7-8): elevated Financial Connections authorization errors, since recovered. - GitHub Pages (Aug 6): deployment lag, mitigated. Other notes Internet access in Iran remains heavily throttled following the roughly 90-day national blackout that partially ended in mid-June. This is a policy-driven restriction rather than a technical fault, and it is unchanged from recent days. No BGP hijacks, DNS failures, or submarine cable faults with broad reach were identified today. One caveat on completeness: Downdetector and a few status endpoints could not be read directly during this check, so crowd-sourced signal was assessed through secondary trackers, which showed only low-level background reports and no sustained spikes.

No internet-wide disruptions today. The internet's core infrastructure — major clouds, CDNs, and DNS — is operating normally. The day's notable incident was at GitHub, which logged its second Actions outage in two days. On August 6, GitHub Actions and Pages suffered roughly five hours of degraded availability starting around 15:22 UTC, with workflow runs failing to start or failing mid-run and errors from the Actions REST API. A follow-on incident on August 7 left some Actions Runner Controller (ARC) runner pods stuck idle, and push and pull request events were not processed while it lasted. GitHub reports the issue resolved and all systems operational (githubstatus.com). Elsewhere, Twilio is working through regional carrier-level issues — SMS delivery problems affecting subscribers in Bangladesh and Puerto Rico, and voice quality degradation on calls to Colombia landlines — limited in scope (status.twilio.com). Status pages for AWS, Google Cloud, Azure, Cloudflare, Akamai, OpenAI, Discord, Slack, Zoom, Atlassian, Vercel, Heroku, and DigitalOcean all report normal operations. Recently resolved elsewhere: Cloudflare cleared a batch of Workers and regional network issues August 3–5, Discord fixed a messaging failure on August 4, and DigitalOcean resolved App Platform and write-operation issues on August 6. No BGP, DNS, or undersea cable problems were flagged today.

No new internet-wide disruptions have emerged today. Core routing, DNS, and the major cloud and CDN platforms are operating normally as of early August 6, 2026 (UTC). The notable items are long-running or narrowly scoped rather than new. Ongoing: AWS Middle East regions remain unavailable The AWS Middle East (UAE) region, me-central-1, and the Middle East (Bahrain) region, me-south-1, are still degraded or unavailable following physical damage to facilities earlier this year. AWS continues to advise customers to run workloads from other regions and has said full restoration is expected to take several months, with no firm date announced. Impact is confined to those two regions; all other AWS regions are operating normally. Source: AWS Service Health (https://health.aws.amazon.com/health/status). Ongoing: Twilio carrier-level messaging and voice delays Twilio is reporting several active, country-specific delivery problems: SMS delays and failures to networks in Italy, Cambodia, Bangladesh, Paraguay, and Burundi; delivery-receipt delays in Puerto Rico; and voice call failures to Reliance Jio subscribers in India. These are downstream carrier issues affecting specific destinations rather than a Twilio platform outage. Source: Twilio Status (https://status.twilio.com/). Planned work: Cloudflare maintenance Cloudflare has scheduled maintenance in progress at its San Jose, Barcelona, and Miami locations. Traffic may be rerouted and some users in those areas could see slightly higher latency. This is planned work, not an outage. Source: Cloudflare System Status (https://www.cloudflarestatus.com/). Resolved in the past 72 hours Spotify — A roughly two-hour disruption on August 5 affected the web player, desktop, and mobile apps, peaking at about 2,000 user reports. Service has recovered. Bluesky — A roughly 35-minute outage on August 5, traced to problems across the platform's Personal Data Server fleet, caused timeline, posting, and login failures. Service was restored at 12:51 UTC. Discord — Messaging failures on August 4, resolved. Akamai — A reporting-data issue on August 5 and a Web Security Analytics issue on August 4, both resolved. All Akamai systems are now operational. DigitalOcean — A cold-storage billing calculation error on August 4, resolved. Operating normally Google Cloud, Microsoft Azure, Azure DevOps, GitHub, OpenAI, Discord, Atlassian, Slack, Zoom, Vercel, Heroku, DigitalOcean, Stripe, and Akamai all report all-clear. Searches and outage aggregators show no BGP hijacks, route leaks, DNS failures, or submarine cable incidents reported today. A note on coverage A few status endpoints could not be read directly during this check: Fastly, Cloudflare Radar, Meta's status page, and Downdetector all blocked automated requests. Independent searches turned up no reports of active problems at any of them, but we could not confirm their status first-hand. Nothing in the available data suggests an issue at any of these providers. Bottom line: the internet is up. Two ongoing situations are worth knowing about if they touch your stack — AWS's two Middle East regions and Twilio's regional carrier delays — but neither is new today and neither affects the wider internet.

No widespread internet disruption is in progress right now. Core infrastructure - AWS, Microsoft Azure, Google Cloud, Cloudflare, Akamai, Fastly, GitHub and OpenAI - is delivering traffic normally. A handful of provider-level incidents are open. ACTIVE INCIDENTS Anthropic / Claude - degraded performance. Starting 07:05 UTC, Anthropic reported elevated error rates on requests to multiple Claude models, affecting claude.ai, the Claude API, Claude Code and Claude Cowork. The cause has been identified and a fix is in progress. Impact is rated minor and the services remain reachable. Source: https://status.claude.com Twilio - several carrier-specific messaging and voice problems remain open, including SMS delivery failures to C+W Sure in the UK, delivery-receipt delays at Liberty Mobile Puerto Rico and Metfone Cambodia, voice call failures to Reliance Jio in India, SMS delays at Econet Burundi, and Video Rooms connection issues in the in1 region. These are route-specific rather than platform-wide. Source: https://status.twilio.com Akamai - a reporting-data issue affecting the "Traffic by Hostname" report, open since 3 August, is being monitored. Content delivery is unaffected. Source: https://www.akamaistatus.com Cloudflare and Fastly - both networks show routine single-location re-routing. Cloudflare lists partial outages at roughly two dozen individual edge locations plus scheduled maintenance at others; Fastly has rerouted traffic away from Port Blair, India since 28 July. In both cases traffic shifts to nearby points of presence and end users generally see no impact. Sources: https://www.cloudflarestatus.com and https://www.fastlystatus.com AWS Middle East regions - a longer-running condition worth noting. AWS still lists Middle East (UAE) ME-CENTRAL-1 and Middle East (Bahrain) ME-SOUTH-1 as damaged and unable to reliably support customer workloads following the regional conflict, and continues to advise customers to run from other regions. AWS has said recovery is expected to take several months. All other AWS regions are operating normally. Source: https://status.aws.amazon.com ALL CLEAR Google Cloud reports no broad severe incidents. Microsoft Azure and Azure DevOps report no active events. GitHub, OpenAI, Discord, Atlassian, Slack, Zoom, Vercel, Heroku, DigitalOcean and Stripe all report all systems operational. Meta's platforms are reported up. RESOLVED IN THE LAST 72 HOURS Discord messaging and DM delivery failures (4 August), Twilio elevated 500 errors across multiple APIs (4 August), a GitHub Copilot incident (3 August), and DigitalOcean control-panel access errors caused by mTLS verification failures (3 August) have all been resolved. NOTES ON DATA We could not retrieve Downdetector directly this run. A secondary crowd-sourced source, istheservicedown.com, showed no services flagged as down. Search results referenced scattered consumer ISP complaints in the US involving Verizon and AT&T, but we found no provider confirmation of a broad outage, so treat those as unverified local reports. No BGP hijacks, route leaks or DNS-level incidents of note were identified. Bottom line: the internet is up. Expect intermittent errors if you depend on Claude's API or on the specific carrier routes Twilio has flagged.

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](https://status.cloud.google.com/), [Azure Status](https://azure.status.microsoft/en-us/status), [Cloudflare Status](https://www.cloudflarestatus.com/), [Akamai Status](https://www.akamaistatus.com/), [Fastly Status](https://www.fastlystatus.com/), [GitHub Status](https://www.githubstatus.com/), [Twilio Status](https://status.twilio.com/), [AWS on the Bahrain Region](https://www.aboutamazon.com/news/aws-bahrain-region-middle-east-conflict)

No widespread internet disruption is underway today. Core routing, DNS and the major cloud and CDN platforms are operating normally, with a small number of geographically contained incidents still open. Cloud providers: Google Cloud reports no broad severe incidents, and Microsoft Azure shows no active events across all regions. AWS global services are operating normally, but two regions remain out of service: ME-CENTRAL-1 (UAE) and ME-SOUTH-1 (Bahrain) are still unavailable following conflict-related physical damage to facilities earlier this year. AWS has suspended billing in the affected regions and advises customers to recover resources elsewhere from remote backups; the company has said restoration is expected to take several months. This is an ongoing situation rather than a new development, and it does not affect AWS regions outside the Middle East. CDN and edge: Cloudflare is operational, with routine scheduled maintenance in progress at San Jose (SJC) and Miami (MIA) and further windows queued for Ashburn, London and Berlin. Traffic may be re-routed away from those locations with minor added latency — normal maintenance behavior, not an outage. Akamai reports all systems operational. Platforms: GitHub, OpenAI, Discord, Slack, Atlassian, Vercel, DigitalOcean and Heroku all report normal operation. Meta platforms are up, though background user reports continue at typical levels for their scale. Zoom has several services in scheduled maintenance windows, including network maintenance at its Vancouver datacenter. Still open: Twilio is tracking a cluster of narrow, carrier-specific incidents — SMS delivery delays affecting Econet Burundi, Metfone Cambodia, Unitel Angola and Liberty Mobile Puerto Rico, plus voice call failures to Reliance Jio in India and one US carrier. These are limited to individual carrier routes rather than Twilio-wide. Resolved in the past 72 hours: Akamai mitigated a partial Edge Delivery disruption causing HTTP/HTTPS errors on August 1. Crowd-sourced trackers also logged report spikes for Verizon and World of Warcraft on August 2; both have since settled. Coverage note: Downdetector, Fastly's status page and ThousandEyes' outage map were unreachable during this check, and Stripe's status page returned stale data. We found no independent indication of problems at those providers, but our visibility into them today is incomplete. Sources: <a href="https://health.aws.amazon.com/health/status">AWS Health</a>, <a href="https://status.cloud.google.com/">Google Cloud Status</a>, <a href="https://azure.status.microsoft/en-us/status">Azure Status</a>, <a href="https://www.cloudflarestatus.com/">Cloudflare Status</a>, <a href="https://www.akamaistatus.com/">Akamai Status</a>, <a href="https://www.githubstatus.com/">GitHub Status</a>, <a href="https://status.twilio.com/">Twilio Status</a>, <a href="https://pulse.internetsociety.org/en/shutdowns/">Internet Society Pulse</a>.

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](https://status.cloud.google.com/) shows no broad severe incidents across its 200+ services. [Azure](https://azure.status.microsoft/en-us/status) reports no active events across every region. [Cloudflare](https://www.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](https://www.fastlystatus.com/), [Akamai](https://www.akamaistatus.com/), [GitHub](https://www.githubstatus.com/), [OpenAI](https://status.openai.com/) and [Discord](https://discordstatus.com/) are all operational. We also checked the second tier of platforms today: [Atlassian](https://status.atlassian.com/), [Slack](https://slack-status.com/), [Zoom](https://www.zoomstatus.com/), [Vercel](https://www.vercel-status.com/), [Heroku](https://status.heroku.com/), [DigitalOcean](https://status.digitalocean.com/) and [Stripe](https://www.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](https://status.aws.amazon.com/rss/all.rss) 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](https://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.

No internet-wide disruptions are underway today. The core cloud platforms — AWS, Google Cloud, and Microsoft Azure — all report normal operations, and crowd-sourced outage trackers show no unusual report activity. The main item to watch is Akamai, which is investigating an emerging edge delivery issue described as a partial disruption of HTTP/HTTPS traffic with 400 errors (last update 11:12 UTC on [akamaistatus.com](https://www.akamaistatus.com/)). User-facing impact appears limited so far — outage trackers show no significant report spikes — and all other Akamai services are listed as operational. Cloudflare is monitoring a fix for network performance issues at its Hamburg, Germany (HAM) data center; customers routing through Hamburg may see intermittent request errors. This follows a cluster of minor, quickly-resolved Cloudflare incidents on July 31 (Istanbul, Ashburn, London, and brief API availability issues) — details on [cloudflarestatus.com](https://www.cloudflarestatus.com/). Elsewhere: GitHub reports degraded availability for one Copilot AI model due to an upstream provider issue, with all core GitHub services operational. Twilio continues to work through carrier-specific voice and SMS issues, including voice call failures to Core Communications subscribers in the US and to Reliance Jio subscribers in India, plus SMS delays affecting carriers in Cambodia, Angola, and Puerto Rico. No BGP, DNS, or undersea cable incidents were reported today. Slack, Zoom, Discord, OpenAI, Stripe, Vercel, Heroku, DigitalOcean, Azure DevOps, and Atlassian all report normal operations. One caveat: Fastly's status page could not be reached during this check, though no Fastly outage signals appeared anywhere else.