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?

    major icon Major

    : Cloudflare global outage disrupts services across regions

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (3 days, 22 hours and 45 minutes)

    The Cloudflare global network suffered a widespread outage beginning on , affecting core services including the Cloudflare Dashboard, CDN/Cache, Workers, Firewall, Bot Management, and the Cloud Network Interconnect. Users worldwide reported pages failing to load, API errors, and login issues to the dashboard, indicating a broad impact across geographies. The incident drew a high volume of user reports, underscoring its widespread reach and effect on many sites and applications.

    minor icon Minor

    : Cloudflare London maintenance triggers brief degraded status

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

    Cloudflare reported a scheduled maintenance window in the London (LHR) region that briefly placed traffic under a degraded state. The window began around and the status moved to a warning at as maintenance proceeded.

    The issue was resolved when Cloudflare returned to normal at . The provider issued two official updates during the event, and impact appeared localized to the London region. User reports were limited, with at least one sample referencing connectivity issues from Sri Lanka during the window.

    major icon Major

    : Cloudflare outage disrupts Dashboard, API, and regional services

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (4 days)

    The outage began on with scheduled maintenance in Miami. Within hours, Ashburn, US network connectivity issues were reported (by ), followed by regional maintenance in Johannesburg later that day. The disruption escalated to widespread problems with Cloudflare Dashboard and Cloudflare API services, with API requests and dashboard interactions failing for customers. The incident expanded to other Cloudflare services including Spectrum TLS termination, and later issues affected Page Shield ingestion, WARP and Zero Trust, and multiple edge components. Cloudflare issued frequent status updates describing ongoing investigations and resolutions as the incident progressed. The disruption persisted until when status returned to up.

    minor icon Minor

    : Cloudflare-wide degraded performance across services

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (2 weeks, 3 hours and 55 minutes)

    Cloudflare experienced a broad degradation impacting a wide range of services including WARP and Zero Trust, Gateway, Email Routing, Pages, and more. Users reported login issues, slow or failed page loads, and delays in email forwarding and API responses. The incident began on and persisted for about two weeks, with ongoing regional maintenance and investigations as Cloudflare worked to restore normal operations.

    Cloudflare’s status updates reflect a multi-faceted remediation effort across many components. Over the course of the incident, the company issued numerous updates across Cloudflare's products, noting investigations, scheduled maintenance in regional facilities, temporary workarounds, and eventual restoration of affected services. Issues touched SSL provisioning, WARP and Gateway traffic, Email Routing, Pages deployments, Dashboard onboarding, Turnstile, Analytics, and Firewall features, among others.

    Impact was broad and reflected in a noticeable volume of user reports from many regions, indicating widespread disruption across Cloudflare's edge network. By , Cloudflare reported recovery as services returned to normal across monitored components, though some regional or product-specific issues may have persisted briefly during remediation.

    minor icon Minor

    : Cloudflare: Workers elevated errors and Bot Management issues

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

    The incident began on when Cloudflare moved to a warning after reports of elevated errors and some aborted requests in the Workers environment. An earlier window of degraded performance was observed between and UTC in impacted regions. Some customers experienced access problems and higher error rates during this period.

    Over the following days, Cloudflare issued five status updates describing Bot Management issues and regional maintenance in Sydney and Bangalore as mitigations progressed. The primary affected components were Cloudflare Sites and Services / Workers and Bot Management, with maintenance in SYD and BLR in progress at various times. The situation gradually improved, and services returned to normal after . A small number of user reports accompanied the incident, but there was no widespread, sustained global outage.

    major icon Major

    : Cloudflare outage hits Browser Rendering and Workers globally

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (6 days, 7 hours and 25 minutes)

    From , Cloudflare experienced browser rendering problems that hindered access to sites using Cloudflare rendering. The outage quickly escalated to affect multiple Cloudflare services, including Workers, Data Loss Prevention (DLP), API endpoints, Radar, and Durable Objects, with users reporting degraded performance and intermittent connectivity across the globe. The impact appeared worldwide, with issues reported in many regions over several days.

    Cloudflare issued a series of status updates, marking investigations and remediation efforts across many components. The incident included degraded load balancing health monitors, elevated latency for R2 in APAC/ENAM, dynamic changes in Browser Rendering and Radar, and later problems with Turnstile and bot management. The issues spread across many locations such as ORD, FRA, LHR, SIN and Basra, with several components moving between up, warn, and down states. On , Browser Rendering-related issues were resolved and affected services began returning to normal.

    Overall, the outage lasted from to , spanning roughly four days, and involved multiple Cloudflare products and edge regions. The incident underscores the breadth of Cloudflare's edge network and the interdependence of its services, with ongoing updates and fixes as engineers responded to the disruption.

    minor icon Minor

    : Cloudflare Frankfurt maintenance degrades service

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

    Cloudflare conducted scheduled maintenance in the Frankfurt region (FRA) beginning around . The status page noted the window as in progress maintenance and promised updates as needed. Some users reported connectivity issues during the window, including Australian users who observed service disruptions around to .

    minor icon Minor

    : Cloudflare Research Service briefly degraded; research.cloudflare.com impacted

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

    Cloudflare reported a brief degraded performance affecting the Cloudflare Research Service, including research.cloudflare.com and related cloudflareresearch.com products. The issue was first acknowledged as an investigation at , with the status updating to degraded at and the service returning to normal by . Cloudflare communicated the incident on the status page and issued two updates during the event, with the service restored shortly after the final update. The incident lasted roughly 5 minutes and affected specific research-related services on Cloudflare.

    minor icon Minor

    : Cloudflare Research Service Issues briefly degrade access

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

    Cloudflare reported issues affecting research.cloudflare.com and various Cloudflare Research products used by cloudflareresearch.com, leading to degraded access for affected users. The outage began on and was resolved by . The incident was short, lasting about 25 minutes, and the affected services appeared to be limited to Cloudflare Research offerings.

    minor icon Minor

    : Cloudflare experiences intermittent issues across services and regions

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (5 days, 8 hours and 50 minutes)

    Cloudflare faced a multi-day sequence of intermittent issues affecting multiple services. The incident began at with intermittent inability to update Cloudflare One application statuses and affected components including Gateway, Distributed Web Gateway, Web3 API, Workflows, Registrar, Browser Isolation, and Logs. Regional maintenance and issues were observed in Lisbon, Milan, Singapore, and Bangkok as the situation unfolded.

    Cloudflare documented the event through 12 official status updates from to , describing ongoing investigations, mitigations, and scheduled maintenance. The incident gradually moved toward recovery, with the Logs component restored by and many services returning to normal operation, though some users may have experienced degraded performance during the period. The impact appeared regional and service-specific rather than a single global outage, with reports from multiple regions over the course of the event.

    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