Internet & cloud outages — July 2026

The internet is healthy today. All core infrastructure checks came back clean: AWS, Google Cloud, Microsoft Azure, Azure DevOps, Cloudflare, Akamai, GitHub, OpenAI, Discord, Atlassian, Slack, Zoom, Vercel, Heroku, DigitalOcean, Stripe, Meta, and X all report normal operations, and crowd-sourced outage trackers show no unusual report spikes. No BGP, DNS, or routing anomalies were flagged. Minor items, none internet-impacting: Twilio is working through a set of localized carrier-route degradations affecting SMS and voice delivery to specific carriers in Angola, Brazil, Cambodia, El Salvador, Guatemala, India, and Puerto Rico. Fastly logged a brief (~3-minute) warning affecting API and configuration management services early this morning, now resolved, and has rerouted traffic around its Port Blair (IXZ) location. Recently resolved (past 72 hours): on July 27, T-Mobile US suffered a mobile network outage peaking above 220,000 reports before service was restored the same day, and Meta's Facebook, Instagram, and Messenger saw a global disruption that was also resolved the same day. Both have remained stable since. Sources: provider status pages (status.cloud.google.com, azure.status.microsoft, www.cloudflarestatus.com, www.githubstatus.com, status.twilio.com, and others) and crowd-sourced outage trackers.

No meaningful internet-wide issues were detected today. All major cloud, CDN, and platform providers are reporting normal operations. We checked status pages across the board — AWS, Google Cloud, Microsoft Azure, Cloudflare, Fastly, Akamai, GitHub, OpenAI, Discord, Atlassian, Slack, Zoom, Vercel, Heroku, DigitalOcean, Stripe, Twilio, Meta, and X — and nearly everything is green. A few minor, localized notes: - Cloudflare briefly reported network congestion in North America early today, caused by a fiber provider's maintenance; it has been resolved (cloudflarestatus.com). Routine scheduled maintenance continues at several Cloudflare data centers (Ashburn, Dallas, Miami, Barcelona) with possible slight latency increases. - Twilio is reporting carrier-specific SMS and voice degradations affecting a handful of international carriers (Cambodia, Puerto Rico, Angola, Zambia, India, Guatemala). These are localized to those carrier networks, not a platform-wide outage (status.twilio.com). Recently resolved (past 72 hours): - GitHub Actions saw delays for about 2% of workflows on July 29 due to under-provisioned infrastructure; resolved (githubstatus.com). - Stripe had elevated card authorization errors for about an hour on July 29; resolved. - Discord resolved a brief login and DM delivery issue on July 27. - Akamai resolved NetStorage issues in Europe on July 29. Crowd-sourced outage trackers show no unusual spikes today. Separately, roughly a dozen government-ordered internet shutdowns remain in effect around the world (per Internet Society Pulse) — policy actions rather than technical failures. Bottom line: the internet is up.

No widespread internet disruption is underway as of roughly 12:15 UTC on July 29, 2026. All major cloud providers, CDNs, and large platforms report normal operations, and crowd-sourced outage trackers show no significant spikes. Core infrastructure AWS reports no open service events. Google Cloud shows "no broad severe incidents" as of 05:11 PDT. Microsoft Azure lists no active events, with all regions reporting good health. Cloudflare, Fastly, and Akamai are operational, as are GitHub, OpenAI, and Discord. Cloudflare does have scheduled datacenter maintenance in progress at Ashburn (IAD), Dallas (DFW), and Miami (MIA). Traffic is being rerouted, which may add small amounts of latency for users near those locations. This is planned work, not an outage. Platforms Slack, Atlassian, Vercel, DigitalOcean, Stripe, and Heroku all report normal operations. Zoom lists one minor degradation affecting a marketplace integration, which it says has been mitigated. Twilio is working through several carrier-specific voice and SMS delivery problems affecting individual international carriers, including voice call failures to Reliance Jio in India that have been open since July 17. These are narrow carrier routing issues rather than a platform outage. X's public status page is not currently serving data, so we could not verify it directly. Crowd-sourced trackers show no elevated reports for the service. Routing and DNS No BGP hijacks, route leaks, or significant DNS failures were reported in the past 24 hours. Recently resolved (past 72 hours) - July 27: A widespread T-Mobile US mobile network outage peaked at more than 220,000 reports on Downdetector. Resolved. - July 27: Meta platforms (Facebook, Messenger, Instagram) were disrupted globally for roughly one to two hours, affecting users in the US, UK, Europe, India, Japan, and Australia. Resolved. - July 27: Discord login sessions and direct message delivery failed. Resolved. - July 27: Akamai Bot Manager false positives. Resolved. - July 28: Cloudflare Tunnel connectivity problems. Resolved. - July 28: DigitalOcean Agent Platform returning HTTP 500 errors. Resolved. - July 29: Cloudflare network congestion on the Singapore-Tokyo path. Resolved. Bottom line The internet is up. Nothing today rises above routine maintenance and narrow, provider-specific issues. Sources checked: AWS Health Dashboard, Google Cloud Service Health, Azure Status, Cloudflare Status and Radar, Fastly Status, Akamai Status, GitHub Status, OpenAI Status, Discord Status, Slack Status, Atlassian Status, Zoom Status, Vercel Status, Heroku Status, DigitalOcean Status, Stripe Status, Twilio Status, and istheservicedown.com.

The internet is operating normally this morning. Core cloud providers, CDNs and major platforms are reporting healthy status, following two significant but now-resolved outages yesterday. ## Recently resolved (past 72 hours) **T-Mobile US — July 27.** A widespread US mobile network outage began around 1:23 p.m. PT, peaking at more than 220,000 reports on Downdetector. Customers lost voice, SMS and data service, with many iPhones showing "SOS" mode, and T-Mobile 5G Home Internet was also affected. T-Mobile confirmed services were fully restored later the same day. The company has not yet published a root-cause explanation. **Meta (Facebook, Instagram, Messenger) — July 27.** A global disruption made Facebook and Messenger inaccessible for users across the US, UK, Europe, India, Japan and Australia, with Instagram also affected. Users saw "Sorry, something went wrong" errors. Reports declined within roughly one to two hours and the platforms have since recovered. ## Active today — minor and localized - **Cloudflare:** Network performance issues in Istanbul, cause identified and a fix being implemented. Scheduled datacenter maintenance is also in progress at Phoenix, Kansas City, Dallas, Atlanta and Berlin. Global services remain operational. ([status](https://www.cloudflarestatus.com/)) - **DigitalOcean:** Agent Platform requests returning HTTP 500 errors since July 27, 18:31 UTC. Agentic Inference Cloud and Agent Runtime show partial outage; Droplets, Kubernetes, databases and networking are unaffected. ([status](https://status.digitalocean.com/)) - **Slack:** Feature degradation affecting receipt of emails in Slack. Messaging, connectivity, huddles and search are normal. ([status](https://slack-status.com/)) - **Twilio:** Several regional carrier-level issues, including voice call failures to some US numbers, SMS delays in Angola, and ongoing Reliance Jio voice problems in India since July 17. ([status](https://status.twilio.com/)) - **AWS:** No new events. The Middle East regions ME-CENTRAL-1 (UAE) and ME-SOUTH-1 remain degraded from infrastructure damage first reported April 30; AWS continues to advise migrating workloads to other regions, with recovery expected to take months. ([status](https://health.aws.amazon.com/health/status)) ## All clear Google Cloud reports no broad severe incidents. Microsoft Azure shows no active events, and Azure DevOps is healthy across all geographies. GitHub, OpenAI, Discord, Akamai, Atlassian, Zoom, Vercel and Heroku all report full operational status. ## Notes on data quality We were unable to retrieve Fastly and Cloudflare Radar status pages this run (both returned HTTP 403), and the Stripe status page did not render. No third-party reports of problems at those providers were found, but we cannot independently confirm their state. The X/Twitter status hostname did not resolve. **Bottom line:** no widespread internet disruption right now. Yesterday's two large consumer-facing outages have been resolved, and the remaining issues are small, provider-specific and being worked on.

No internet-wide disruption is underway. Core cloud, CDN, and routing infrastructure is healthy, but a handful of individual providers are working through degradations. What's active right now: • OpenAI — An incident affecting ChatGPT conversations with elevated error rates opened late on July 27. Mitigation has been applied and OpenAI is monitoring recovery. This follows a cluster of shorter error-rate incidents on July 24–25 that were all resolved. (https://status.openai.com) • Zoom — Degraded performance across several features, including offline meeting transcription in the US region, Zoom AI Companion components, My Notes, and Zoom Phone devices. Zoom says root cause is identified and a fix is in progress. Core meetings remain usable. (https://www.zoomstatus.com) • Twilio — Regional carrier-level problems rather than platform failures: SMS delays and failures to Mascom and Orange subscribers in Botswana, voice call failures to Claro in Guatemala, and ongoing voice delivery failures to Reliance Jio in India. (https://status.twilio.com) • Cloudflare — The Dallas (DFW) data center is in a scheduled maintenance window (06:00–12:00 UTC), with traffic rerouted and a possible slight latency increase regionally. This is planned work, not an incident. (https://www.cloudflarestatus.com) Core infrastructure all-clear: Amazon Web Services, Google Cloud, and Microsoft Azure report no active events. Akamai, Fastly, GitHub, Discord, Slack, Atlassian, Vercel, Heroku, DigitalOcean, and Stripe are all operational. We found no evidence of BGP hijacks or route leaks, no DNS resolver problems, and no new submarine cable faults affecting global connectivity. Resolved in the last 72 hours: • Akamai mitigated a Bot Manager false-positive issue at 01:30 UTC on July 27; normal operation has resumed. • GitHub resolved degraded GraphQL API performance earlier on July 27, plus Actions run failures on July 25 and a broader multi-service degradation on July 24. • Stripe cleared elevated API errors on July 24. • DigitalOcean traced a July 24 connectivity issue for some India-based users reaching NYC resources to an internal Airtel network problem, not DigitalOcean infrastructure. Consumer-level reports: Crowd-sourced trackers show localized ISP complaint spikes today — Spectrum in the United States beginning around 3:19 a.m. Eastern, Vodafone in Australia, and Biznet in Indonesia. These are regional access issues affecting individual providers' subscribers and are not connected to a broader infrastructure failure. One note on sourcing: the AWS public RSS feed remains stale, with its newest entries dated April 2026. Our AWS assessment relies on the health dashboard and corroborating signals rather than that feed. Bottom line: The internet is up. If you're seeing problems today, the most likely explanations are your own ISP, or one of the specific services listed above.

The internet is up. Core infrastructure is healthy today, but a handful of named incidents are active — most visibly an OpenAI/ChatGPT disruption that is now in recovery. **Active incidents** **OpenAI / ChatGPT** — OpenAI's status page lists an open incident, "Elevated errors affecting ChatGPT conversations," currently in the Monitoring phase. OpenAI states: "Mitigation has been implemented, and we are monitoring the recovery of ChatGPT conversations." Press coverage of the disruption described users worldwide hitting login failures, missing conversations and error messages across the ChatGPT website and mobile app, with OpenAI's API and Codex also affected at the peak. The incident is trending toward recovery rather than worsening. (https://status.openai.com/) **Twilio** — Three open, carrier-level incidents: SMS delivery failures from the US to a subset of Twilio short codes; delayed SMS delivery receipts to Claro Guatemala; and voice call failures to Reliance Jio subscribers in India. Twilio has identified the cause on the latter two. Impact is narrow and route-specific rather than platform-wide. (https://status.twilio.com/) **Vercel** — The Vercel Community forums are unavailable for maintenance. Hosting, builds and edge delivery are unaffected. (https://www.vercel-status.com/) **Ongoing background: AWS Middle East** — The AWS Middle East (UAE) me-central-1 and Middle East (Bahrain) me-south-1 regions remain degraded following physical damage to facilities earlier this year. AWS has said recovery is expected to take months and advises affected customers to run workloads in alternate regions. This is a long-running situation, not a new event today, but it continues to affect customers anchored to those two regions. **All clear** Google Cloud reports no broad severe incidents. Microsoft Azure shows no active events, with all regions green. Cloudflare, Akamai and Fastly report normal edge delivery. GitHub, Discord, Atlassian, Slack, Zoom, Heroku, DigitalOcean and Stripe are all fully operational. Cloudflare's status page lists its usual scattering of single-datacenter partial outages and scheduled maintenance windows — routine traffic re-routing that is part of normal operation, not a service incident. **Recently resolved (past 72 hours)** Akamai resolved edge delivery issues on July 24. DigitalOcean resolved a network connectivity problem on the India-to-NYC path on July 24. GitHub cleared its open incidents on July 25. An Azure West US connectivity and latency incident on July 23 ran from 14:44 to 19:41 UTC and is closed. **Assessment** Status: incidents-detected. The issues in play are single-provider and, in Twilio's case, route-specific. There is no evidence of BGP instability, DNS failure, submarine cable damage or multi-provider correlation. Routing and naming infrastructure look normal. One caveat on completeness: Downdetector and Fastly's status page both blocked automated requests this run, and Meta's status page did not return readable content. Fastly was confirmed clear via secondary sources; the crowd-sourced signal for this run is thinner than usual.

No widespread internet disruption is in progress. Core infrastructure — the major cloud regions, CDNs, and public DNS — is operating normally. A few narrower issues remain open, and GitHub is recovering from an unusually busy 24 hours. **What is active right now** Twilio is the main open item. Its status page lists SMS delivery delays and failures from US carrier networks to a subset of Twilio short codes (under investigation since July 24), voice call failures to Reliance Jio and other Indian networks (cause identified, fix in progress since July 17), and delayed delivery receipts for Claro Guatemala subscribers. These are carrier-level problems affecting messaging and voice traffic rather than general web access. See [status.twilio.com](https://status.twilio.com/). Cloudflare's dashboard shows its usual scattering of partial outages at small edge locations, where traffic is automatically re-routed to nearby data centers. This is normal background state for a network of that size and is not a service-wide problem. **Resolved in the past 72 hours** GitHub had a difficult stretch and has now fully recovered. Today it reported degraded availability across several GPT models in Copilot between 09:42 and 10:11 UTC, which it attributed to an issue with an upstream model provider, plus a short Actions queueing delay earlier in the morning. On July 24 it saw a critical failure creating pull requests (19:37–20:23 UTC) and a broader disruption touching the API, Issues, Actions, Pages, and Copilot (16:17–17:36 UTC). Separately, an abuse-mitigation change incorrectly blocked some legitimate traffic through GitHub's Central Europe and South America edge locations from 18:45 UTC on July 23 until 11:19 UTC on July 24. All are marked resolved at [githubstatus.com](https://www.githubstatus.com/). AWS resolved a connectivity event on the morning of July 24 (roughly 04:40–06:01 PDT). Akamai mitigated an edge delivery issue causing latency and 5xx errors on July 24 at 12:00 UTC, traced to a third-party provider. DigitalOcean cleared a routing problem affecting traffic from India to its NYC region, limited to Airtel subscribers. Sony's PlayStation Network had a multi-hour global outage on July 24 affecting sign-in, multiplayer, and the store; services have been restored. **A note on unverified reports** At least one outlet published a story today describing a global, ongoing ChatGPT outage and stating that OpenAI had acknowledged elevated error rates on its dashboard. We could not substantiate this. OpenAI's status page reports all systems operational with no ongoing incidents or affected components, and both chatgpt.com and the OpenAI API responded normally to our checks. GitHub's brief Copilot model degradation this morning does point to a real upstream model-provider hiccup in an overlapping window, but we found no evidence of a broad or continuing ChatGPT outage. Treat that report with caution. **Everything else checked** Operating normally: [AWS](https://health.aws.amazon.com/health/status), [Google Cloud](https://status.cloud.google.com/) (no broad severe incidents), [Azure](https://azure.status.microsoft/status) (no active events), [Cloudflare](https://www.cloudflarestatus.com/), [Akamai](https://www.akamaistatus.com/), [OpenAI](https://status.openai.com/), [Discord](https://discordstatus.com/), [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/), [Stripe](https://www.stripestatus.com/), and Meta. Public DNS resolvers (1.1.1.1, 8.8.8.8, 9.9.9.9) answered in 31–39 ms, and no significant BGP hijacks or route leaks surfaced in our checks. Two sources could not be read this run: Fastly's status page and API returned HTTP 403, and Downdetector blocked automated access. We saw no independent signal of problems at either provider, but our Fastly coverage today is incomplete. **Bottom line:** the internet is up. Expect messaging delays if you send SMS to US short codes or place voice calls into India via Twilio; otherwise things are quiet.

The internet is operating normally today. Core infrastructure — major cloud providers (AWS, Google Cloud, Microsoft Azure), CDNs (Cloudflare, Akamai), DNS, and BGP routing — is healthy, with no signs of widespread disruption or undersea cable issues. A few minor, contained incidents are worth noting: - OpenAI reported elevated error rates across its APIs and ChatGPT. Engineers have applied a mitigation and are monitoring recovery. - Slack flagged an issue sending messages to channels via certain Workflows; the rest of the platform (messaging, login, calls) is operating normally. - Twilio is working through several carrier- and region-specific messaging and voice issues, typical of its distributed carrier footprint rather than an internet-wide problem. - EA Sports FC servers saw a login and connectivity spike overnight tied to a scheduled maintenance window (06:00–07:00 UTC); service has largely recovered. Cloudflare has routine scheduled maintenance in progress at its Kansas City and Dallas datacenters, which may cause brief latency in those regions. GitHub, Discord, Atlassian, Vercel, DigitalOcean, and Zoom are all operational. Recently resolved: Meta (Facebook, Instagram, WhatsApp) experienced a roughly one-to-two-hour global outage on July 22 affecting users in the US, UK, and Europe; platforms have since stabilized. A brief Azure incident in the West US region on July 23 has also been resolved. Bottom line: no meaningful internet-wide disruption. A small number of single-provider incidents are being actively worked and are trending toward recovery.

The internet is operating normally today. Core cloud providers (AWS, Google Cloud, Microsoft Azure), major CDNs (Cloudflare, Fastly, Akamai), and major platforms (Slack, Zoom, Discord, Atlassian, Stripe, Vercel, Heroku, DigitalOcean, OpenAI) all report healthy status. No BGP routing incidents, DNS failures, or undersea cable events have been detected. Recently resolved: Meta suffered a global outage on Wednesday, July 22, starting around 13:00 GMT. Facebook, Instagram, and WhatsApp were unreachable or degraded for millions of users across Europe, the UK, the US, and other regions, with many users logged out or shown "account temporarily unavailable" errors. Service recovered within one to two hours, and Meta platforms have been stable since — notably, this was the second Meta disruption in 72 hours, following a smaller wave of reports on July 19. Analysts pointed to a possible DNS-related root cause, though Meta has not confirmed details. Separately, GitHub resolved a latency incident this morning affecting Webhooks, Pull Requests, Issues, and Actions, with recovery by 09:39 UTC (https://www.githubstatus.com). Minor ongoing items, localized and not internet-wide: Cloudflare continues to investigate degraded availability for specific Workers AI models, an issue open since mid-June (https://www.cloudflarestatus.com). Twilio reports regional telecom issues — voice call failures to subscribers in India (ongoing since July 17), SMS delivery delays involving Romania, and degraded voice performance in parts of APAC (https://status.twilio.com). Localized ISP-level connectivity problems were also reported in the Houston, Texas area on July 22.

The internet is healthy today. Core infrastructure is operating normally worldwide, with a handful of minor, provider-specific incidents — none affecting general connectivity. OpenAI / ChatGPT — active incident: elevated errors affecting file uploads and image generation in ChatGPT, ongoing for several hours as of this check. OpenAI reports a mitigation has been applied and recovery is being monitored (status.openai.com). The API, Codex, and other OpenAI services are unaffected. Twilio — three minor regional telephony issues: SMS delivery delays and failures from Twilio to MPT Myanmar subscribers (investigating, since July 21), SMS delivery failures from network subscribers to Twilio Romania numbers (cause identified, since July 21), and voice call failures from Twilio numbers to Reliance Jio India (cause identified, since July 17) (status.twilio.com). Cloudflare — the status page shows a minor indicator tied to a long-running Workers AI degradation affecting two specific AI models (since June 16); core CDN, DNS, and API services are operational. Several edge locations are in routine scheduled maintenance windows today (including London, Ashburn, and Oslo) with traffic rerouted as normal (cloudflarestatus.com). All clear elsewhere: AWS, Google Cloud, Microsoft Azure, Azure DevOps, GitHub, Discord, Slack, Zoom, Vercel, Heroku, DigitalOcean, Atlassian, and Stripe all report normal operations. Crowd-sourced outage trackers show no unusual report spikes, and no BGP, DNS, or routing anomalies were flagged today. Context from the past week (both fully resolved): Cloudflare's 1.1.1.1 public DNS resolver outage on July 14 (a route-withdrawal configuration error, not a BGP hijack, per Cloudflare's post-mortem) and a Google Cloud europe-west4-a power and cooling incident on July 15–16 affecting VMware Engine, Bare Metal Solution, and NetApp Volumes. Monitoring notes: Fastly's status page blocked our automated checker this run (HTTP 403), and Meta's and X's status pages could not be read; however, crowd-sourced trackers showed no elevated reports for any of these services.

No internet-wide disruption is underway right now. Checks across crowd-sourced outage trackers and the status pages of the major cloud, CDN, DNS and platform providers show core infrastructure operating normally as of the morning of July 21, 2026. All clear: Google Cloud, Microsoft Azure, GitHub, OpenAI, Discord, Slack, Atlassian, Vercel, DigitalOcean and Heroku all report full operational status with no active incidents. Ongoing — AWS Middle East. The AWS ME-CENTRAL-1 (UAE) and ME-SOUTH-1 (Bahrain) regions remain unavailable. These are not new failures: both regions were physically damaged in early March 2026 when data centre facilities were struck during regional conflict, and AWS has said restoration would take several months. Both events are still listed as open on the AWS Health Dashboard, and AWS continues to advise customers to run disaster-recovery plans and shift workloads to alternate regions. Customers outside those two regions are unaffected. (https://health.aws.amazon.com/health/status) Minor and localised issues. Cloudflare has routine scheduled datacentre maintenance in progress in Baghdad and Dubai, which can cause brief latency increases as traffic reroutes, and continues to investigate degraded availability for two Workers AI models — an issue open since June 16 that does not affect CDN, DNS or WAF delivery (https://www.cloudflarestatus.com/). Akamai is still monitoring an Application Load Balancer reporting issue that it describes as stable, with all delivery and security services operational. Twilio reports carrier-level SMS and voice delivery problems in Mexico, Malawi and India; these originate in third-party mobile networks rather than Twilio's own platform. Resolved in the past 72 hours. Meta suffered a broad but short outage on July 19, with Facebook, Instagram and Messenger returning account-unavailable errors for users across North America, Europe and India starting around 03:25 ET; service was largely restored within one to two hours. GitHub resolved a disruption affecting one Copilot model on July 20. DigitalOcean cleared block-storage attachment problems across several regions and an outbound connectivity issue in Bangalore on July 19, and Akamai resolved an Edge Delivery issue affecting India the same day. One caveat on completeness: Downdetector and Cloudflare Radar both refused automated requests during this run, so the crowd-sourced picture is drawn from secondary trackers and news reporting rather than primary dashboards. Nothing in those secondary sources indicates a significant unreported event. Bottom line: the internet is up. There is no active multi-provider or internet-wide outage. The AWS Middle East regional outage remains the one substantial open item, and it is a known, geographically contained, long-running recovery rather than a developing incident.

No major internet-wide outages are ongoing as of this morning (July 20, 2026). Core cloud and CDN providers — AWS, Google Cloud, Microsoft Azure, Cloudflare, Fastly, and Akamai — are reporting healthy core services, and crowd-sourced outage trackers show no unusual report spikes. GitHub Actions recovered overnight. GitHub experienced degraded performance starting at 23:34 UTC on July 19, with Actions workflow runners unavailable for an extended period and knock-on effects on API requests, Issues, Pages, and Git LFS. Recovery began around 03:27 UTC and GitHub declared full resolution at 04:44 UTC today (githubstatus.com). Smaller active items we are watching: - Twilio has several open regional incidents: voice call post-dial delay to Germany, SMS delivery failures to Altan Redes (Mexico) and Pelephone (Israel, recovering), and voice call failures to Reliance Jio (India) (status.twilio.com). - Akamai is in monitoring mode on two recovering incidents: edge delivery issues in India (fix implemented July 19) and an Application Load Balancer reporting issue open since July 16 (akamaistatus.com). - Cloudflare continues to investigate degraded availability for two Workers AI models, ongoing since June 16 (cloudflarestatus.com). Recently resolved (past 72 hours): the July 17 AWS us-east-1 operational issue affecting Lambda, CloudFormation, and the Management Console; a July 16 GitHub REST API degradation in which roughly 39% of requests failed for about 90 minutes; a brief worldwide Facebook/Instagram disruption on the morning of July 19; elevated errors in Cloudflare R2 and Durable Objects on July 16; and DigitalOcean networking issues in its Bangalore (BLR1) region on July 19. Bottom line: the internet is up. Activity over the past 72 hours has been routine — isolated, provider-level incidents resolved within hours — with no widespread or multi-provider disruption today.

The internet's core infrastructure is healthy today — no widespread outage is in progress — but a few provider-level incidents are active or recently recovered. GitHub is experiencing an ongoing incident affecting GitHub Actions and API requests (githubstatus.com). Actions is in a partial outage with critical impact and API requests show degraded performance; GitHub is still investigating as of 02:23 UTC. The disruption has knock-on effects: OpenAI reports elevated errors in ChatGPT and Codex workflows that depend on GitHub (status.openai.com), and CI/CD pipelines relying on Actions may see failures or delays. Earlier today, Facebook and Instagram users worldwide reported a brief outage between roughly 3:44 and 5:02 a.m. ET, with more than 23,000 Facebook and 18,000 Instagram problem reports in the US alone before report volumes dropped sharply (cnn.com/2026/07/19/world/facebook-instagram-outages-intl). NetBlocks confirmed the disruption was platform-level, not a country-level internet issue. Service has recovered. Elsewhere, Akamai has two incidents in the monitoring/recovery phase — edge delivery issues in India and an Application Load Balancer reporting issue — both trending toward normal (akamaistatus.com). Cloudflare shows only a minor degradation affecting two Workers AI models, and Twilio lists routine regional carrier-level SMS/voice delays. Recently resolved (past 72 hours): AWS CloudFront suffered a roughly 3.5-hour outage on July 16 tied to a configuration loading failure in its VPC Origins feature, affecting sites including Hugging Face, Canvas, and Ubiquiti — fully recovered. GitHub also resolved a July 17 incident in which about 39% of REST API requests failed. All clear at AWS, Google Cloud, Azure, Azure DevOps, Discord, Atlassian, Slack, Zoom, Vercel, Heroku, DigitalOcean, and Stripe. Crowd-sourced outage trackers show no other elevated reports.

The internet is operating normally today, with no widespread or internet-wide outages detected. No significant BGP routing, DNS, or undersea cable issues have been reported. The most notable recent event is yesterday's AWS incident: on July 17, the us-east-1 (Northern Virginia) region experienced an operational issue affecting multiple services — including AWS Lambda, CloudFormation, Amazon Connect, and the Management Console — causing problems for dependent sites and apps. AWS reported the issue resolved the same day (around 3:42 PM PDT). One follow-on effect is still being worked: inaccurate estimated billing data in the Billing and Cost Management Console, traced to a unit-pricing issue in a billing computation subsystem. AWS expects all affected accounts to be fully recovered by July 19, 12:00 AM PDT (health.aws.amazon.com). Core workloads are running normally. Other minor, localized issues currently being tracked: - OpenAI: some users are unable to access Codex; a mitigation has been applied and the issue is being monitored (status.openai.com). - Cloudflare: a long-running degradation affecting two Workers AI models (open since June 16) remains under investigation. Several small incidents — Paris (CDG) network latency, Workers API errors, and email delivery delays — were resolved on July 17 (cloudflarestatus.com). - Akamai: an Application Load Balancer availability issue detected July 16 was fixed the same day and remains in monitoring with no recurrence (akamaistatus.com). - Twilio: carrier-specific SMS/voice delivery issues on routes to MTS Russia, Reliance Jio India, Chunghwa Taiwan, and Vodafone Australia — external carrier problems; core Twilio services are operational (status.twilio.com). Recently resolved (past 72 hours): GitHub's REST API was significantly degraded on July 16, with about 39% of requests failing between 22:21 and 23:50 UTC due to an infrastructure change that incorrectly marked API backends as unhealthy — since resolved (githubstatus.com). All clear elsewhere: Google Cloud, Azure, Azure DevOps, Slack, Zoom, Discord, Stripe, Vercel, Heroku, DigitalOcean, and Atlassian all report normal operations.

The internet is operating normally today. No global or internet-wide disruption is in progress, and all major cloud, CDN, and platform providers report their core services as operational. **What is active right now** A small number of minor, localized issues are open: - **Cloudflare — Paris (CDG):** Cloudflare is investigating higher-than-normal latency for a subset of traffic transiting its Paris data center. Impact is described as slight. Cloudflare is also still investigating degraded availability for some Workers AI models, an issue open since mid-June. ([status](https://www.cloudflarestatus.com/)) - **Akamai:** An issue affecting Application Load Balancer reporting, which began July 16, is in monitoring. A fix is in place and Akamai reports no recurrence. ([status](https://www.akamaistatus.com/)) - **Twilio:** Degraded SMS carrier performance continues in parts of Latin America, APAC, and Europe, including delivery delays on specific carriers in Brazil, Russia, and Myanmar. ([status](https://status.twilio.com/)) None of these are expected to be noticeable to most users. **Recently resolved (past 72 hours)** - **AWS CloudFront** suffered a roughly 3.5-hour partial outage on July 16, beginning at 12:45 AM PDT. Customers using VPC Origins saw widespread HTTP 5xx errors, taking a number of well-known sites and services offline. AWS attributed it to an internal connection-management limit in the fleet handling private VPC origins: once that threshold was reached, routing configuration failed to load correctly on the network processors. Full recovery was confirmed at 5:21 AM PDT. ([AWS Health Dashboard](https://health.aws.amazon.com/health/status)) - **Google Cloud** resolved a 12-hour, 28-minute outage in europe-west4-a caused by a cooling failure, affecting VMware Engine, NetApp Volumes, and Bare Metal Solution. Closed July 16. ([status](https://status.cloud.google.com/)) - **GitHub** logged a REST API degradation traced to an infrastructure change that incorrectly marked API backends as unhealthy. Resolved; all systems operational. ([status](https://www.githubstatus.com/)) - **DigitalOcean** resolved a Reserved IP routing issue in TOR1 on July 16. ([status](https://status.digitalocean.com/)) **All clear** Microsoft Azure, Google Cloud, Fastly, GitHub, OpenAI, Discord, Atlassian, Slack, Zoom, Vercel, Heroku, DigitalOcean, and Stripe all report normal operations. Crowd-sourced trackers show no meaningful spikes. No BGP hijacks, route leaks, DNS failures, or submarine cable faults are being reported. **A note on sources:** Downdetector, Cloudflare Radar, and ThousandEyes blocked automated checks this run, so this report is based primarily on official provider status pages plus secondary crowd-sourced signals. Nothing in the available data suggests those sources would change the assessment. **Bottom line:** The internet is up. A handful of small regional issues are being worked, and the most significant recent incident — the AWS CloudFront disruption — is fully resolved.

No internet-wide disruptions are ongoing today, but several provider-specific incidents are active or recovering. Google Cloud is experiencing an ongoing zonal outage in europe-west4-a (Netherlands) caused by a cooling failure, affecting Bare Metal Solution, NetApp Volumes, and VMware Engine since late July 15 UTC ([Google Cloud status](https://status.cloud.google.com/)). This is zonal in scope — other regions and zones are unaffected. GitHub reported a disruption with some services early on July 16 (investigation began 09:13 UTC); the degradation has been mitigated and GitHub is monitoring for stability ([GitHub status](https://www.githubstatus.com/)). OpenAI is working on elevated error rates for SSO login affecting ChatGPT and the API ([OpenAI status](https://status.openai.com/)), and Vercel is separately investigating SAML SSO login errors that began at 08:39 UTC ([Vercel status](https://www.vercel-status.com/)). Smaller items: Akamai mitigated an overnight Application Load Balancer availability issue and reports the service resuming normal operations. Cloudflare resolved elevated R2 error rates early today (04:49 UTC) and Hong Kong datacenter 502 errors on July 15; a remaining minor issue is limited to Magic WAN/Magic Transit tunnel health alert notifications, with traffic unaffected ([Cloudflare status](https://www.cloudflarestatus.com/)). Twilio is monitoring recovering SMS delivery delays to several carriers, including MTN Nigeria, Liberty Puerto Rico, and Vodafone Australia. In the US, crowd-sourced trackers showed morning report spikes for Spectrum and CenturyLink, consistent with regional ISP issues rather than a broader problem. AWS, Azure, Slack, Zoom, Discord, Stripe, DigitalOcean, Heroku, and Atlassian all report normal operations; Fastly's status page could not be checked directly, but aggregate monitors show no outage signals. No BGP or routing incidents of note were detected today. Bottom line: scattered provider-level incidents, most already mitigated or recovering — the internet is up.

The internet is operating normally today. Across the major cloud, CDN, and platform providers we monitor — AWS, Google Cloud, Microsoft Azure, Cloudflare, Fastly, Akamai, GitHub, OpenAI, Discord, Slack, Atlassian, Zoom and Vercel — core services are healthy with no widespread disruption. A few minor, isolated issues are worth noting, none of which affect general internet availability: • Cloudflare is investigating elevated errors on item PUT requests to its AI Search product, and continues to report degraded availability on some Workers AI models. Routine datacenter maintenance is also in progress in Atlanta, London, Barcelona and Accra. • DigitalOcean reported latency and timeouts on its Serverless Inference "Gemma 4" model; a fix has been deployed and the platform is monitoring recovery. • Twilio is investigating SMS delivery delays to Romania — a localized carrier-routing issue. Recently resolved (past 72 hours): Google Cloud VMware Engine had zonal outages affecting stretched-cluster customers in Australia and Europe for roughly 12 hours, resolved July 14. GitHub had a brief webhook-delivery blip on July 14, since resolved. Earlier edge-delivery degradation in Pakistan tied to a submarine-cable fault (SEA-ME-WE 5) has cleared. No BGP hijacks, route leaks, DNS failures, or new undersea-cable faults are affecting the broader internet as of this report. Bottom line: the internet is up. Today's issues are minor, isolated, and mostly developer- or region-specific.

The internet is operating normally today. There is no widespread outage, no significant routing or DNS failure, and no evidence of physical infrastructure problems affecting global connectivity. A handful of narrow, service-specific incidents are open. None of them affect core internet infrastructure. Active incidents: • Cloudflare — AI Search: Cloudflare is investigating elevated errors on item PUT requests to its AI Search service, first reported at 04:01 UTC. The component is listed as degraded. Cloudflare's core CDN, DNS, and network services are operational and unaffected. (https://www.cloudflarestatus.com/) • GitHub — Codespaces: GitHub reported degraded performance for Codespaces beginning around 08:21 UTC and is investigating. Git operations, the API, Actions, Pull Requests, Packages, and Pages all remain operational. (https://www.githubstatus.com/) • Twilio — carrier-level messaging and voice: Twilio has several open incidents tied to individual carriers, including SMS delivery delays to XL Axiata in Indonesia, SMS delivery failures to Vodafone Australia, voice call failures to Portugal, and SMS delays to Liberty Mobile in Puerto Rico. These are downstream carrier issues rather than a Twilio platform outage, though the SMS component is listed as degraded. (https://status.twilio.com/) • DigitalOcean — Serverless Inference: Elevated latency affecting Gemma 4 inference workloads. A fix has been deployed and DigitalOcean is monitoring recovery. (https://status.digitalocean.com/) Operating normally: AWS, Microsoft Azure, Google Cloud, Akamai, OpenAI, Discord, Atlassian, Slack, Zoom, and Vercel all report no active incidents. Scheduled maintenance (not an outage): Cloudflare has planned maintenance windows in progress at its Kansas City (MCI), Ashburn (IAD), Barcelona (BCN), and Accra (ACC) datacenters. Traffic may be re-routed from these locations, which can cause a slight increase in latency for nearby users. Zoom also has several no-impact backend maintenance releases in progress. Consumer ISP reports: Spectrum is showing elevated user-submitted reports over the past 24 hours, concentrated in Florida, North Carolina, and New York. Report volumes at this level are typical background noise for a large ISP and do not indicate a broad regional outage. A note on completeness: the AWS Health Dashboard renders its status client-side and could not be read directly this run. Independent sources and crowd-sourced reporting show no signs of an AWS incident, but that specific page was not verified firsthand. The Fastly, Heroku, Stripe, and Meta status pages also did not return readable content this run; no secondary signals suggest problems at any of them. Bottom line: a few isolated, service-level degradations — mostly in AI and messaging add-on services — against an otherwise healthy internet. Core cloud, CDN, DNS, and routing infrastructure is stable. The internet is up.

The internet is operating normally today. No widespread outage, routing failure, or cloud-provider disruption is in progress. **Core infrastructure** Microsoft Azure, Google Cloud, Cloudflare, GitHub, Discord, Slack, Atlassian, Vercel, DigitalOcean, Akamai, Fastly, and Stripe all report normal operations. Google Cloud explicitly reports "no broad severe incidents," and Azure shows no active events across any region. One note on completeness: we were unable to directly retrieve the AWS Health Dashboard this morning (the page renders client-side and its public RSS feed is currently stale). We found no corroborating evidence of an AWS disruption today in crowd-sourced trackers or news, but we are flagging this as unverified rather than asserting all-clear. **Active incidents (limited scope)** - **OpenAI** — Users may see elevated errors uploading, deleting, or navigating files in the ChatGPT Library. The issue has been under investigation for roughly an hour. Core API and ChatGPT conversation functionality are unaffected. ([status.openai.com](https://status.openai.com/)) - **Twilio** — SMS delivery failures from Twilio to Vodafone Australia subscribers, ongoing since July 12. Investigation continues. Impact is limited to that one carrier and region. ([status.twilio.com](https://status.twilio.com/)) - **Cloudflare Workers AI** — Degraded availability on two specific models (Kimi K2.6 and K2.7-code), an ongoing item since June 16. Other Cloudflare services are operational. ([cloudflarestatus.com](https://www.cloudflarestatus.com/)) **Scheduled maintenance** Cloudflare has planned maintenance windows today in its Istanbul (08:00–12:00 UTC) and Kansas City (07:00–12:00 UTC) datacenters. Traffic may reroute with slight latency increases in those regions. Zoom has several multi-day maintenance releases in progress with no expected user impact. These are planned, not outages. **Recently resolved (past 72 hours)** - GitHub Actions delays on July 9 (~8% of hosted-runner workflows delayed) — resolved. - Discord billing operations issue on July 10 — resolved. - DigitalOcean DOKS DNS timeouts in NYC1 on July 11 — resolved. **Bottom line** No internet-wide problem. The active issues are narrow — one file-management feature, one carrier-specific SMS path, and two AI models — and none of them threaten broad connectivity.

The internet is operating normally. Our checks across the major cloud, CDN, and platform providers show no widespread outages, routing failures, or DNS problems. Core infrastructure is healthy: AWS, Microsoft Azure, and Google Cloud all report normal operations, as do Akamai, Fastly, GitHub, OpenAI, Discord, Slack, Atlassian, Vercel, DigitalOcean, Stripe, and Meta. Minor, isolated incidents (no broad impact): - Cloudflare Workers AI is showing degraded availability on a couple of specific AI models. Core Cloudflare CDN, DNS, and network services are unaffected. - Twilio reports SMS delivery delays to specific carriers (Pelephone in Israel, now recovering; GTA Wireless in the US). This is carrier-specific and not internet-wide. Recently resolved (past 72 hours): - DigitalOcean: a Kubernetes deployment issue in NYC1 (resolved July 11). - Discord: billing operation issues (resolved July 10). - GitHub: delayed Actions job starts affecting roughly 8 percent of runs (resolved July 9). No BGP incidents, DNS failures, or undersea cable problems are affecting the broader internet. Overall status: all clear.

The internet is operating normally today. No widespread outages or internet-wide disruptions are affecting global connectivity. Core cloud, CDN, and platform providers — AWS, Microsoft Azure, Google Cloud, Cloudflare, Akamai, Fastly, GitHub, OpenAI, Discord, Slack, Atlassian, Vercel, DigitalOcean, and Zoom — are all reporting normal operations. A few minor, single-provider issues are worth noting: - Twilio is reporting partially degraded service, with degraded performance on SMS/Programmable Messaging, Conversations memory, and MMS in the APAC region. Most Twilio products remain operational. - Cloudflare core CDN, DNS, and network services are healthy; Workers AI shows degraded availability on a small number of AI models. Routine datacenter maintenance is scheduled at several locations through July 15. Recently resolved (past 72 hours): - GitHub Actions saw delayed workflow runs on July 9; the issue has been resolved. - A fault in the SEA-ME-WE 5 (SMW5) submarine cable slowed international traffic in Pakistan around July 2; traffic was rerouted and connectivity has recovered. Bottom line: no meaningful internet-wide issues detected. The internet is up and running normally.

The internet is operating normally today. Across the major cloud, CDN, and platform providers we monitor — AWS, Google Cloud, Microsoft Azure, Cloudflare, Fastly, Akamai, GitHub, Discord, Slack, Zoom, Vercel, and Atlassian — all core services are reporting healthy status with no widespread disruptions. A few minor, isolated issues are worth noting, none of which affect the internet broadly: - Cloudflare has routine scheduled datacenter maintenance in progress today (Newark, Atlanta, and London), which may cause brief, localized latency as traffic reroutes. A long-running issue affecting two specific Workers AI models (open since June 16) also remains under investigation. - OpenAI reports lingering issues confined to FedRAMP workspaces; core ChatGPT and API functionality is unaffected. - Twilio is investigating SMS delivery delays to Liberty Mobile subscribers in Puerto Rico — a carrier- and region-specific issue. - DigitalOcean is monitoring a Kubernetes issue in its NYC1 region that has subsided, with workloads reported functioning normally. No BGP hijacks, route leaks, DNS failures, or new submarine cable faults were detected today. Earlier in July a fault on the SEA-ME-WE 5 cable degraded international connectivity for Pakistan, but that is a regional event from over a week ago and outside today's scope. Bottom line: no meaningful internet-wide issues. The internet is up.

The internet is operating normally overall on July 9, 2026, with no widespread or internet-wide outage. A handful of localized, single-provider incidents are worth noting. GitHub Actions is seeing the most notable disruption: roughly 30% of Actions runs on GitHub-hosted runners are experiencing start delays exceeding five minutes, and a smaller share are failing to start after exhausting retries. GitHub has been investigating since 04:34 UTC and the incident remains open as of 10:15 UTC. Core GitHub services (repositories, pull requests, web) are unaffected (githubstatus.com). Other minor and regional issues: - Cloudflare: Workers AI shows degraded availability for a couple of Moonshot AI models (ongoing since mid-June), and Pages reports degraded performance. Scheduled datacenter maintenance is also underway in several cities (cloudflarestatus.com). - OpenAI: Narrow issues affecting FedRAMP government workspaces; core ChatGPT and API functionality is normal (status.openai.com). - Twilio: Regional messaging and voice delivery delays (UK long codes, US T-Mobile SMS, Colombia voice, Italy) (status.twilio.com). Core cloud and CDN infrastructure is healthy: AWS, Google Cloud, Azure, Akamai, Fastly, Discord, Slack, Atlassian, Vercel, DigitalOcean and Stripe all report normal operations. No BGP, DNS, or undersea-cable incidents are affecting the broader internet. Recently resolved (past 72 hours): Akamai edge-delivery issues in Pakistan tied to submarine-cable problems (resolved Jul 4), and several DigitalOcean regional incidents (resolved Jul 3–7). Bottom line: the internet is up. Expect intermittent CI/CD delays if you rely on GitHub-hosted Actions runners until that incident clears.

The internet is operating normally today. No widespread outages, routing failures, DNS problems, or physical infrastructure incidents are affecting global connectivity. Major cloud, CDN, and platform providers are reporting normal operations, including AWS, Microsoft Azure, Google Cloud, Akamai, Fastly, GitHub, Discord, Slack, Atlassian, Zoom, Vercel, and DigitalOcean. No BGP routing incidents, DNS resolver problems, or undersea cable events have been detected today. A few minor, provider-specific issues remain active but do not affect the broader internet: - Cloudflare: Workers AI reports degraded availability on a small number of specific models. Core Cloudflare CDN, DNS, and network services are operating normally. - OpenAI: An ongoing issue is confined to FedRAMP (US government) workspaces, affecting features such as Codex and workspace analytics in that environment. Standard ChatGPT and API services are unaffected. - Twilio: Localized messaging and console issues, largely tied to scheduled carrier maintenance windows (AT&T and MMS in the US) plus a WhatsApp sandbox problem. Core voice and messaging remain operational. Recently resolved in the past 72 hours: Akamai restored edge delivery in Pakistan after a submarine cable disruption (resolved July 6), and Zoom cleared several regional service degradations. GitHub resolved a brief Actions/Codespaces API incident on July 7. Bottom line: the internet is up and running normally. Any issues today are isolated to specific provider sub-services and are not impacting general connectivity.

The internet is operating normally today. Across the major cloud providers, CDNs, and platforms we monitor, no widespread or internet-wide disruption is in progress. Core infrastructure is healthy. Amazon Web Services, Google Cloud, and Microsoft Azure are all reporting normal operations, with only minor, older regional component notes (a July 5 multi-service item and small UAE/Bahrain component issues) that are not causing broad impact. GitHub, Discord, Vercel, Atlassian, and DigitalOcean are all fully operational. A few minor, tightly scoped incidents are worth noting for affected users. Cloudflare (https://www.cloudflarestatus.com) shows routine scheduled datacenter maintenance across several regions plus a niche degradation affecting two Workers AI models — core delivery is unaffected. OpenAI (https://status.openai.com) has an ongoing incident limited to FedRAMP workspaces (Codex, analytics, and related features); standard ChatGPT and API service is normal. Twilio (https://status.twilio.com) reports planned SMS maintenance on some small US carriers and degraded voice speech recognition in its EU-West region. Recently resolved: Akamai mitigated a submarine-cable-related performance issue affecting edge delivery in Pakistan on July 2, and GitHub cleared a Copilot budget-reset delay on July 1. Bottom line: no cause for concern. The internet is up.

No internet-wide disruptions are affecting connectivity today. Core cloud platforms — AWS, Google Cloud, and Microsoft Azure — report normal operations in their primary regions, and no significant CDN incidents are active. Two provider-level issues are worth noting. Twilio is investigating voice call failures from Twilio phone numbers to network subscribers in multiple countries across North America and Europe; the incident opened late July 5 (PDT) and remains under investigation (status.twilio.com). Cloudflare reports degraded performance on its Zero Trust Dashboard, with some users unable to complete onboarding or manage Access applications, alongside a longer-running degradation affecting two Workers AI models (cloudflarestatus.com). OpenAI continues to work through residual issues scoped to FedRAMP workspaces. Recently resolved in the past 72 hours: Akamai rerouted traffic around a submarine cable fault affecting connectivity to and from Pakistan, with normal delivery restored today (akamaistatus.com). DigitalOcean resolved droplet action disruptions in its NYC3 region on July 4, and GitHub cleared a Pages deployment latency issue on July 2. Background context: AWS Middle East regions ME-CENTRAL-1 (UAE) and ME-SOUTH-1 (Bahrain) remain in long-term disruption due to conflict-related damage, with AWS advising customers to migrate workloads to other regions — a continuing situation since March, not a new incident. Crowd-sourced outage trackers show no unusual report spikes for major consumer platforms. GitHub, Slack, Zoom, Discord, Atlassian, Stripe, Vercel, Heroku, and DigitalOcean all report normal operations. Overall: the internet is up.

The internet is broadly healthy today. Crowd-sourced outage trackers show no elevated reports, and the major cloud platforms — AWS, Google Cloud, and Azure — are all reporting normal operations. A few minor items are still being monitored: - Cloudflare is monitoring network performance in North America after implementing a fix on July 4 (https://www.cloudflarestatus.com/). A separate issue affecting some Workers AI models is under investigation. - Akamai continues to monitor content delivery in Pakistan following a submarine cable issue; traffic has been rerouted and service has resumed normal operations (https://www.akamaistatus.com/). - Twilio reports degraded SMS performance tied to carrier network issues in parts of APAC, the Middle East, and Africa (https://status.twilio.com/). - OpenAI has an ongoing issue limited to FedRAMP workspaces, now in its sixth day (https://status.openai.com/). Recently resolved (past 72 hours): - AWS US-EAST-1: a cooling failure in one Northern Virginia data center on the night of July 2–3 shut down EC2 instances and EBS volumes in a single Availability Zone, with knock-on impact to dependent services. AWS restored full cooling capacity by the afternoon of July 3 (https://health.aws.amazon.com/health/status). - Pakistan: a fault in the SEA-ME-WE 5 submarine cable caused intermittent degradation on the night of July 2. The PTA confirmed on July 3 that the fault was fixed and traffic returned to normal (https://www.dawn.com/news/2012653). - GitHub resolved Pages deployment latency on July 2. Discord, Slack, Zoom, Atlassian, Stripe, Heroku, DigitalOcean, and Vercel all report normal operations. No internet-wide routing, DNS, or connectivity problems are evident today.

The internet is operating normally today. There is no widespread or internet-wide outage — only a handful of minor, provider-specific incidents, all localized or already being mitigated. What we are tracking: • Cloudflare — Engineers implemented a fix for a network performance issue affecting parts of North America and are monitoring the results. Separately, Workers AI is showing degraded availability for a couple of specific models. Core services remain largely operational. (https://www.cloudflarestatus.com) • Akamai — A submarine cable problem affecting traffic to and from Pakistan (began July 2) has been mitigated by rerouting traffic away from the affected paths. Akamai reports normal operations and continues to monitor. • Twilio — Carrier-specific SMS delivery delays or failures on certain networks in Haiti, Bolivia, Indonesia, and Iraq. These are external carrier issues; core Twilio services are operational. • OpenAI — Some features remain degraded in FedRAMP (US government) environments. Standard ChatGPT and API services are unaffected. All clear: AWS, Google Cloud, Microsoft Azure, GitHub, Discord, Slack, Atlassian, Vercel, and DigitalOcean report no active incidents. Recently resolved (past 72 hours): GitHub Pages deployment latency (July 2), Discord intermittent chat issues (June 29), and several DigitalOcean regional issues (July 1–3). Bottom line: The internet is up. The issues in play are localized or provider-specific and are being actively managed.

The internet is operating normally today. Major cloud, CDN, and platform providers — AWS, Microsoft Azure, Google Cloud, Cloudflare, Fastly, Akamai, GitHub, Discord, Slack, Zoom, Vercel, Atlassian and DigitalOcean — are all reporting normal operations with no widespread disruptions. A handful of minor, localized incidents are being monitored, but none affect the broader internet: - Akamai is monitoring a regional content-delivery issue in Pakistan linked to a submarine cable fault. Traffic has been rerouted and service has largely resumed. - Twilio is working through carrier-specific SMS and voice delivery issues affecting a small number of individual mobile networks (in Iraq, France, Côte d'Ivoire, Brazil, Bolivia and Haiti). These are per-carrier telecom issues, not an internet-wide problem. - OpenAI reports a narrow, ongoing issue limited to FedRAMP workspaces; core ChatGPT and API functionality is unaffected. Cloudflare has routine scheduled maintenance underway at several data centers (Los Angeles, São Paulo, Marseille), which may cause brief, minor latency changes in those regions but no outages. Crowd-sourced outage trackers show no unusual report spikes. Overall status: all clear — the internet is up and running normally.

The internet is broadly healthy today, with two notable provider incidents and no global disruption. Cloudflare — North America network performance issue (recovering). At 00:23 UTC today, Cloudflare began investigating network performance problems in Eastern and Western North America (ENAM/WNAM), logged as a major-impact incident on cloudflarestatus.com. Customers using Argo Smart Routing in the affected regions were impacted. The cause was identified by 01:03 UTC, a fix has been implemented, and Cloudflare is monitoring the results. A separate minor incident — degraded availability for some Workers AI models — has been open since June 16. AWS — Middle East (UAE) region still impaired. The ME-CENTRAL-1 region remains unable to reliably support customer workloads after two facilities were physically damaged by drone strikes in mid-June amid the regional conflict. AWS says recovery will take several months, billing for the region is suspended during restoration, and customers are advised to migrate workloads to other regions and enact disaster recovery plans (health.aws.amazon.com). Minor issues elsewhere: Twilio reports three minor regional SMS incidents (sender verification in Australia, delivery delays to Asia Cell Iraq, delivery failures to Natcom Haiti). OpenAI has an ongoing incident limited to FedRAMP government workspaces; its public APIs and ChatGPT are operational. All clear elsewhere: Google Cloud, Azure, Azure DevOps, Akamai, GitHub, Discord, Atlassian, Slack, Vercel, Heroku, and DigitalOcean all report normal operations. No notable BGP, DNS, or undersea cable issues were detected. Sources: cloudflarestatus.com, health.aws.amazon.com, status.twilio.com, status.openai.com, status.cloud.google.com, azure.status.microsoft, githubstatus.com

The internet's core infrastructure is operating normally today. No widespread or internet-wide outage is in progress. A handful of minor, provider-specific incidents are active: - GitHub: Degraded performance for Copilot tied to budget-limit reset delays; under investigation. - DigitalOcean: Two open incidents — the Droplet "Downscale Anytime" resize option is unavailable in the control panel (API workaround available), and Agents are seeing timeouts retrieving Knowledge Base data. - Twilio: Regional SMS delivery issues affecting specific carriers in Bulgaria, Peru, and the Philippines, plus Sender ID verification quirks for Australia — routine telecom-level, not internet-wide. - OpenAI: Feature issues limited to FedRAMP workspaces; core ChatGPT and API services unaffected. - Cloudflare: Scheduled datacenter maintenance in Las Vegas and Atlanta (possible slight latency in those regions) plus degraded availability for two Workers AI models. The major providers are healthy: AWS, Microsoft Azure, Google Cloud, Akamai, Discord, Slack, Atlassian, Vercel, Zoom, and Stripe all report normal operations. No BGP hijacks, route leaks, DNS failures, or submarine cable incidents were detected. Recently resolved (past 72 hours): Discord intermittent chat issues (June 29) and an Akamai configuration deployment issue (June 30) are both fixed. Bottom line: the internet is up. Today's issues are scattered and localized, with no meaningful impact on general connectivity.