Optimizely incident
Cloudflare experiences global Dashboard and Cloudflare API service issues affecting Optimizely services
Optimizely experienced a major incident on December 5, 2025 affecting Singapore and Norway East and 1 more component, lasting 45m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Dec 05, 2025, 09:05 AM UTC
Cloudflare experiences global Dashboard and Cloudflare API service issues affecting Optimizely services. Further detail will be provided as more information becomes available.
- monitoring Dec 05, 2025, 09:14 AM UTC
A fix has been implemented by Cloudflare. We are monitoring the results.
- monitoring Dec 05, 2025, 09:29 AM UTC
Cloudflare Resolved their incident. We continue close monitoring of Optimizely service health.
- resolved Dec 05, 2025, 09:50 AM UTC
Optimizely’s monitoring confirm continuous service health since 09:12 (UTC). Incident Resolved.
- postmortem Dec 05, 2025, 10:32 AM UTC
## Cloudflare service issues, impacting multiple Optimizely services - December 5, 2025 An initial root cause has been provided by our third-party vendor, Cloudflare, [https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q](https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q) A recent change to how Cloudflare’s Web Application Firewall parses requests temporarily caused portions of Cloudflare’s network to become unavailable. The issue lasted from December 05, 2025 - 08:56 \(UTC\) to December 05, 2025 - 09:12 \(UTC\). Cloudflare informs that this was not an attack; the change was deployed to help mitigate the industry-wide vulnerability disclosed this week in React Server Components. For the final Post Mortem of the Cloudflare outage on December 5, 2025, we refer to Cloudflare's published Post Mortem, [https://blog.cloudflare.com/5-december-2025-outage/](https://blog.cloudflare.com/5-december-2025-outage/)