Cloudflare has another technical glitch: the internet will be down worldwide
Cloudflare servers are probably down again. The world is experiencing a massive outage of Internet resources for the second time in a week.
Cloudflare servers are probably down again. The world is experiencing a massive outage of Internet resources for the second time in a week.
Cloudflare servers are probably down again. The world is experiencing a massive outage of Internet resources for the second time in a week.
According to Downdetector, many sites are down.

Users are massively complaining about problems with Western websites and online services.

On November 18, a Cloudflare network outage knocked out thousands of websites around the world and in Ukraine for several hours. Now the company has released a report and admitted that it was not a hacker attack, but an internal bug.
While changing access rights to the ClickHouse database, which generates the configuration file for the Bot Management system, the file mistakenly contained twice the number of bot «signs». The file exceeded the size limit, the traffic checking module for bots was unable to process it and began massively returning 5xx errors to users instead of sites.
Since this file is updated every few minutes and instantly distributed to all servers, the failure quickly became global. Some data centers managed to download the correct version, others the «broken» one, so the network sometimes crashed, then partially recovered. Only at 14:30 UTC did engineers stop the distribution of the incorrect file, replace it with a stable version and restart the proxy; completely normal network operation was restored at 17:06.
Cloudflare emphasizes that the incident was not a DDoS attack. At first, the team suspected it, the day before the company repelled record attacks by the Aisuru botnet, and during the failure, an independent status site also stopped opening. However, analysis of the logs showed that the «culprit» was an internal configuration file that was incorrectly formed after changing the access settings.
UCloud and GigaCloud commented on the situation.




