Cloudflare Outage History

The Cloudflare WARP service experienced errors when connecting to MySQL, followed by related issues affecting Pages builds and Cloudflare Workers. The incident began around 8:13 AM UTC and persisted through 4:05 PM UTC, with users reporting connection errors, build failures at the end of builds, and degraded script execution. The outage appeared to be limited to a subset of Cloudflare services rather than the entire platform, but multiple services were affected during the event.

Cloudflare issued multiple status updates throughout the incident, including investigations, identification of the issues, and ongoing mitigations as services gradually returned to normal. The situation underscores the impact on WARP connectivity, Pages builds, and Workers during the incident, with services resuming normal operation after the final updates.

Cloudflare conducted a scheduled maintenance window in the Nasiriyah region (XNH). The window began at 3:02 AM UTC and, by 3:05 AM UTC, the status page listed the incident as in-progress. Users in the Nasiriyah area may have experienced intermittent connectivity during the maintenance window. The maintenance concluded with services restored by 5:35 AM UTC, after roughly 2 hours and 33 minutes. Cloudflare issued two status updates during the incident to communicate progress and restoration. The impact was localized to the Nasiriyah region and did not indicate global disruption.

Cloudflare experienced a multi-region degradation beginning at Jun 3, 2025 8:05 AM UTC during scheduled maintenance in CMH (Columbus). The issue impacted three main areas: the Cloudflare Dashboard (including issues with Browser Cache TTL), the Gateway service (geolocation connectivity concerns), and Access policy checks. Regions such as Hong Kong and Phoenix were involved as maintenance and investigations progressed, leading to degraded performance and intermittent access for some customers.

Cloudflare issued multiple status updates throughout the incident, detailing identified issues and ongoing maintenance efforts. Gateway and Access began to recover over the following hours, with components returning toward normal as repairs progressed. The incident lasted roughly 16 hours and 35 minutes, and affected components included Dashboard, Gateway, and Access, highlighting a broad but partial impact across multiple regions.

Cloudflare conducted scheduled maintenance in Macau (MFM) beginning at 6:00 PM UTC. The status page indicated the work with the message 'In progress - Scheduled maintenance is currently in progress,' and the incident transitioned from normal to a maintenance alert during the window. The maintenance lasted about 5 hours and 5 minutes and concluded at 11:05 PM UTC, after which the service was reported back to normal. The provider issued two official status updates during the window to communicate progress and completion of the maintenance.

Cloudflare experienced a short degradation in DNS updates within Cloudflare Sites and Services, with delays in propagation of DNS record updates. This caused DNS changes to propagate more slowly for a brief period, potentially affecting newly created or updated records.

The incident began at Jun 2, 2025 2:50 PM UTC and was resolved by Jun 2, 2025 3:05 PM UTC, lasting about 15 minutes. Cloudflare issued two status updates during the incident, describing the investigation and the subsequent restoration of normal DNS update propagation.

Cloudflare initiated scheduled maintenance at the EZE data center in Buenos Aires on 2025-06-02. The incident entered a warning state around 06:05 UTC, with maintenance listed as in progress and updates promised as necessary. The maintenance ran for about 7 hours, ending around 13:00 UTC when service status returned to normal. A total of two official status updates were posted during the event, describing the in-progress maintenance and its resolution. The impact was localized to traffic routed through the EZE region, with potential degraded performance or intermittent connectivity for affected users in that area.

Cloudflare conducted scheduled maintenance in the Najaf region (NJF) on 2025-06-02. During the maintenance window, services in the NJF region experienced degraded performance as the status changed to a warning. The window began at 3:01 AM UTC and concluded with the status returning to up at 5:35 AM UTC.

Cloudflare experienced degraded performance due to cached traffic latency affecting its CDN/Cache in Europe and Africa. Users loading resources from cached assets may have observed slower response times during the incident.

The issue began on 8:00 PM UTC and was resolved by 9:45 PM UTC, lasting about 1 hour and 45 minutes. Cloudflare issued three status updates during the incident, noting an investigation, a fix with ongoing monitoring, and eventual recovery. The impact appeared localized to Europe and Africa.

Cloudflare experienced degraded network performance focused on the Jakarta region while Basra scheduled maintenance was in progress. The Basra maintenance began at May 31, 2025 3:02 AM UTC and the incident was first flagged as a warning at 3:05 AM UTC. Jakarta region users began seeing connectivity problems around 3:50 AM UTC, with a Bandung, Indonesia user noting that many Cloudflare–protected sites were inaccessible during the window. This indicates a partial outage affecting sites routed through Cloudflare's network in multiple regions.

Cloudflare issued four status updates during the incident, describing ongoing Basra maintenance and Jakarta network issues, and indicating that conditions were improving over time. The status was restored to up at 5:35 AM UTC. The disruption lasted roughly two and a half hours and primarily impacted Cloudflare's Network services in the Basra and Jakarta regions.

Cloudflare's scheduled maintenance in the Kuala Lumpur region affected the Cloudflare Sites and Services / Workflows component, causing issues with deploying Workflows and degraded performance for users in that region.

The outage lasted about 4 hours, beginning at 6:01 PM UTC and ending at 10:05 PM UTC. Cloudflare issued four official updates during the incident to communicate the maintenance and eventual restoration. The impact was regional to Kuala Lumpur with Workflows experiencing degradation, and services returned to normal by the end of the window.