Yesterday, Cloudflare experienced a widespread outage that disrupted access to numerous websites and online services across the globe. The incident, which lasted for approximately 45 minutes, affected a large portion of the internet due to Cloudflare’s central role in managing web traffic, security, and content delivery for millions of domains.
So, what happened Bal?
The outage was traced to a configuration error during a routine network update. Cloudflare’s engineers identified that a change in the routing configuration caused a cascade of failures across several data centers. This led to a temporary loss of connectivity for many websites relying on Cloudflare’s infrastructure.
Cloudflare quickly rolled back the faulty update and restored normal operations. The company confirmed that the issue was not the result of a cyberattack or external interference but rather an internal technical misconfiguration. And that’s good – in a strange kind of way. Imagine if it was a cyberattack…!
Which websites and services were impacted?
Because Cloudflare acts as a content delivery network (CDN) and security layer for a vast number of websites, the outage had a ripple effect across the internet. Users attempting to access affected sites encountered “502 Bad Gateway” or “Connection Timed Out” errors.
Some of the major platforms and services impacted included:
- Discord – Users reported connection issues and message delivery failures.
- Shopify – Many online stores were temporarily inaccessible or unable to process transactions.
- Medium – The blogging platform experienced downtime for both readers and writers.
- Coinbase – Cryptocurrency traders faced difficulties accessing their accounts and viewing market data.
- DoorDash – Food delivery orders were delayed or failed to process.
- Feedly – The RSS reader service was unavailable for a short period.
Smaller websites and independent businesses using Cloudflare for DNS or DDoS protection were also affected, highlighting the company’s extensive reach across the web. And this is also why I couldn’t tweet much within that 45 minute period!
Cloudflare’s Response
Cloudflare’s engineering team provided real-time updates through its status page and social media channels. Within an hour, most services were restored, and the company issued a detailed post-incident report explaining the root cause and steps taken to prevent similar issues in the future. If you’re interested in that report – go ahead and google it.
The company emphasized improvements to its deployment process, including additional safeguards for configuration changes and enhanced monitoring to detect anomalies faster.
Lessons from the Outage
The incident underscored the internet’s reliance on a few key infrastructure providers. While Cloudflare’s services improve performance and security for millions of websites, the outage demonstrated how a single point of failure can have global consequences.