A chronological record of significant internet infrastructure failures and service disruptions in 2025. Each incident includes root cause analysis, duration, and scope of impact.
Zoom experienced a partial outage affecting meeting join and host features for users across the Americas. Thousands reported meetings dropping or failing to connect, disrupting work calls and webinars.
Azure East US compute outage hits virtual machines and AKS
Azure customers in the East US region reported failures provisioning virtual machines and Azure Kubernetes Service clusters. Teams relying on Azure for production workloads without geo-redundancy faced extended disruptions.
DURATION
~3 hours
AFFECTED
Azure customers in East US using VM and AKS services
Discord's API went down for approximately two hours, causing widespread failures for bots, integrations, and normal messaging. Bot-dependent servers and gaming communities were particularly affected.
A routing issue within Cloudflare's network caused elevated latency and partial unavailability for a broad set of customers across multiple regions. Sites relying on Cloudflare for DDoS protection and CDN saw increased error rates for roughly an hour.
DURATION
~1 hour
AFFECTED
Cloudflare CDN customers across multiple regions
ROOT CAUSE
BGP routing misconfiguration affecting several Cloudflare edge PoPs
Spotify suffered a playback outage affecting mobile and desktop apps. Users reported blank libraries, songs failing to start, and login loops. The outage occurred during peak evening hours in Europe and North America.
DURATION
~2.5 hours
AFFECTED
Spotify users in Europe and North America
ROOT CAUSE
Backend service failure; Spotify resolved without publishing a detailed post-mortem
GitHub.com experienced degraded performance including slow page loads, delayed Action runs, and intermittent API timeouts. Engineers traced the issue to database query slowdowns affecting multiple services.
DURATION
~2 hours
AFFECTED
GitHub users and CI/CD pipelines globally
ROOT CAUSE
Database query performance degradation
Data sourced from public post-mortems, official status pages (statuspage.io, instatus.com), and credible tech reporting. Duration estimates are approximate based on incident start/resolution timestamps. If you notice an inaccuracy or want to suggest an addition, contact us.