Cloudflare Outage History

Cloudflare conducted scheduled maintenance in the Manchester region (MAN). The maintenance window began around 1:50 AM UTC and the status page showed maintenance during this period, with updates issued as needed. The maintenance lasted about 7 hours and 45 minutes, with services in the Manchester region returning to normal by 9:35 AM UTC. The incident involved the Manchester regional component and did not indicate wider impact. The provider issued two status updates during the incident.

Cloudflare reported a degraded IP Geolocation feature in the Cloudflare Dashboard, with minor inaccuracies affecting a very limited number of IP addresses. This could cause some traffic to appear as Unknown or to be assigned to an incorrect country or region in the dashboard. The incident began at Dec 23, 2025 10:45 AM UTC and was resolved by Dec 23, 2025 4:05 PM UTC, lasting about 5 hours 20 minutes. The affected component was Cloudflare Sites and Services / IP Geolocation. The provider issued 3 status updates during the incident to communicate investigation progress and resolution.

Cloudflare reported degraded network performance in South America due to a route leak from an upstream transit provider. Users in the region may have experienced slower connections or intermittent connectivity while Cloudflare mitigated the impact.

The outage began around Dec 23, 2025 6:28 AM UTC and Cloudflare moved to a degraded state at Dec 23, 2025 6:30 AM UTC, citing a route leak affecting network performance in South America. Cloudflare issued two status updates during the incident, and services returned to normal by Dec 23, 2025 7:10 AM UTC, for an outage duration of about 42 minutes.

Cloudflare conducted scheduled maintenance in the STL (St. Louis) region from 6:00 PM UTC to 10:05 PM UTC. During this window, users in the STL region may have experienced intermittent connectivity or degraded performance as traffic was handled during the maintenance window. The maintenance was announced on Cloudflare's status page with an in-progress update indicating the work was underway.

Cloudflare published two official status updates during the incident: an initial in-progress notice at Dec 22, 2025 6:05 PM UTC and a follow-up at Dec 22, 2025 10:05 PM UTC indicating the maintenance had concluded and services had returned to normal. The impact was regional to the STL region and not indicated to affect Cloudflare services globally.

Cloudflare reported degraded availability in Cloudflare Workers AI for a subset of models, with an investigation launched. The issue affected specific AI models, including @cf/openai/gpt-oss-120b and @cf/baai/bge-base-en-v1.5, and began at 3:00 PM UTC. Cloudflare issued an initial status update noting degraded availability and an ongoing investigation, with a second update as the situation progressed. The incident lasted 1 hour 40 minutes and concluded with services restored to normal by 4:40 PM UTC.

Cloudflare conducted scheduled maintenance at the GRU data center in São Paulo, causing temporary access issues and degraded performance for some users. The outage began at 5:00 AM UTC and was resolved by 10:05 AM UTC, lasting about 5 hours. The provider posted two official updates during the incident, noting that maintenance was in progress and later confirming restoration. The impact appeared regional to the GRU area, with user reports indicating connectivity issues during the maintenance window.

An extended incident affected Cloudflare's network, causing degraded performance and intermittent connectivity for sites relying on Cloudflare. The outage began at Dec 19, 2025 11:20 AM UTC with the Network component briefly down, and it impacted two components: Network and Containers within Cloudflare Sites and Services. Users across regions reported errors and slow responses during the incident, and there was a brief period of downtime in the early window of the event.

Cloudflare logged a sequence of regional maintenance windows and latency events spanning 2025-12-16 to 2025-12-18, affecting multiple services in several regions. The incident began with a Singapore maintenance window around 4:00 PM UTC, which was noted as in progress at 4:05 PM UTC. On 8:00 PM UTC, Cloudflare reported possible network congestion in western North America, with elevated error rates in delivery and upload paths that could cause retries for video-related requests. Singapore components (Stream and R2) were recovered by 9:00 PM UTC.

Cloudflare experienced a prolonged degradation impacting multiple services, including R2 storage access, GraphQL API queries, CDN cache purging, and Analytics. The issue affected users loading Cloudflare sites and querying data across regions, with reports spanning Western Europe, the UK, India, France, Brazil and beyond. The incident began during a scheduled maintenance window and persisted for about 36 hours, with recovery completed in the early afternoon of the following day. Cloudflare issued a series of updates over the course of the incident, working to identify and apply fixes, and reporting progress as services returned to normal. The affected components included R2, GraphQL API, CDN Cache Purge, and Analytics.

The Cloudflare maintenance window in the MCI (Kansas City) region began at 11:00 AM UTC and led to degraded performance for users in that area. The incident was acknowledged when the status changed to a degraded state at 11:05 AM UTC with the note that scheduled maintenance was in progress. The window lasted roughly 11 hours, and service was restored by 10:05 PM UTC as the status returned to normal. Cloudflare issued 2 updates during the incident to communicate progress and resolution.