By This is a developing story – see updates at the end of the post
Cloudflare has run into another global outage, leading to many websites going offline and showing an internal error (HTTP 500). This error is caused by Cloudflare and not from the websites (origin servers).
Similar to the previous global outage on November 18th 2025, a lot of well known websites (e.g. LinkedIn) are affected.
We – Geeker's Digest – also use Cloudflare. But so far we don't seem to be affected. Yet.
Cloudflare customers with an Enterprise plan seem to be affected this time.
Updates
Cloudflare confirms the issues and mentions problems with their API and dashboard on their status page.
09:20 UTC: Cloudflare reports they have fixed the issue and are monitoring the situation.
We can confirm that affected sites seem to be working again. From our own monitoring checking external sites we can tell that the downtime of affected sites was approximately 26 minutes.
09:40 UTC: Cloudflare now reports issues with workers and elevated errors in worker scripts. These are often involved for scripts created by Cloudflare customers to handle specific actions and implement programmatic logic (e.g. show custom maintenance page on Cloudflare).
10:00 UTC: Additional information has been published which explain the reason for the internal server errors. A mitigation for a recent critical vulnerability in React applications (CVE-2025-55182) was added in the Cloudflare Managed Rules, a security ruleset (previously known as WAF in Cloudflare). An error inside the adjusted rule seems to have caused the internal server errors.
