Hundreds of websites and services have been rendered inaccessible by a now-resolved outage at web application security and performance firm Cloudflare.
The company confirmed in a statement on its service status page that it had suffered a “critical incident” and connectivity in its network has been “disrupted in broad regions” as a result. “Customers attempting to reach Cloudflare sites in impacted regions will observe 500 errors. The incident impacts all data plane services in our network,” it said.
The status page said the issue has now been resolved within an hour of the firm, which claims to be “trusted by millions of internet properties”, reportedly rolling out a fix for it at 8.20am.
According to data accrued by the DownDetector website, which compiles user-generated reports of downtime incidents for tracking and monitoring purposes, the incident appears to have begun just before 7.15am.
While the outage itself was relatively short-lived, the downtime incident is known to have knocked a number of high-profile web services offline – including voice over IP app Discord and the hugely popular online game Minecraft – and has also been linked to the onset of technical difficulties for users of Microsoft Teams, Amazon Web Services and various Google services.
Several users of social media site Twitter raised concerns about the fact that a single service provider experiencing technical difficulties can lead to so many other companies going down, too.
Cloudflare going down and half the internet going down with it (and half the people freaking out over it) is a perfect example why having something as important to everyday life like the internet rely on a single service is stupid
– Luna~♡ (@LunasTLs)
June 21, 2022
Huge chunks of the internet being inaccessible due to Cloudflare being down highlights a problem. This is exactly the opposite to how the web was designed to function #InternetDown pic.twitter.com/xO9jurEVxU
– TedBot 2000 (@TedAylmer)
June 21, 2022
Computer Weekly contacted Cloudflare for further details on the cause of the outage and the steps it was taking to prevent it happening again, but had not received a response at the time of publication.
