Cloudflare Outage History

Cloudflare reported an incident impacting Cloudflare Workers scripts and R2 storage, causing degraded performance for users. The issue began at 3:15 PM UTC with an elevated error rate and prompts for investigation. The problems affected Workers and R2 components (Cloudflare Sites and Services / R2), potentially causing intermittent errors and slower responses for users running Worker code or accessing R2 storage.

Over the course of the incident, Cloudflare issued four status updates. A fix was implemented and monitoring followed as services returned toward normal. The components progressed from degraded to healthy, and the incident was resolved by 7:15 PM UTC, lasting roughly four hours.

The Cloudflare Snippets update flow experienced an outage affecting a subset of users who were unable to update Snippets on their zones. The outage began at 4:30 PM UTC and was resolved by 10:25 PM UTC, lasting roughly 5 hours and 55 minutes. Cloudflare documented the issue on their status page as Snippets updates and conducted investigations with mitigation steps, noting the affected component as Cloudflare Sites and Services / Snippets. The impact appeared limited to the Snippets update flow and did not indicate a broader disruption across other Cloudflare services. Cloudflare issued 2 status updates during the incident.

Cloudflare reported degraded email delivery impacting email notifications, including Access One Time PIN, password resets, and two-factor authentication, while Access and Dashboard authentication via other methods remained available. The incident began at 3:20 PM UTC and was resolved by 3:40 PM UTC, lasting about 20 minutes. Cloudflare issued two status updates during the event, with Dashboard and Access briefly listed as degraded before returning to normal.

The Cloudflare Durable Objects service in Lisbon, Portugal and London, UK experienced an elevated rate of overload errors, causing degraded performance for users relying on those regions. The issue began around 11:15 AM UTC and persisted until 1:10 PM UTC, lasting approximately 1 hour and 55 minutes. Affected customers in these areas may have seen timeouts or failed operations related to Durable Objects.

Cloudflare’s status page shows two official updates during the incident. The first indicated the issue and an ongoing investigation around Nov 27, 2025 11:12 AM UTC with the state moving to degraded at Nov 27, 2025 11:15 AM UTC. The second update on Nov 27, 2025 1:10 PM UTC confirmed recovery and return to normal. The disruption was limited to the Durable Objects component within Cloudflare Sites and Services and affected Lisbon and London locations.

Cloudflare FRA (Frankfurt) maintenance caused degraded service in the Frankfurt region. The work began around 10:00 PM UTC and lasted about 9 hours, with users experiencing intermittent connectivity and performance issues during the window. A San Jose area user reported issues at 2:01 AM UTC.

The provider issued two status updates during the incident. The status moved from up to warn at Nov 26, 2025 10:05 PM UTC with maintenance in progress, and the service returned to normal by Nov 27, 2025 7:05 AM UTC. The impact appears concentrated in the Frankfurt FRA region, with limited global reports.

Cloudflare experienced a broad outage affecting multiple regions and services, including Cloudflare Sites and Services and Workers AI functionality. Data centers in Osaka (KIX), Xiangyang (XFN), Ashburn (IAD), Amman (AMM), and Buenos Aires (EZE) reported degraded performance or outages at various times, with users worldwide experiencing connectivity issues and site errors. Some services such as Web Analytics weekly emails were not delivered during the incident, and users observed HTTP 499 and 5xx errors in Osaka. The disruption shows a widespread geographic reach across the Americas, Europe, Asia, and Australia.

Cloudflare experienced a brief degraded performance affecting Cloudflare Sites and Services / Workers Builds. The incident involved an increased failure rate for new Workers Builds and higher latency in the Builds API, potentially impacting builds and deployment workflows. The issue began at 2:45 PM UTC and was resolved by 4:40 PM UTC, lasting about 1 hour 55 minutes. The Cloudflare status page issued 2 updates during the incident as teams investigated and implemented mitigation.

Cloudflare conducted scheduled maintenance at the Vilnius data center (VNO) on 2025-11-24, resulting in degraded service for users routed through that region. The maintenance window began at 12:00 AM UTC; the status page moved to a degraded state at 12:05 AM UTC and the incident concluded with the status returning to up at 2:05 PM UTC after roughly 14 hours and 5 minutes. The provider issued two official updates during the window.

Cloudflare experienced degraded performance across Load Balancing and Health Checks, impacting health processing, notifications, analytics, and potentially routing decisions. The disruption affected two Cloudflare components: Load Balancing and Monitoring, and Health Checks, and lasted from 11:50 PM UTC to 1:20 AM UTC, about 1 hour 30 minutes.

Cloudflare issued two status updates during the incident, describing ongoing investigation into health processing delays and their impact on customer notifications and analytics. The components returned to normal after the final update, with services restored to their usual operating state.

Cloudflare experienced an incident impacting the API and Dashboard, with errors observed in Workers AI inference requests. The incident began at Nov 21, 2025 4:45 PM UTC and included regional maintenance events in Osaka and Singapore as updates progressed. Cloudflare notes that cached content via the CDN and other edge protections were not affected.

The provider issued 6 status updates over the course of the incident and the disruption affected 3 components: API, Dashboard, and Workers AI. The outage lasted about 5 hours 20 minutes, ending at Nov 21, 2025 10:05 PM UTC, after which services returned to normal.