2025: The year of the global cloud outage

Learn more
magnifying glass icon
magnifying glass icon
  • Can't find service? Request service
    magnifying glass icon
    Sign Up
    Cloudflare icon
    Cloudflare icon

    Cloudflare Outage History

    Minor Cloudflare outage

    There were 236 Cloudflare outages since May 2025 which are summarized below, including incident details, duration, and resolution information.

    Cloudflare not working for you?

    Cloudflare not working for you?

    minor icon Minor

    : Cloudflare ORD maintenance completed; service restored

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (3 hours and 5 minutes)

    Cloudflare carried out scheduled maintenance in the ORD (Chicago) region beginning at and concluding at , lasting about 3 hours and 5 minutes. The status page described the window as in progress and noted that updates would be provided as necessary. Two official status updates were published during the incident: one noting the maintenance in progress, and a follow-up confirming the service had returned to normal.

    minor icon Minor

    : Cloudflare Taipei maintenance causes regional degradation

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (10 hours and 30 minutes)

    Cloudflare carried out scheduled maintenance in the Taipei region (TPE). During the maintenance window lasting about 10 hours and 35 minutes, users in Taipei experienced degraded service and intermittent connectivity. The maintenance began at and concluded at . The Taipei region was restored and the status returned to normal by .

    minor icon Minor

    : Cloudflare DNS API and Pages issues affect users worldwide

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (1 day, 4 hours and 50 minutes)

    The incident began on with Cloudflare reporting issues in the DNS Records API. API requests to update or create DNS records could fail or display errors, though Cloudflare’s CDN edge and security features remained largely available. Over the next 24 hours, users also reported intermittent network performance in South Korea and problems with Automatic Platform Optimization (APO) that could yield unexpected 500 errors. Cloudflare Pages deployments were affected as well, with function deployments potentially failing or being delayed. Athens and Seattle maintenance events were listed during the period as fixes were implemented. The outage persisted until , lasting about 28 hours and 50 minutes. The provider issued multiple status updates throughout the incident to identify issues and communicate fixes.

    minor icon Minor

    : Cloudflare Analytics delays affect subset of customers

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (8 hours and 25 minutes)

    Cloudflare experienced delays in Network Analytics affecting a subset of Cloudflare Sites and Services / Analytics users, causing analytics data and reporting to lag for several hours. The status page indicated an investigation started around and the affected component moved to a degraded state at . The incident lasted about 8 hours and 25 minutes and was resolved by when the Analytics service returned to normal. The provider issued 2 official updates during the incident.

    minor icon Minor

    : Cloudflare ICN region network performance issues

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (1 hour and 20 minutes)

    Cloudflare reported degraded network performance in the South Korea region (ICN). The incident began on and was resolved by , lasting about 1 hour 20 minutes. Cloudflare issued two official updates during the event, first noting investigation of the ICN network performance and later confirming a return to normal operation. The impact appears localized to the ICN region, with other regions unaffected according to the status page.

    major icon Major

    : Cloudflare Gateway outage briefly disrupts Zero Trust access

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (2 hours and 35 minutes)

    The incident began with warnings on the Cloudflare Challenge Platform at after users reported issues passing challenge pages, resulting in 500 errors and degraded authentication flows for affected users. The disruption impacted Cloudflare Sites and Services / Challenge Platform and hindered access to challenged resources.

    At , Cloudflare identified a separate issue with Zero Trust Gateway, and a fix was being implemented as the gateway went down. The outage lasted about 20 minutes and the Gateway was restored by . The incident involved two components and was addressed through three official updates from Cloudflare during the period.

    minor icon Minor

    : Cloudflare Miami data center maintenance completed

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (6 hours)

    Cloudflare conducted scheduled maintenance at its Miami data center (MIA). The maintenance window began at and the status moved to degraded at . Normal service was restored by . The incident was contained to the Miami data center and involved a temporary degradation in services during the window. Two status updates were published during the incident, documenting the maintenance progress and restoration.

    minor icon Minor

    : Cloudflare Nasiriyah maintenance caused brief degradation

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (6 hours)

    Cloudflare carried out scheduled maintenance in the Nasiriyah region (XNH), which caused a period of degraded performance for some users. The maintenance window ran from to and was reflected on Cloudflare's status page as a maintenance window listed under a 'warn' state. Users may have experienced slower responses or intermittent connectivity during this time.

    minor icon Minor

    : Cloudflare Tallahassee regional maintenance in progress

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (5 hours)

    Cloudflare carried out scheduled maintenance in the Tallahassee region (TLH) on 2025-08-07. The status page indicated the window began at and soon after the incident entered a warn state during the maintenance window. The work was regional in scope and described as in progress with updates to follow.

    The TLH region returned to normal by , with Cloudflare posting two official updates during the incident to communicate progress and the conclusion of the maintenance window. The impact was limited to the Tallahassee region and did not constitute a global outage.

    minor icon Minor

    : Cloudflare Seattle maintenance causes brief degraded performance

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (5 minutes)

    During a scheduled maintenance window in the Seattle region (SEA), Cloudflare experienced a brief degraded performance. The maintenance began at , and a warning was raised at , with service returning to normal by . The Seattle data center was affected, and Cloudflare posted 2 official status updates during the incident.

    Cloudflare icon

    Looking for more Cloudflare outage stats?

    Get real-time insights and historical data on Cloudflare outages.

    Looking to track Cloudflare downtime and outages?

    • Receive real-time status updates
    • Show current status on private or public status page
    • Be the first to know if service is down
    • Keep your team informed
    • Monitor alongside other services and websites
    Start monitoring for free