Internet & cloud outages today

**Overall: incidents detected, no internet-wide outage.** The core cloud platforms (AWS, Google Cloud, Azure) and the major CDNs are working normally. The biggest event of the day happened somewhere we don't track: a drone strike took Yandex's largest data center offline in Russia. **Yandex data center offline after drone strike (Russia)** Overnight, a drone strike set fire to the building housing Yandex's data center in Sasovo, Ryazan region. The company said the facility has stopped operating completely and that some services may be unavailable. No one was hurt. Downdetector logged more than 1,300 user reports, mostly about Yandex Cloud, Yandex Documents and Yandex Tables. Search and Taxi stayed online. Some reports said connectivity across Yandex's network dropped to roughly 70% of normal, and sites hosted on Yandex Cloud were affected too, including Cian, Russian Railways and several regional government portals. Sasovo opened in 2014 and is rated at up to 12 MW. Yandex has not said when it expects the site to come back. Sources: [CNBC](https://www.cnbc.com/2026/10/08/russia-yandex-ukraine-drone-strike-data-center.html), [The Record](https://therecord.media/yandex-russia-drone-ukraine), [Meduza](https://meduza.io/en/feature/2026/10/08/ukraine-strikes-yandex-data-center-housing-two-of-the-company-s-supercomputers). **Still open at tracked providers** - **Anthropic:** the incident for elevated errors on the Claude Console (platform.claude.com), opened October 7, is still in monitoring. The Claude API itself is not listed as degraded. ([status](https://status.claude.com)) - **Akamai:** the incident for origin connectivity errors in APAC, open since September 22, is still in monitoring. - **Twilio:** a handful of carrier-specific SMS/MMS delays (Movistar El Salvador, Brisanet Brazil, GCI US, some Australian networks). - **Zoom:** Zoom Phone still has a known issue with some Polycom devices going offline. - **Cloudflare:** two long-running minor incidents (WARP geolocation, Cloudflare One client challenges), plus routine data-center rerouting shown on its status page. **Resolved in the past 72 hours** - **GitHub, October 5–7:** a rough few days, with five incidents rated major or critical. On October 7 there were two critical incidents affecting Git operations, pull requests, Actions and Issues (about 15:14–16:25 and 17:17–18:04 UTC), with widespread impact for roughly ten minutes during the first. A root-cause analysis has been promised. ([GitHub Status](https://www.githubstatus.com), [Android Authority](https://www.androidauthority.com/github-outage-oct-2026-3720346/)) - **Cloudflare, October 7:** network performance issues in Columbus (major, resolved) and a short Cloudflare API issue. - **OpenAI, October 7–8:** several minor ChatGPT and Codex incidents, the latest being errors for some APAC users from 03:17 to 04:51 UTC today. - **ElevenLabs:** a 10-minute slowdown on Music endpoints this morning, plus EU SIP-call disruption for Agents on October 6. Both are resolved. **All clear:** AWS, Google Cloud, Azure, Azure DevOps, GitHub (currently), Discord, Slack, Atlassian, Vercel, Heroku, DigitalOcean, Stripe, Cursor, Groq, Replicate, Cohere and Stability AI. We found no reports of Meta, Fastly or major ISP problems today, and no notable BGP incidents surfaced. Meta's status page couldn't be read automatically, so that one rests on outage-report signal only.

No widespread internet outage is in progress as of about 10:45 UTC on Tuesday, October 6. Major clouds (AWS, Google Cloud, Azure) show no active incidents. Cloudflare, GitHub, OpenAI, Anthropic and Discord are operational. Overnight brought a handful of short incidents that have since been resolved, and the biggest event of the past 24 hours was a GitHub Actions disruption on Monday evening. **GitHub Actions (resolved).** Between 19:11 and 22:49 UTC on October 5, GitHub-hosted runners were slow to be assigned to Actions jobs. Workflows across several runner configurations started late, and some jobs failed. GitHub rated the incident critical and has promised a root cause analysis. A separate, smaller GitHub issue from 23:47 UTC to 01:32 UTC affected organization and enterprise billing and licensing pages. Source: [GitHub Status](https://www.githubstatus.com/history). **Cloudflare (resolved).** From 08:22 to 09:06 UTC today, TLS handshakes failed for some Keyless SSL customers using RSA keys with specific key-backend configurations. On October 5 Cloudflare also reported three other incidents, all resolved: higher latency for cacheable assets in multiple locations (09:30–11:10 UTC), API Shield JWT validation errors for customers using symmetric keys (about 11 hours until fully resolved), and reduced Durable Objects availability in Eastern North America (from 17:14 UTC, fix in place by 17:53). Cloudflare's page still lists a number of individual data centers as degraded or re-routed, which is routine. Source: [Cloudflare Status](https://www.cloudflarestatus.com/history). **AI platforms.** OpenAI had several minor incidents, all resolved. They included elevated errors across ChatGPT conversations, image generation and other products early today (from 02:41 UTC) and errors in the API Platform login and admin APIs (from 00:40 UTC). Anthropic reported elevated errors for Claude Mythos 5.1 and Fable 5.1 on October 5, from 12:40 to 13:10 UTC. ElevenLabs is investigating two incidents right now: higher latency on a small share of text-to-speech requests (since 09:09 UTC) and disrupted SIP calls for EU-residency Agents (since 10:28 UTC). **Carrier-level messaging.** Twilio lists new SMS delivery delays to Chunghwa Telecom (Taiwan), Rain (South Africa) and Orange Niger. Older MMS issues with GCI (US) and Australian carriers are still open. Zoom has an ongoing issue with some Polycom devices going offline for Zoom Phone. Akamai still shows an APAC origin-connectivity incident in monitoring that has been open since September 22. **Not a current outage.** Recent headlines link OpenAI's agents to a Wikimedia outage. According to Wikimedia's own account, that incident hit the Wikidata Query Service from May 7 to May 11, 2026. Nothing points to new disruption at Wikimedia today. **Regional connectivity.** Third-party trackers flagged short connectivity drops in Bangladesh, Ghana and Burkina Faso on October 5. We could not independently confirm the cause or how far they reached. Overall: some notable but contained incidents, with no internet-wide disruption. This report was written early in the day and covers events up to about 10:45 UTC.

The internet is up globally as of 10:00 UTC on Monday, October 5. There is no widespread outage. What's active this morning is limited to specific products, and the most notable item from the last 24 hours is a regional AWS incident in Spain that has since been resolved. **Ongoing** - **OpenAI (ChatGPT Work Mode):** OpenAI opened an incident for elevated Work Mode errors at 07:03 UTC. ChatGPT Work and Codex in the ChatGPT desktop app show degraded performance, and the incident is in monitoring, which means a fix has been applied. Core ChatGPT and the API are not listed as affected. It follows a busy week at OpenAI, including a major login and signup incident on October 1, now resolved. [status.openai.com](https://status.openai.com) - **Twilio (Europe messaging):** Twilio opened two new messaging incidents overnight: delayed messaging logs and status callbacks in its IE1 (Ireland) region, now in monitoring, and SMS delivery delays and failures between Twilio long codes and several French mobile networks, with the cause identified. Older MMS issues in Australia and with GCI in the US remain open. [status.twilio.com](https://status.twilio.com) - **Long-running, low-impact:** Akamai's APAC origin connectivity issue (since September 22) is still in monitoring. Zoom's Polycom device issue (since September 25) is still open. Cloudflare has two minor open items, a Cloudflare One challenge issue and incorrect WARP geolocation, plus routine data-center maintenance and rerouting. **Resolved in the past 72 hours** - **AWS EU-SOUTH-2 (Spain):** Between 15:48 and 18:28 UTC on October 4, a single Availability Zone (eus2-az1) saw elevated packet loss. AWS said this also raised API latencies and error rates for multiple services in the region. AWS found the root cause and the issue is fully resolved. [health.aws.amazon.com](https://health.aws.amazon.com/health/status) - **Philippines subsea cable cut:** The October 2 damage to the Philippines–Singapore and Philippines–Hong Kong links slowed international traffic for about two days. PLDT reported full restoration on October 4, and Globe and Converge are carrying traffic on alternate routes. The physical repair may take weeks, and DICT is still investigating the cause. [GMA News](https://www.gmanetwork.com/news/scitech/technology/1004568/slow-intermittent-internet-in-ph-on-friday-oct-10-2026-linked-to-submarine-cable-outage/story/) · [Rappler](https://www.rappler.com/technology/submarine-cable-cut-philippines-singapore-disrupts-internet-services/) - **Cloudflare:** CDN configuration changes and dashboard cache purges briefly returned errors on October 2 (about 11 minutes; API purges were unaffected), and Workers Builds failed to start on October 3. Both are resolved. [cloudflarestatus.com](https://www.cloudflarestatus.com/incidents/2xnmsnv8yv5x) **Regional and unconfirmed signals** - Outage-tracking sites showed a rise in AT&T user reports from around 04:30 UTC (00:30 ET). It looks like hundreds of reports, not thousands, and we found no confirmation from AT&T, so treat it as unverified. - IODA flagged a connectivity drop in Kampong Speu province, Cambodia, at 04:35 UTC. It comes from a single source and is low-confidence. [Voidly/IODA](https://voidly.ai/incident/KH-2026-0214) - Internet Society Pulse lists 10 government-ordered shutdowns ongoing worldwide. [pulse.internetsociety.org](https://pulse.internetsociety.org/en/shutdowns/) **All clear** AWS (outside the long-standing Middle East region outages), Google Cloud, Azure, Azure DevOps, GitHub, Anthropic/Claude, Discord, Atlassian, Slack, Vercel, Heroku, DigitalOcean, Stripe, Cursor, Groq, ElevenLabs, Cohere and Stability AI all report no active incidents. Replicate's status page now redirects into Cloudflare's, which lists Replicate as operational. Meta's status page shows no incident we could read. Status: incidents detected. These are product-level issues, and there is no internet-wide disruption.

The internet is up globally on Sunday, October 4. The main story is a recovery: Philippine carriers say service is back to normal after Friday's subsea cable cut. The major cloud providers (AWS, Google Cloud, Azure) report no active incidents. The issues still open elsewhere are minor and product-specific. **Philippines: service restored after subsea cable cut (recovering)** The Philippines–Singapore cable segment went offline on October 2, and the Philippines–Hong Kong link was also affected. For two days, users had slow and intermittent access to overseas content. As of 4:30 p.m. local time today (08:30 UTC), PLDT reports full restoration of its network services nationwide. Globe says it has restored mobile and broadband service after the cable landing station in the Philippines reactivated the system, and it is still investigating the exact nature and location of the fault. Converge moved affected traffic onto alternative submarine cables and is monitoring connections to Singapore-hosted apps and sites. No cause has been confirmed, and it is not yet clear whether the cable itself has been physically repaired, so some performance variation is possible while operators keep monitoring. Sources: [NewsBytes.PH](https://newsbytes.ph/2026/10/04/internet-services-normalize-after-ph-singapore-cable-cut/), [Rappler](https://www.rappler.com/technology/submarine-cable-cut-philippines-singapore-disrupts-internet-services/), [GizGuide](https://www.gizguide.com/2026/10/dict-submarine-cable-outage-triggers.html). **Other open, limited-scope issues** **Cloudflare:** the Workers Builds problem that began at 05:55 UTC on October 3 (builds failing to start) has had a fix in place since 08:55 UTC that day and is still marked as monitoring. Deployed Workers were not reported as affected. Cloudflare's network map also shows its usual scattered data-center reroutes and maintenance, with no broad incident declared. ([Cloudflare Status](https://www.cloudflarestatus.com)) **Twilio:** a new carrier-specific issue opened today, with SMS delivery delays from some Twilio numbers to Cellcom Israel (monitoring). Older MMS issues with GCI (US) and Australian carriers are still open. ([Twilio Status](https://status.twilio.com)) **Akamai:** the APAC origin-connectivity incident that has been open since September 22 is still in monitoring. ([Akamai Status](https://www.akamaistatus.com)) **Zoom:** some Polycom devices are still going offline (open since September 25). ([Zoom Status](https://www.zoomstatus.com)) **Regional connectivity signals** IODA flagged a connectivity drop in Vientiane, Laos, starting around 07:55 UTC today. It is a low-confidence, single-measurement signal, and Laos has had several similar short disruptions since August, so treat it as unconfirmed. ([IODA via Voidly](https://voidly.ai/incident/LA-2026-0016)) **Recently resolved (past 72 hours)** **Cloudflare:** from 21:46 to 21:57 UTC on October 2, CDN configuration changes and cache purges issued from the dashboard saw elevated errors. API purges were unaffected. ([Cloudflare incident](https://www.cloudflarestatus.com/incidents/2xnmsnv8yv5x)) **All clear at:** AWS, Google Cloud, Azure, Azure DevOps, GitHub, OpenAI, Anthropic (Claude), Discord, Atlassian, Slack, Vercel, Heroku, DigitalOcean, Stripe, Cursor, Groq, ElevenLabs, Cohere and Stability AI. Meta's status page could not be read on this run, and none of the outage reports we checked mentioned a Facebook, Instagram or WhatsApp disruption.

The internet is up globally on Saturday, October 3. The one story that matters is in Southeast Asia: a subsea cable cut is still slowing connections in the Philippines. Elsewhere, the major cloud providers report no active incidents, and the open issues are minor, product-specific ones. **Philippines: subsea cable cut (ongoing, regional)** On October 2, the cable segment linking the Philippines and Singapore went offline, and the Philippines–Hong Kong segment was also affected. Users reported slow and intermittent connections. Converge ICT, PADECO and the UP Diliman network issued advisories. PLDT reported losing about 300 Gbps of capacity on the affected links. PLDT and Converge say most traffic has been rerouted, while Globe warned customers that access may still be slow. The DICT says the cause is still unknown (a natural fiber cut or equipment failure). Repair vessels are being prepared, and repairs are expected to take several weeks, so expect degraded international performance from the Philippines for some time. Sources: [Rappler](https://www.rappler.com/technology/submarine-cable-cut-philippines-singapore-disrupts-internet-services/), [GMA News](https://www.gmanetwork.com/news/scitech/technology/1004568/slow-intermittent-internet-in-ph-on-friday-oct-10-2026-linked-to-submarine-cable-outage/story/), [NewsBytes.PH](https://newsbytes.ph/2026/10/03/ph-sg-subsea-cable-cut-disrupts-internet-as-telcos-reroute-traffic/). **Cloudflare: Workers Builds (monitoring)** Starting at 05:55 UTC today, Cloudflare Workers builds were failing to start. A fix went out at 08:55 UTC and Cloudflare is monitoring it. Serving of deployed Workers was not reported as affected. Late yesterday (21:46–21:58 UTC, October 2), Cloudflare also had a brief incident with errors on CDN configuration changes and dashboard-issued cache purges. API purges were unaffected. ([Cloudflare Status](https://www.cloudflarestatus.com/)) **Other open, limited-scope issues** - **Twilio:** carrier-specific SMS delivery delays to Banglalink (Bangladesh) and Magti (Georgia) opened this morning, alongside older MMS issues with GCI (US) and Australian carriers. ([Twilio Status](https://status.twilio.com/)) - **Akamai:** a long-running APAC origin-connectivity incident from September 22 is still in monitoring. ([Akamai Status](https://www.akamaistatus.com/)) - **Zoom:** some Polycom devices going offline on Zoom Phone (open since September 25). ([Zoom Status](https://www.zoomstatus.com/)) **Recently resolved (past 72 hours)** - **Microsoft Azure:** from 20:30 UTC on September 30 to about 02:15 UTC on October 1, ExpressRoute and VPN gateways, Azure Firewall, Application Gateway and Azure VMware Solution lost or had degraded connectivity across 18 regions. Microsoft linked it to infrastructure OS servicing work, which it paused. ([The Register](https://theregister.com/off-prem/2026/10/01/azure-maintenance-mess-disrupted-hybrid-clouds-vpns-cloudy-vmware-services/5300333)) - **AT&T:** on October 2, around 10:30 a.m. PT, more than 2,000 Downdetector reports of mobile signal and Wi-Fi problems. No cause was disclosed. ([GV Wire](https://gvwire.com/2026/10/02/att-down-for-thousands-of-users-downdetector-shows/)) - **Cloudflare:** Durable Objects and R2 errors on October 1, plus short local network issues in Mumbai, Columbus and Seoul. **All clear** AWS, Google Cloud, Azure, Azure DevOps, GitHub, OpenAI, Anthropic (Claude), Discord, Atlassian, Slack, Vercel, Heroku, DigitalOcean, Stripe, Cursor, Groq, Replicate, ElevenLabs, Cohere and Stability AI all report normal operation. Searches showed no significant BGP or DNS incidents today. Meta's status page could not be read automatically, and we found no reports of a Meta outage.

No internet-wide outage is in progress as of 13:30 UTC on October 2. Two items are worth knowing about: a new Akamai DNS propagation issue this morning, and a large Microsoft Azure networking incident on the evening of September 30 that our October 1 report did not cover. **Akamai Edge DNS (investigating).** At 13:24 UTC Akamai opened an incident for Edge Delivery. Record changes made on customers' primary (master) DNS servers are not being reflected on Akamai Edge DNS. Sites that changed DNS records recently may still be serving old answers from Akamai's edge, while sites with unchanged records should not be affected. Akamai marks Content Delivery and Edge Delivery as degraded and has not yet given a scope or cause. This is at an early stage. ([Akamai status](https://www.akamaistatus.com/)) **Microsoft Azure gateways (resolved, Sept 30 to Oct 1).** From 20:30 UTC on September 30, ExpressRoute Gateway and VPN Gateway connections degraded or dropped in about 18 regions, among them West US, North and West Europe, UK South, Japan West, Southeast Asia and South Africa North. Azure VMware Solution, Azure Firewall and Application Gateway were also hit. Gateways had mostly recovered by about 23:13 UTC, and Microsoft declared the incident mitigated around 02:15–03:30 UTC on October 1. Microsoft ties it to infrastructure OS servicing work and a change to a regional gateway management service that created more load than expected. That servicing has been paused. Hybrid-cloud and site-to-site VPN customers took the impact; public internet traffic to Azure was not broadly affected. ([Azure status history](https://azure.status.microsoft/en-us/status/history), [The Register](https://theregister.com/off-prem/2026/10/01/azure-maintenance-mess-disrupted-hybrid-clouds-vpns-cloudy-vmware-services/5300333)) **Other incidents from the past 24 hours (all resolved):** - **OpenAI**: login, signup and ads were failing from 18:46 to 19:39 UTC on October 1 (rated major), with full recovery after a mitigation. An earlier ChatGPT Space Pages error incident has also closed. ([OpenAI status](https://status.openai.com/)) - **Cloudflare**: increased errors for Durable Objects and R2 for about 20 minutes (20:59–21:18 UTC, Oct 1), and short network issues in Mumbai and Columbus, Ohio. The Madrid performance problem and the Workers build delays carried over from September 30 are now resolved. Two older, minor incidents remain open: Cloudflare One clients being challenged on some sites, and incorrect geolocation for some WARP users. ([Cloudflare status](https://www.cloudflarestatus.com/)) - **GitHub**: Actions job delays (14:47–17:56 UTC, Oct 1) and a short period of elevated request latency. ([GitHub status](https://www.githubstatus.com/)) - **Discord**: higher API error rates for about an hour on October 1. **Zoom**: a short degradation across Contact Center, Meetings and Webinars plus a Google Workspace add-on issue, both resolved. **Ongoing minor issues:** Twilio is tracking carrier-specific messaging problems, including Silent Network Authentication failures on AT&T in the US, SMS delays to Telenet in Belgium and MMS delays to GCI in the US. Zoom Phone has an open issue with Polycom devices going offline. Akamai is still monitoring APAC origin connectivity tied to subsea cable repairs, which it expects to finish in early October. **All clear:** AWS, Google Cloud, Azure DevOps, Anthropic, Atlassian, Slack, Vercel, Heroku, DigitalOcean, Cursor, Groq, ElevenLabs, Cohere and Stability AI report normal operation. We could not load Stripe's or Meta's status pages this run, so their status is unconfirmed, though we saw no outage reports for either. IODA flagged short, localized connectivity drops in a few countries over the past day, and no global BGP or DNS-root event has been reported. **Bottom line:** the internet is up. If you run DNS through Akamai Edge DNS and changed records today, check that the changes have propagated.

No widespread internet outage is in progress as of 12:40 UTC on Thursday, October 1. AWS, Google Cloud, Azure, GitHub, Cloudflare's core network, Akamai, Anthropic, Discord, Slack, Atlassian, Vercel, Heroku, DigitalOcean and Stripe all report normal operation. This report covers the morning (US Eastern time). Anything that happens later in the day is not included. What is open right now (all minor, all limited in scope): - Zoom: the Zoom add-in for third-party calendar services (Google, Outlook) is degraded, which can stop meeting links from being created or updated from the calendar. The incident opened at 11:52 UTC and the cause has been identified. A separate, older issue with some Polycom devices going offline is still open. Joining meetings directly is not affected. (https://www.zoomstatus.com) - Twilio: several carrier-specific messaging and voice issues. SMS and voice failures to DigiMobil in Spain (since 08:32 and 10:40 UTC), delayed SMS delivery receipts from some US short codes, and older carrier issues in Cambodia, Alaska (GCI) and Australia (Telstra). These affect delivery to specific mobile networks only. (https://status.twilio.com) - Cloudflare: fixes are in place and being monitored for slow network performance in Madrid (since Sept 30, 10:31 UTC) and for delayed Workers builds (since Sept 30, 15:33 UTC). (https://www.cloudflarestatus.com) - OpenAI: elevated errors on ChatGPT "Space Pages", in monitoring since Sept 30. ChatGPT and the API otherwise work normally. (https://status.openai.com) Regional connectivity: IODA flagged short BGP-visibility drops overnight in several countries, including Burundi, South Sudan, the DR Congo, Ethiopia and Argentina. These are localized national or network-level signals, not a global routing event. No major BGP hijack or route leak was reported. (https://ioda.inetintel.cc.gatech.edu) Recently resolved (past 72 hours): on September 30, Cloudflare had network performance problems in Los Angeles (13:49 to 19:18 UTC, affecting services including R2 and Containers) and a WARP connectivity issue in Newark, NJ. Both are resolved. Bottom line: the internet is up. The open issues are narrow and only affect specific features, carriers or cities. Note: an Internet Society Pulse analysis published today on the Moscow M9 hub failure covers an incident from August 18, 2026, not a new one. (https://pulse.internetsociety.org/en/blog/2026/10/inside-the-m9-outage-measuring-the-impact-of-a-major-russian-internet-hub-failure)

No internet-wide outage is in progress as of about 20:20 UTC on September 30, 2026. AWS, Google Cloud, Azure, Azure DevOps, GitHub, Anthropic, Discord, Slack, Atlassian, Vercel, Heroku, DigitalOcean, Stripe and the smaller AI platforms we track all report normal operation. Today's open incidents are small and mostly recovering. **OpenAI: elevated API latency (recovering)** OpenAI opened an incident at 17:05 UTC for elevated latency on some API requests, with Chat Completions and Responses marked degraded. A mitigation is in place and OpenAI is monitoring recovery. A separate issue with elevated errors in ChatGPT Space Pages, open since 02:20 UTC, is also in monitoring. Source: https://status.openai.com **Cloudflare: Madrid performance and Workers build delays (monitoring)** Cloudflare reported network performance issues in Madrid from 10:31 UTC and delays to Cloudflare Workers builds from 15:33 UTC. Fixes are deployed for both and Cloudflare is monitoring. The Asia-Pacific network degradation that Cloudflare had open since September 23 no longer appears among its active incidents. Two older low-impact issues remain open: Cloudflare One clients being wrongly challenged on some sites (since September 22) and WARP geolocation errors (since August 27). Source: https://www.cloudflarestatus.com **Akamai: APAC origin errors linger** Akamai's Canada edge delivery incident from September 28 is no longer listed. Its APAC origin connectivity incident stays in monitoring while an upstream carrier finishes repairs on the damaged subsea cables. Akamai says immediate impact has subsided, but intermittent errors are possible until the work is done. Source: https://www.akamaistatus.com **Twilio and Zoom: carrier-level issues** Twilio is tracking SMS failures from some short codes to several networks in Chile (recovering) and SMS delays and failures to Metfone, Viettel, Beeline and Sotelco subscribers in Cambodia (cause identified). Zoom is still working with a provider on Polycom desk phones that went offline on September 25, which is affecting Zoom Phone devices. Sources: https://status.twilio.com, https://www.zoomstatus.com **Recently resolved: Spotify outage (September 29)** Spotify went down for a large number of users on Tuesday, September 29. Downdetector reports started climbing around 9:30 to 9:45 AM ET (13:30 to 13:45 UTC) and peaked near 10:41 AM ET. Downdetector received more than 200,000 reports from 173 countries, about 46% of them from the US. Most complaints were about the mobile app (roughly 58%) and audio streaming (21%). Service came back later that morning. Spotify has not given a public cause. This happened after our September 29 report was filed, so it appears here. Source: https://www.forbes.com/sites/zacharyfolk/2026/09/29/spotify-outage-thousands-of-users-report-problems-with-music-streaming-app/ **Other notes** Crowd-sourced trackers show scattered reports for LinkedIn and Grok today, but neither company has confirmed a problem and we could not verify real impact. Microsoft retires the Azure NVv4 GPU VM series today. That is a scheduled retirement, not an outage. Meta's status page could not be read this run, and we found no reports of a Meta disruption. **Bottom line:** the internet is up. Today's incidents are regional or limited to single products, and most are already recovering.