Major App Outages Hit Reddit, X, and Monzo Sparking Fears
On January 13, 2026, Reddit, X (formerly Twitter), and Monzo all suffered outages within hours of each other, leaving users concerned about ...
Widespread Impact:: The outage affected major platforms including X (formerly Twitter), Spotify, OpenAI, and Amazon Web Services.
Root Cause:: A bug in Cloudflare's Bot Management system, triggered by a database permissions change, led to the generation of an oversized feature file that overwhelmed the network.
Rapid Response:: Cloudflare's team identified and resolved the issue within a few hours, restoring core traffic flow by 14:30 UTC and fully resolving all systems by 17:06 UTC.
Vulnerability of Centralized Infrastructure:: The incident underscores the fragility of relying on a small number of providers for critical internet services. Why does this matter? Outages like these can disrupt business operations, hinder communication, and impact user experiences across the globe.
Cloudflare acts as a critical intermediary for a significant portion of internet traffic, providing CDN, security, and DNS services. Its outage cascaded through the internet, demonstrating how interconnected the web has become.
The outage was triggered by a change in a ClickHouse database system's permissions, causing the Bot Management system to generate an unexpectedly large "feature file." This file, propagated across the network, exceeded software limits, leading to system failures. The issue manifested as HTTP 5xx errors and increased latency for users.
Core CDN and Security Services:: HTTP 5xx status codes were widely served.
Turnstile:: Failed to load.
Workers KV:: Returned elevated HTTP 5xx errors.
Dashboard:: Most users were unable to log in.
Email Security:: Temporary loss of access to an IP reputation source.
Access:: Widespread authentication failures.
Cloudflare addressed the issue by:
Stopping the generation and propagation of the bad feature file.
Manually inserting a known good file into the distribution queue.
Restarting the core proxy.
Cloudflare is implementing measures to prevent future incidents, including:
Hardening ingestion of Cloudflare-generated configuration files.
Enabling more global kill switches for features.
Eliminating the ability for core dumps to overwhelm system resources.
Reviewing failure modes for error conditions across all core proxy modules.
Diversify Services:: Don't rely on a single provider for all critical services.
Monitor Status Pages:: Keep an eye on the status pages of your key service providers.
Implement Redundancy:: Where possible, implement redundant systems to ensure business continuity.
Businesses and individuals who rely heavily on Cloudflare for their online presence and services were most affected by this outage.
Q: What caused the Cloudflare outage?
The outage was caused by a bug in Cloudflare's Bot Management system, triggered by a database permissions change that led to an oversized feature file.
Q: How long did the outage last?
Core traffic was largely restored by 14:30 UTC, with all systems functioning normally by 17:06 UTC on November 18, 2025.
Q: What services were affected?
Services affected included core CDN, Turnstile, Workers KV, the Cloudflare Dashboard, Email Security, and Access.
Cloudflare's outage highlights the internet's reliance on a few key infrastructure providers.
A seemingly small configuration change can have widespread consequences.
Monitoring service status and diversifying providers can help mitigate the impact of future outages.
Do you think incidents like this will become more or less frequent in the future? Let us know in the comments!
Share this article with others who need to stay ahead of this trend!
On January 13, 2026, Reddit, X (formerly Twitter), and Monzo all suffered outages within hours of each other, leaving users concerned about ...
On October 19, 2025, a widespread Xfinity by Comcast internet and TV outage impacted thousands of users across the United States. The disrup...
Several online platforms and mobile networks experienced outages recently, causing disruptions for users worldwide. These incidents highligh...
⚠ Disclaimer: Yanuki provides article summaries and links for reference only. Yanuki does not endorse, verify, or guarantee the accuracy of third-party sources. Please review original sources and verify information independently. Managed by the Yanuki Data Engine. Full Disclaimer