Cloudflare says it has fixed an issue that caused a 25 minute outage on Friday, following a major, hours-long outage last month
from content delivery and DDoS protection to DNS services. When Cloudflare has an outage, it doesn't just affect one company; it impacts a Dane Knecht / @dok2001 : You can read the details of what went wrong this morning in the post below. We let the Internet down again today; We're locking down all changes in order to ensure we have better mitigation and rollback systems before we begin any again. https://blog.cloudflare.com/ ... @anakin : Cloudflare is down again, two weeks after breaking the internet. Hetzner must be printing money. [image] @cloudflare : Cloudflare experienced a significant traffic outage on December 5, 2025, starting approximately at 8:47 UTC, for approximately 25 minutes. We are sorry for the impact that it caused to our customers and the Internet. Here's what happened: https://blog.cloudflare.com/ ... Artem Russakovskii / @artemr : @Cloudflare @eastdakota The post mortem for the 25-minute @Cloudflare outage from last night. https://x.com/... LinkedIn: Harshit Maurya : ⚠️ What happened at Cloudflare yesterday? — Around 08:47 UTC, a massive chunk of the internet—including Zerodha, Canva, X, and Spotify—suddenly started failing with 500 errors. … Bluesky: @swiftonsecurity.com : To be fair to Cloudflare, this incident is bit different. Context: There is a massive software vulnerability recently released in a web platform that most teams are not gonna get to fast enough or know and there's gonna be a lot of victims — But they did screw up. — blog.cloudflare.com/5-december- 2... Threads: Benedict Evans / @benedictevans : It's sad to see Cloudflare going down again, but in this day and age there's really no excuse for a big Internet company not to be using a CDN. Mastodon: @ngate@mastodon.social : Ah, #Cloudflare, the self-proclaimed internet savior, decided to take a 25-minute #nap on December 5, 2025, leaving 28% of their HTTP traffic in a state of existential dread. 😴🔌 But fear not, dear reader, their blog was quick to remind us that their corporate jargon is as resilient as ever. … Forums: r/rust : Cloudflare outage on December 5, 2025 r/CloudFlare : Cloudflare outage on December 5, 2025 r/rustjerk : This is a straightforward error in the code, which had existed undetected for many years. This type of code error is prevented by languages with strong type systems. …
Context & Ripple Effects
This follows Cloudflare’s major November incident, for which the company said a database-permissions change caused the disruption, and its CTO acknowledged the failure’s broad effect on customers and internet traffic.
The new, shorter outage matters because it occurred before Cloudflare had fully rebuilt confidence after that earlier event. Cloudflare’s decision to freeze changes makes the immediate focus operational control rather than a new external threat.
First-order effects
- Customers whose delivery, DNS, or protection traffic runs through Cloudflare faced 500 errors during the 25-minute incident, including the named services Zerodha, Canva, X, and Spotify.
- Cloudflare is pausing changes while it improves mitigation and rollback procedures, constraining near-term operational releases as it prioritizes reliability.
Second-order effects
- A second incident so soon after the November outage affecting X, ChatGPT, and others gives customers reason to scrutinize their dependency on a single edge provider and the quality of their fallback plans.
- The change freeze shifts pressure onto Cloudflare’s engineering process: fixes and feature changes will need stronger rollback discipline, potentially trading deployment speed for lower operational risk.
Third-order effects
- Repeated failures at a provider embedded across delivery, DNS, and security services reinforce that internet resilience depends on how customers design for provider outages, not only on a provider’s stated uptime.
- If peers and customers respond by emphasizing failover and change-control evidence, resilience practices could become a more important basis of competition among edge-infrastructure providers.
The trend: The incident is part of a broader push to make highly concentrated internet infrastructure more resilient through stricter change management and customer-level redundancy.