Internet & cloud outages — August 2026

No widespread outages today. The core cloud platforms — AWS, Google Cloud, and Microsoft Azure — are operating normally, and most major services report all systems operational. Cloudflare is the day's main story, with two minor incidents opened mid-day UTC: elevated error rates on Workers KV read requests in Western Europe (from 11:01 UTC) and failures in the Access IP-bypass list service (from 11:40 UTC). Both are under investigation, with writes and core CDN traffic unaffected. A WARP geolocation-accuracy issue open since August 27 also remains active, with a fix in progress (cloudflarestatus.com). Elsewhere, Twilio is working through a cluster of carrier-level degradations: SMS delivery failures to Telma Madagascar, recovering voice-call issues in Hong Kong and the UK, and MMS delivery delays to C-Spire in the US. Slack's long-running issue with retrieving historical messages in workspaces that use custom data-retention policies, open since mid-August, is still unresolved. ElevenLabs had a brief outage of its customer-support ticketing system (its APIs were unaffected) and reports it largely restored. Recently resolved: GitHub cleared elevated errors on OpenAI models in Copilot this morning (09:58 UTC, an upstream provider issue); Anthropic resolved about three hours of elevated errors on Claude Code on August 28; Akamai fixed an Event Center reporting outage on August 28; and Zoom resolved a Contact Center billing/reporting degradation in Europe on August 30. In the US, a brief overnight spike in Spectrum outage reports cleared quickly. Bottom line: the internet is up. August closes out with isolated, minor incidents and no widespread disruption.

No internet-wide disruptions today. Core infrastructure is healthy — AWS, Google Cloud, Azure, Akamai, GitHub, OpenAI, Anthropic, and Discord all report normal operations, and there are no significant BGP, DNS, or undersea cable incidents. Two providers are carrying minor open incidents. Cloudflare is still working on an issue, open since August 27, that returns incorrect geolocation for some WARP users; impact is rated minor and the broader CDN and DNS network is unaffected (cloudflarestatus.com). Twilio's status page lists several regional carrier-level degradations — SMS delivery issues to networks in Kuwait, El Salvador, and Costa Rica, MMS delays to C-Spire in the US, and voice-call problems on some UK routes and in Hong Kong — most already in recovery or being monitored (status.twilio.com). Elsewhere: Slack continues to work through a low-impact issue, open since August 13, affecting access to historical messages in workspaces with custom data-retention policies (slack-status.com). The Internet Archive / Wayback Machine drew a bump of user outage reports this afternoon, though automated checks show it responding normally. Recently resolved: GitHub cleared several Actions and Pull Request delay incidents earlier this week (Aug 24–27, githubstatus.com), Cloudflare resolved elevated 5xx errors in Singapore on August 29, and Zoom fixed a Hong Kong service degradation on August 27.

No widespread internet disruption is underway on August 29, 2026. Core infrastructure (AWS, Google Cloud, Azure, Akamai, GitHub, OpenAI, Anthropic, Discord) reports all systems operational, and there are no signs of BGP routing or DNS problems. The day's most notable item is a Cloudflare edge incident in Singapore that wrapped up in the early hours UTC, on top of a busy 72 hours of platform-level incidents that have all since cleared. **Cloudflare — Singapore edge errors (resolved 00:43 UTC).** Cloudflare's Singapore (SIN) data center returned elevated HTTP 5xx errors for roughly seven hours, from 17:36 UTC on August 28 until 00:43 UTC on August 29. Cloudflare classed the impact as minor, and traffic served from other locations was unaffected. A separate low-impact issue — incorrect geolocation for some Cloudflare WARP users — has been open since August 27 and is still marked "Identified" with a fix in progress. Source: https://www.cloudflarestatus.com/history **Twitch — critical outage, resolved.** Twitch had its most serious incident of the week on Thursday evening: a "Critical" impact event affecting Web, Chat and Video (Watching) from 20:09 UTC on August 27 until 02:31 UTC on August 28 (about 6.5 hours). Users saw chat failures, login trouble and impaired search. Downdetector registered a second, smaller spike of ~2,000 reports on Friday afternoon (US Pacific), but Twitch's status page showed all systems operational at the time and logged no new incident. No root cause has been published. Source: https://status.twitch.com/ **Anthropic — Claude Code and Cowork on the web (resolved).** On August 28 from about 18:21 to 21:00 UTC, an issue with an upstream cloud provider caused some Claude Code (web) and Claude Cowork sessions to fail to start or disconnect mid-task. A mitigation restored service and the incident is resolved; the API and Claude.ai were not listed as affected. Source: https://status.claude.com/ **Other recently resolved incidents (past 72 hours):** - GitHub: Actions job start failures and delays on August 26 (up to 25% of pull-request-triggered workflow runs delayed), plus a billing-services disruption and a Copilot model-provider issue on August 27 — all resolved. https://www.githubstatus.com/ - Zoom: service degradation for users in Hong Kong on August 27 (12:02–15:10 PDT), resolved. https://www.zoomstatus.com/ - Cursor: sign-in degradation on cursor.com and the IDE on August 27, resolved. https://status.cursor.com/ - Akamai: reporting/Event Center dashboard data unavailability on August 28, resolved. https://www.akamaistatus.com/ **Ongoing, low impact:** - Twilio has ten open "Minor" incidents, all carrier- or country-specific SMS and voice routes (Brazil, Canada, UK, Hong Kong, Tajikistan, Kuwait, Bulgaria, El Salvador, Costa Rica, Puerto Rico). None affect the Twilio platform or API globally. https://status.twilio.com/ - Slack's incident affecting access to historical messages in workspaces with custom data-retention policies remains open (since August 13). https://slack-status.com/ - AWS's me-central-1 (UAE) region remains impaired following the physical infrastructure damage in March 2026; AWS continues to advise customers to run workloads in other regions. https://health.aws.amazon.com/health/status **Regional / unconfirmed:** Downdetector Indonesia showed a rise in user reports for mobile operator Telkomsel starting around 00:30 WIB on August 29. We could not confirm scope or an operator statement, so treat this as a possible localized disruption rather than a verified outage. Status pages for Stripe, Heroku, Vercel, DigitalOcean, Atlassian, Groq, Replicate, ElevenLabs, Cohere and Stability AI show no active incidents. Meta's status page (metastatus.com) did not render for automated checks; no crowd-sourced reports point to a Facebook, Instagram or WhatsApp problem today. Undersea cable news is limited to the early-August Indigo West/Central faults off Perth, which remain under investigation but are not causing new connectivity impact today. Overall classification: incidents-detected — a handful of notable provider incidents, all resolved or contained, with no internet-wide disruption.

Early-day report (published 09:00 UTC). No internet-wide outage is in progress. The most notable event of the past 24 hours was a roughly six-hour disruption at Twitch, which has been resolved. A minor Cloudflare WARP issue remains open. Core cloud platforms, DNS, and global routing show no problems. Twitch (resolved). Twitch confirmed an incident beginning at 20:09 UTC on August 27 in which chat, login, and search were impaired for many users; Downdetector reports climbed past 13,000 within minutes. A fix was implemented at 22:03 UTC and Twitch declared all known impact resolved at 02:31 UTC on August 28. Sources: https://status.twitch.com/ and https://gvwire.com/2026/08/27/twitch-down-for-thousands-of-users-downdetector-shows/ Cloudflare (minor, ongoing). Cloudflare is still working on a fix for incorrect geolocation affecting some WARP users, open since 18:46 UTC on August 27. Two other short incidents from yesterday, Turnstile challenge issues (resolved 19:29 UTC) and degraded Workers Builds (resolved 22:58 UTC), are closed. No Cloudflare data centers are marked degraded or re-routed. Source: https://www.cloudflarestatus.com/ Other items being tracked: - Akamai resolved a reporting-data issue at 03:30 UTC today; a separate data-availability problem in its Traffic by Hostname report, open since August 20, is still in monitoring. Neither affects content delivery. https://www.akamaistatus.com/ - Zoom resolved a service degradation in Hong Kong yesterday (12:02 to 15:10 PDT). https://www.zoomstatus.com/ - Twilio has six open carrier-level items: SMS delays to Megafon Tajikistan, Telefonica El Salvador, and I.C.E. Costa Rica; delivery-receipt delays to Liberty Puerto Rico; MMS delays to C-Spire in the US; and voice call issues to UK numbers. These are routine carrier-specific problems, not a platform outage. https://status.twilio.com/ - Slack's issue with accessing historical messages in workspaces using custom data-retention policies, open since August 13, is still listed as unresolved. https://slack-status.com/ - Crowd-sourced trackers show a modest rise in EA problem reports since about 00:45 UTC; EA has not confirmed an incident and the volume is small, so we are treating this as unconfirmed. Recently resolved (past 72 hours). GitHub's three August 27 incidents (Copilot AI model providers, Actions and Pull Requests, and Billing) are all resolved and GitHub reports all systems operational today; its August 26 Actions incident (jobs failing to start from 15:02 to 15:45 UTC) was traced to database primary saturation. DigitalOcean's control panel and API 5xx errors (August 24 to 25) are resolved. Cursor's sign-in degradation on August 27 is resolved. Anthropic's August 24 elevated-error incidents are resolved. Google Cloud published its final incident report for the August 20 us-west1 (Oregon) degradation, attributing it to fiber maintenance that compromised inter-datacenter capacity when automated rerouting failed. https://www.githubstatus.com/ https://status.digitalocean.com/ https://status.cloud.google.com/ All clear today: AWS (apart from the long-running unavailability of the Middle East UAE and Bahrain regions dating to March), Google Cloud, Microsoft Azure, Azure DevOps, GitHub, OpenAI, Anthropic, Discord, Atlassian, Vercel, Heroku, DigitalOcean, Stripe, Cursor, Groq, Replicate, ElevenLabs, Cohere, and Stability AI all report normal operations. Meta's platforms are operating normally with user report volumes in the typical range. No BGP hijacks, leaks, or DNS root issues were reported. Overall assessment: incidents detected, no widespread outage. This report was compiled early in the UTC day and reflects conditions as of 09:00 UTC.

Most of the internet is running normally this morning, but GitHub is carrying an active, high-impact incident. **GitHub Copilot AI Model Providers — ongoing.** GitHub opened an incident at 10:04 UTC reporting degraded availability for Copilot AI Model Providers, and marked the component as a major outage. The incident is still in the investigating stage with no mitigation announced yet, so Copilot code completions and chat may fail or time out for some users. GitHub rates the impact as critical. Live updates: https://www.githubstatus.com **GitHub Billing — ongoing, minor.** A separate billing incident opened at 23:37 UTC on August 26. Billing budget pages failed to load and Copilot CLI sessions failed to start or continue. GitHub applied a mitigation that restored Copilot usage and is now monitoring the remaining billing page disruption. GitHub also resolved two shorter incidents in the last 48 hours: a degradation affecting Actions and Pull Requests earlier today, and an Actions incident on August 26 that GitHub traced to database saturation. **Everything else is quiet.** Google Cloud reports no broad severe incidents. Microsoft Azure reports no active events. Cloudflare has no open incidents — only scheduled datacenter maintenance in Ashburn, Philadelphia and Hamburg — after resolving a roughly 90-minute Durable Objects degradation on August 26 and a brief Realtimekit API failure earlier today. Akamai, OpenAI, Anthropic, Discord, Atlassian, Zoom, Vercel, Heroku, DigitalOcean and Stripe are all operational, as are Cursor, Groq, Replicate, ElevenLabs, Cohere and Stability AI. Two smaller items worth noting. Slack has a long-running minor incident, open since August 13, affecting access to historical messages in workspaces with custom data retention policies. Twilio is reporting several carrier-level regional issues — SMS delivery delays to ICE subscribers in Costa Rica, MMS delays to C-Spire in the US, delayed delivery receipts in El Salvador, and voice call problems in Sweden and Brazil that are now recovering. These are localized to specific carriers rather than platform-wide. As standing background, AWS still lists its two Middle East regions — UAE (me-central-1) and Bahrain (me-south-1) — as unable to reliably support customer workloads following damage sustained earlier this year. That is a long-term condition, not a new development, and AWS has advised customers to recover resources in other regions. No new AWS incidents are open elsewhere. We found no evidence of BGP routing incidents, DNS failures, undersea cable faults, or country-level connectivity loss today. Crowd-sourced outage trackers show only routine, localized ISP and consumer-service noise. Overall: incidents detected, but no widespread internet disruption. The main thing to watch is the GitHub Copilot model provider outage, which is still unresolved as of publication.

No internet-wide outage today. The major cloud, CDN and platform providers are reporting normal operations, and the notable activity is regional or long-running rather than global. **Subsea cables off Perth.** Repair work on the Indigo West and Indigo Central cables continues, with the marine operator's estimated completion date falling today. Both systems took shunt faults in close succession over the weekend of 8–9 August, inside Australia's federally declared Submarine Cable Protection Zone, and the [Australian Federal Police are assessing a report](https://www.itnews.com.au/news/afp-assessing-report-in-connection-with-perth-cable-faults-628061) in connection with the faults. Traffic on the Perth–Singapore route has been rerouted around the breaks, so the practical effect has been reduced capacity and added latency rather than loss of connectivity. Timelines remain subject to weather and vessel logistics. ([SubTel Forum](https://subtelforum.com/indigo-west-subsea-cable-repairs-underway/)) **AWS Middle East regions.** me-south-1 (Bahrain) remains unavailable and me-central-1 (UAE) is still unable to reliably support customer applications, following physical damage to those facilities earlier this year. Recovery has been measured in months, and AWS continues to advise affected customers to run workloads in other regions. This is a long-standing condition rather than a new event — it is also why some third-party trackers show AWS in a persistent warning state while every other AWS region operates normally. **Twilio.** Regional carrier problems are still open: voice call failures between some Twilio numbers and Brazilian networks (recovering since 25 August), and SMS delivery delays to I.C.E subscribers in Costa Rica and Telefónica subscribers in El Salvador. Bulk Export is degraded. ([status.twilio.com](https://status.twilio.com/)) **Slack.** An issue retrieving historical messages in workspaces with custom data retention policies has been open since 13 August. Login, connectivity, files, huddles and search are all operational. ([slack-status.com](https://slack-status.com/)) **Core infrastructure is green.** AWS globally, Google Cloud, Microsoft Azure, Cloudflare, Akamai, GitHub, OpenAI, Anthropic and Discord all report normal service. Cloudflare has scheduled datacenter maintenance in progress in Chicago, Montréal and Hamburg, with a wider maintenance window running 27 August to 2 September. Akamai is monitoring a reporting-data issue in its Traffic by Hostname report after deploying a fix on 25 August. There is no sign of a broad routing, DNS or root-server problem. **Resolved in the past 72 hours.** GitHub Actions start delays on 24 August, affecting about 3.8% of runs for 31 minutes; elevated model errors and intermittent login failures at Anthropic on 24–25 August; a DigitalOcean cloud control panel and API disruption on 24–25 August; and several short Cloudflare incidents in Los Angeles and Chicago on 24–25 August. **Elsewhere.** Small, localized report spikes appeared for Sky Broadband in the UK, NTT Docomo in Japan and Indosat IM3 in Indonesia in the early hours of 26 August, and for AT&T on 25 August. Facebook drew a modest volume of user reports, mostly about ad delivery and slow loading, with no acknowledged Meta incident. The Internet Society counts 11 government-ordered internet shutdowns in force worldwide, including the ongoing blackout in Iran. **Coverage note.** The Heroku, Stripe and Azure DevOps status pages did not render for automated retrieval this run, so those three are unverified; no independent signal suggested problems at any of them.

No internet-wide disruption today. Two provider incidents are worth knowing about, one still open and one recovering. Cloudflare — increased CDN latency (ongoing, minor). Cloudflare opened an incident at 20:38 UTC on August 24 for latency increases affecting a subset of requests through its CDN/Cache service. The cause was identified by 22:24 UTC and a fix was being implemented; as of 08:50 UTC today the incident is still marked Identified with the fix in progress, so it has been open for roughly 14 hours. Cloudflare rates the impact as minor and there is no sign of widespread reachability failures — this is slower responses for some requests, not sites going dark. Source: https://www.cloudflarestatus.com/ DigitalOcean — Cloud Control Panel and API outage (recovering). Starting 17:14 UTC on August 24, DigitalOcean's public API returned elevated 5xx errors for all requests and cloud.digitalocean.com was unreachable for many users; Serverless Inference users also saw 403 and 503 errors. A mitigation at 19:14 UTC restored access, but the problem recurred at 22:27 UTC with elevated latency and intermittent errors. A further mitigation at 00:54 UTC today restored the panel and API, and the incident remains in monitoring. This was a control-plane outage: customers could not manage or create resources, but existing Droplets and workloads kept running. Source: https://status.digitalocean.com/ Recently resolved (past 72 hours): - Anthropic: a major incident with elevated errors on Claude Mythos 5, Fable 5 and Opus 5 ran from about 05:00 to 08:30 UTC on August 24 and cascaded downstream — GitHub Copilot and Cursor both logged degraded Claude model availability in the same window. Resolved. https://status.claude.com/ - GitHub: Actions run-start delays on August 24 (3.8% of runs delayed more than 5 minutes, 1.25% failed outright), caused by a disk failure on a service node; resolved 14:04 UTC. https://www.githubstatus.com/ - Akamai: edge delivery issues in India from August 22 to 24, attributed to a third-party connectivity provider; resolved 18:50 UTC on August 24. A separate reporting-data issue affecting the "Traffic by Hostname" report is still under mitigation. https://www.akamaistatus.com/ - Zoom: short meeting-chat and AI API degradations on August 24, each resolved within about an hour. Still open but narrow: Slack continues to work through an incident that began August 13 in which workspaces with custom data-retention policies could not load older messages; retention jobs are being gradually restored from backups. Twilio is tracking SMS delivery delays to several individual carriers (Costa Rica, Dominican Republic, El Salvador, Kosovo, and some small US carriers) — carrier-side issues affecting delivery to those networks only. All clear at AWS, Google Cloud, Microsoft Azure, Azure DevOps, OpenAI, Discord, Atlassian, Vercel, Heroku, Stripe, and the AI platforms we checked (Cursor, Groq, Replicate, ElevenLabs, Cohere, Stability AI). Meta's products are operating normally. Crowd-sourced outage trackers show no elevated reports for any major platform, and we found no BGP, DNS or undersea-cable incidents today. Overall status: incidents detected — none widespread.

The internet is broadly healthy today. AWS, Google Cloud, Azure, Azure DevOps, Cloudflare, GitHub, OpenAI, Meta, Stripe, Vercel, Heroku, Discord and Atlassian all report normal operations. There is no sign of an internet-wide event — no significant BGP leak, no submarine cable break, no DNS failure. ACTIVE: ELEVENLABS MEDIA DELIVERY ElevenLabs is investigating media that will not load across Studio, Audiobooks, Image & Video, Music and Dubbing. Both its ElevenAPI and ElevenCreative components are marked degraded. The incident opened at 08:49 UTC and, as of this report, has neither a cause nor a resolution. Source: https://status.elevenlabs.io/ ACTIVE, NARROW SCOPE • Twilio has four open issues — three carrier-specific SMS delivery delays (ICE Costa Rica, Dukagjini Kosovo, Telefónica El Salvador) and one where recently upgraded accounts are still hitting trial-account restrictions. Twilio's Carrier Network and Developer Tools sections show degraded performance; the core APIs do not. Source: https://status.twilio.com/ • Slack has carried a minor incident since August 13: workspaces with custom data retention policies have trouble reaching historical messages. Messaging and workspace administration are flagged; login, files, huddles, search and apps are not. Source: https://slack-status.com/ • Akamai's edge delivery problems in India, open since August 22, are in monitoring after a fix. Akamai has ruled out the third-party provider it initially suspected. Source: https://www.akamaistatus.com/ • DigitalOcean is running extended Spaces maintenance in London, Singapore and Sydney, with brief interruptions possible. Planned work, not an outage. THE DAY'S CROSS-PROVIDER STORY: AI MODEL ERRORS Overnight, Anthropic logged elevated errors on requests to Claude models including Opus 5 and Fable 5, from 9:50pm to 12:36am PT. The same window showed up downstream at two other vendors: GitHub reported reduced Copilot availability for the Fable model "due to an upstream provider," and Cursor reported elevated Claude Opus 5 errors from 05:38 to 08:51 UTC. All three are resolved. It is a useful reminder that AI coding tools now share a small number of model backends, so one provider's bad hour becomes several products' bad hour. RESOLVED IN THE LAST 72 HOURS • Cloudflare: Durable Objects and D1 degraded in Hong Kong and Singapore, and elevated HTTP 5xx errors in Chicago. Both minor, both resolved earlier today. Maintenance continues in Ashburn, Montréal and Astana. • Zoom: roughly 40 minutes of degraded meeting chat today, resolved. • GitHub: on August 21, SSH Git operations fell below 95% success for about four minutes, and Copilot agent task creation failed intermittently. Git over HTTPS was unaffected. • DigitalOcean: a significant interruption in the MKC1 region on August 19 affecting GPU Droplets is largely restored, with GPU node recovery continuing. ONE SOURCING CAVEAT AWS's public RSS feed is currently serving stale March 2026 entries, so today's AWS read comes from the Health Dashboard and secondary reporting rather than the feed. Neither showed an open broad event. Third-party monitors noted a short AWS warning window on August 23 that we could not corroborate against AWS's own dashboard, so we are not treating it as a confirmed incident. Overall: incidents detected, none widespread. The internet is up.

The internet is operating normally today. We found no widespread outage, routing failure, or DNS disruption across the providers we monitor. A handful of narrower incidents are worth noting. Akamai — Edge Delivery issues in India. Akamai began investigating around 11:40 UTC and attributed the disruption to a third-party service provider. A fix has been implemented and the incident is now in a monitoring state, with service resuming normal operation. Akamai is separately reporting degraded performance on its Data Services and Reporting components. This was the day's most substantive infrastructure item, but the impact was regional rather than global. (akamaistatus.com) Slack — an incident open since August 13 continues to affect access to historical messages for workspaces that have custom data retention policies enabled. Messaging and workspace/org administration are flagged; login and SSO, connectivity, files, huddles, search, and workflows are normal. Narrow in scope, but still unresolved after nine days. (slack-status.com) Twilio — several country-specific SMS delivery problems remain open, including delivery delays to Telefonica El Salvador, delivery failures to Dukagjini in Kosovo, and delayed delivery receipts to ICE in Costa Rica. A scheduled London (IE1) maintenance window affecting Voice, Messaging, Authentication, and Interconnect also ran through the day. Earlier SMS issues in Bulgaria, Oman, and Vietnam were resolved. (status.twilio.com) Everything else we track reports normal operation: Cloudflare, Google Cloud, Microsoft Azure, GitHub, OpenAI, Anthropic, Discord, Atlassian, Zoom, Vercel, Heroku, DigitalOcean, Stripe, and the AI platforms on our list (Cursor, Groq, Replicate, ElevenLabs, Cohere, Stability AI). Cloudflare resolved a minor network connectivity issue in Dubai (DXB) at 02:57 UTC. One caveat on crowd-sourced signal: third-party report trackers showed small spikes for Cloudflare and X during the afternoon. Neither company confirmed an incident, and we found no corroborating evidence, so we are treating those as unverified user-report noise rather than real events. Recently resolved, past 72 hours: DigitalOcean restored Container Registry and Spaces access on August 21 after customers were unable to push or pull images, and recovered its MKC1 region on August 19 following an interruption to GPU Droplets, Kubernetes nodes, and serverless inference. Zoom resolved a brief Canvas outage in its US region on August 21 and a file-search problem in Zoom Hub on August 22. GitHub resolved intermittent failures creating Copilot Cloud Agent tasks on August 21. A note on sourcing: the AWS Health Dashboard renders through JavaScript and did not return readable content to us this run. We found no news reports or corroborating signals pointing to an AWS incident, and the aggregator flags we did see for AWS look like stale component noise rather than a live event — but our AWS read today is indirect rather than directly confirmed. Overall: incidents detected, none internet-wide.

No internet-wide disruption today. The major cloud, CDN, and platform providers are largely operating normally, with a handful of service-specific incidents open and no new BGP routing or submarine cable faults detected. Active incidents Akamai has Data Services and Reporting degraded, with a data-availability issue affecting "Traffic by Hostname" reporting. Root cause was identified on August 20 at 18:32 UTC and mitigation remains in progress. Content delivery itself is unaffected. Source: https://www.akamaistatus.com/ Slack continues an incident open since August 13: channels in workspaces with custom data retention policies cannot serve historical messages. Retention settings have been restored, but the retention jobs themselves remain on hold. Source: https://slack-status.com/ Twilio is partially degraded, affecting Bulk Export, some carrier lookups, and Zipwhip toll-free SMS to North America. Two separate issues resolved today: Japan voice services and Altan Redes SMS in Mexico. Source: https://status.twilio.com/ Zoom reports degradation in its Meta integration for Zoom CX third-party clients, with the root cause identified. Source: https://www.zoomstatus.com/ Long-running conditions AWS me-south-1 (Bahrain) remains unavailable and me-central-1 (UAE) remains impaired, both dating to conflict-related infrastructure damage in late March 2026. AWS has indicated restoration is measured in months rather than days. This was verified against independent reporting rather than the status feed alone. Source: https://health.aws.amazon.com/health/status Resolved in the past 72 hours Google Cloud cleared a us-west1 incident on August 20 that ran 3 hours 40 minutes and touched more than 26 products. GitHub resolved a Copilot Cloud Agent degradation spanning August 20 and 21. Cloudflare closed a cluster of short regional incidents. Anthropic resolved model and connector errors on August 20. DigitalOcean restored Container Registry and Spaces, with GPU Droplets in MKC1 still recovering. AWS cleared a Connect metrics issue in ap-northeast-1. Operating normally Microsoft Azure, Azure DevOps, OpenAI, Discord, Atlassian, Vercel, Heroku, Stripe, Cursor, Groq, Replicate, ElevenLabs, Cohere, Stability AI, and Meta all report all-clear. Bottom line: the internet is up. Today's open issues are service-specific rather than internet-wide.

No widespread internet disruption today. The major cloud, CDN, and platform providers are largely operating normally, though a handful of regional and service-specific incidents are open. Active incidents Cloudflare is monitoring two minor regional incidents: increased errors for Durable Objects and downstream services in Indonesia (opened 13:49), and network performance issues in India (opened 12:01). Both are classified as minor and are in the monitoring stage. A planned maintenance window at the Chicago (ORD) facility is also in progress. Source: https://www.cloudflarestatus.com/ OpenAI is investigating errors affecting some users of Thinking in ChatGPT. The incident was opened very recently and the impact scope has not yet been stated. Source: https://status.openai.com/ Twilio reports SMS delivery delays from a subset of Twilio short codes to T-Mobile US subscribers. The SMS short code and toll-free components in North America are showing degraded performance. Source: https://status.twilio.com/ Slack has an open incident affecting access to historical messages in workspaces with custom data retention policies enabled, ongoing since August 13. All other Slack components are operational. Source: https://slack-status.com/ Akamai is continuing to monitor its Certificate Provisioning System after Control Center UI timeouts and API errors on August 19 between 03:12 and 03:34 UTC. Normal operations have resumed. Source: https://www.akamaistatus.com/ AWS Middle East (UAE), region me-central-1, remains impaired, and AWS continues to advise customers to run workloads in other regions. This is a long-running condition dating back to the March 1 physical damage to two of the region's three availability zones, not a new development today. All other AWS regions are operating normally. Source: https://health.aws.amazon.com/health/status Resolved in the past 72 hours Fastly resolved a global CDN performance impact spanning August 19 and 20 that affected multiple POPs, during which some purge requests were lost between 17:02 and 23:24 UTC. A separate reduced cache performance issue affecting Compute customers was also resolved earlier today. GitHub resolved a significant 7 hour 47 minute degradation on August 17 that caused elevated errors and latency across Issues, Pull Requests, APIs, Actions, and Copilot, peaking near 20 percent web and API error rates. GitHub attributed it to load balancer network saturation in its Central US datacenter combined with a sidecar pod that failed to scale. DigitalOcean cleared an August 19 issue in its MKC1 region affecting GPU Droplets. AWS resolved elevated EC2 instance launch errors in a single London (eu-west-2) availability zone on August 19. Cloudflare also resolved network performance degradation in Singapore and elevated error rates in its Chicago region. Operating normally Google Cloud, Microsoft Azure, GitHub, Discord, Atlassian, Vercel, Heroku, DigitalOcean, Zoom, Stripe, and X all report all-clear. Crowd-sourced outage report volumes show no unusual spikes, and we identified no significant BGP routing or DNS incidents. Bottom line: the internet is up. Today's open issues are regional or service-specific rather than internet-wide.

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.

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.