Cloudflare Outage History

Cloudflare carried out scheduled maintenance at the Seattle (SEA) data center on 2025-08-07, with a maintenance window from 8:00 AM UTC to 1:00 PM UTC, causing a brief disruption for users in the Seattle region. The incident was reflected on Cloudflare's status page, with two updates during the window: an in-progress notice and a final restoration update as services returned to normal by 1:00 PM UTC. The impact appeared localized to the Seattle region, with no broader service disruption observed.

Cloudflare reported a scheduled maintenance window in the AMM (Amman) data center that led to degraded service for the region. The maintenance began at 11:00 PM UTC and ran for about 8 hours and 5 minutes, with services restoring at 7:05 AM UTC.

Cloudflare reported degraded performance for Durable Objects in the Eastern North America region, with purge actions experiencing higher latency. This regional issue could slow down purge-related operations for customers in that geography. The incident began at 2:20 PM UTC and was resolved by 9:20 PM UTC.

Cloudflare posted two status updates as the incident progressed, first acknowledging investigation and later confirming restoration. The disruption was regional to Eastern North America and involved the Durable Objects component, with uptime returning as latency conditions improved.

Cloudflare conducted scheduled maintenance in the ORD (Chicago) region starting at Aug 6, 2025 8:20 AM UTC and completing by Aug 6, 2025 12:05 PM UTC. The maintenance window briefly manifested as degraded performance for some users while the status page showed the ORD region in progress, then reported completion once maintenance finished. The provider issued two updates during the incident, and overall services returned to normal after the maintenance concluded. User reports were limited during the window.

Cloudflare experienced delays affecting Cloudflare Access configuration changes and Web Analytics processing, resulting in slower policy updates and delayed analytics visibility for customers. Access authentication and policy enforcement remained functional, but configuration changes and analytics data delivery were behind schedule. Wrangler builds also faced intermittent issues during the incident. The outage affected 3 components: Cloudflare Access, Cloudflare Sites and Services / Analytics, and Wrangler builds. The incident began on Aug 5, 2025 4:00 PM UTC and was resolved by Aug 6, 2025 3:05 AM UTC.

Cloudflare experienced a multi-region disruption beginning on Jul 31, 2025 5:00 AM UTC with network routing problems in India. The issue expanded to Cloudflare WARP and Zero Trust, affecting new registrations and configuration changes, and later caused compression issues for Cloudflare Pages. The impact extended to Dubai connectivity and a separate Workers fault, with services intermittently degraded or partially available. The regional nature of the issues was evident, with Europe experiencing network performance problems by Aug 4, 2025 10:05 AM UTC and other localized disturbances.

Over the course of the incident, Cloudflare issued 14 official status updates across six components: WARP, Zero Trust, Pages, Network, Workers, and Web Analytics. The timeline included a Luanda maintenance window on Aug 1, 2025 3:10 AM UTC and ongoing mitigation efforts that gradually restored some services; India network routing was listed as restored by Aug 4, 2025 1:30 PM UTC and European issues were being resolved. Web Analytics attribution issues appeared on Aug 4, 2025 11:15 PM UTC and maintenance activity in Mombasa occurred on Aug 4, 2025 11:55 PM UTC. The incident concluded with overall service restoration on Aug 5, 2025 11:30 AM UTC.

Cloudflare experienced a multi-day degraded-operations event primarily impacting the Asia Pacific region, with Durable Objects availability degraded and WARP services affected. Customers may have encountered intermittent failures and slower responses, including issues with public API access, device registration, and dashboard analytics. The outage began around 11:01 PM UTC during scheduled maintenance and extended until 3:00 AM UTC, lasting about 2 days and 4 hours. The incident affected multiple components including Durable Objects, WARP, Network, and Web Analytics in the Cloudflare Dashboard.

Cloudflare scheduled maintenance in the IAD (Ashburn) region led to a brief DNS disruption and status page access issues. The maintenance window started at 8:30 AM UTC and ended by 11:05 AM UTC, lasting about 2 hours and 35 minutes. Users reported DNS problems during this period, consistent with a localized maintenance activity.

Cloudflare communicated via status updates, first indicating maintenance was in progress and later confirming the service was restored. The impact appeared limited to the IAD region, and there were no reports of widespread outages beyond the scheduled window.

Cloudflare carried out scheduled maintenance in the ALG (Algiers) region, causing degraded performance for users in that area. The incident began when maintenance started and the status was updated to reflect ongoing work. The outage began on 1:00 AM UTC and was resolved by 5:05 AM UTC, lasting about 4 hours and 5 minutes. The provider issued 2 status updates during the incident, and service returned to normal after maintenance completed. Impact was regional to Algiers with no indication of global disruption.

Cloudflare carried out scheduled maintenance in the TBS (Tbilisi) region, resulting in degraded performance for traffic routed through that area. The maintenance window began around 10:00 PM UTC and the issue persisted for about 17 hours, with recovery completed at Jul 25, 2025 3:05 PM UTC. The provider issued two status updates during the incident, reflecting the in-progress maintenance and eventual recovery. The degradation was localized to the Tbilisi region and did not indicate broad global impact.