Cloudflare Outage History

Cloudflare conducted scheduled maintenance in the London region (LHR) on {{date:2025-07-01}}. The status page showed the work as in progress with the note 'In progress - Scheduled maintenance is currently in progress' beginning at 1:00 AM UTC. This maintenance window could have caused a brief regional disruption for users in London.

The maintenance concluded with the region returning to normal at 5:35 AM UTC, lasting about 4 hours and 35 minutes. The impact was limited to the London area; other regions did not report issues.

A subset of Cloudflare Containers applications were unable to start, causing startup failures for affected workloads. The incident was detected at Jun 30, 2025 8:20 PM UTC when Cloudflare moved the status to a degraded state and began investigating. The impact window was noted as 18:05 - 19:57 Jun 30, 2025, with a UTC reference of 20:17. The issue was short-lived, and service was restored by Jun 30, 2025 8:25 PM UTC.

Cloudflare issued 2 status updates during the incident to communicate the investigation and resolution, and the disruption was localized to specific containers rather than a broad service outage.

Cloudflare experienced a multi-day incident affecting Web Analytics data from its RUM beacon and related services. The issue began with a scheduled Auckland maintenance and progressed to Web Analytics outages, with RUM POST requests failing and 404 errors that led to missing analytics data for Free, Pro, and Biz plans. The disruption extended to multiple Cloudflare components, including Web Analytics, and later involved other areas such as R2 latency in the ENAM region and Browser Isolation related traffic. The outage spanned from Jun 25, 2025 7:25 PM UTC to Jun 30, 2025 4:35 PM UTC, with regional maintenance and follow-up issues reported over several days.

Cloudflare conducted scheduled maintenance in the Los Angeles (LAX) region, which caused brief service degradation for the area. The maintenance began at 9:00 AM UTC and the status moved to degraded at 9:05 AM UTC as work started. The maintenance window lasted approximately 4 hours and 5 minutes, with services restored by 1:05 PM UTC.

The provider issued 2 official updates during the incident: one noting maintenance in progress and another confirming restoration. The impact was localized to the LAX region, with no broader global impact indicated.

Cloudflare Stream on-demand video playback experienced intermittent errors beginning around Jun 23, 2025 6:41 PM UTC. The status page transitioned to a warning at Jun 23, 2025 6:45 PM UTC, with investigation ongoing. A Madrid maintenance window started around Jun 25, 2025 12:01 AM UTC and the service was restored by Jun 25, 2025 5:35 AM UTC.

Cloudflare published three official updates during the incident describing investigation, the maintenance activity in Madrid, and restoration. The issue affected Cloudflare Stream on-demand playback, resulting in degraded playback experience for users during the event.

Cloudflare reported Magic WAN provisioning issues beginning around Jun 23, 2025 1:24 PM UTC, with degraded network availability for Magic WAN and provisioning problems for customers lacking authorized prefixes. User reports started around 1:45 PM UTC, including at least one note of WAN outage in Nacka, Sweden. The outage persisted for nearly four hours as Cloudflare investigated the cause and worked on mitigation.

Cloudflare conducted scheduled maintenance in the YYZ (Toronto) region beginning at 8:00 AM UTC. The status transitioned to a degraded state as the work started, with Cloudflare updating the incident to indicate maintenance and that updates would be provided as necessary. The maintenance window lasted about 3 hours and 5 minutes, finishing around 11:05 AM UTC and the status returning to normal. The status page described the work as in progress during the window, and the impact appears localized to the YYZ (Toronto) region.

Cloudflare Gateway in Cloudflare Zero Trust experienced a brief issue saving HTTP policies when using the Application selector with full application categories. This prevented policy configuration changes for affected users and caused degraded workflow within Gateway components. The incident was resolved after a short period and the Gateway returned to normal operations shortly after.

Cloudflare carried out scheduled maintenance at the MXP Milan data center beginning at 12:00 AM UTC. The status page noted that maintenance was in progress during the window and described routine work for the Milan site. The window was regional, and traffic routed through MXP may have experienced intermittent connectivity during the maintenance.

The maintenance lasted about 5 hours and 35 minutes and concluded at 5:35 AM UTC when the status page indicated normal operations. Cloudflare posted 2 status updates during the incident. The impact was localized to the Milan MXP data center with no confirmed global outages.

Cloudflare conducted scheduled maintenance at the BGW Baghdad data center. The maintenance window began at 3:02 AM UTC and was listed as in progress at 3:05 AM UTC. The work continued for about 2 hours and 33 minutes, with the Baghdad facility returning to normal by 5:35 AM UTC. Cloudflare issued two status updates during the incident, and the impact was localized to the BGW Baghdad data center, with services returning to full operation once maintenance completed.