Rewindex

RewindexOutage eventsDec 5, 2025

Cloudflare outage, Dec 5, 2025

46 vendors posted 45 incidents between 08:00 and 17:00 UTC, against about 21 incidents from 13 vendors in the same hours on an ordinary week. 21 vendors named Cloudflare in 21 incidents (21 of them blamed it). Vendors reported a Cloudflare outage; Cloudflare’s own incident for this date is not in the archive.

Observed, not verified. A line means a vendor’s incident named another vendor, or started in the same window. It is not a proven cause.

Times are UTC; lags are from when the first vendor named Cloudflare.

    19. first vendor named Cloudflare 08:47
Named CloudflareNamed another vendorDid not name anyoneEach column is 30 minutes

How it spread

Vendors that named Cloudflare, grouped by when they posted, and vendors that blamed one of the vendors Cloudflare took down. Solid lines: the vendor named the other. Dashed: same window, not named.

Swipe sideways to see the whole diagram.

Cloudflareown incident not archivedWithin an hour18 vendors, 18 blamed CloudflareUnbounce, Expo, GitLab, Rootly +141 to 4 hours later1 vendor, 1 blamed CloudflareKlaviyoLater2 vendors, 2 blamed CloudflareBitrise, Sigma Computing
Cloudflareown incident not archivedWithin an hour18 vendors, 18 blamedCloudflareUnbounce, Expo, GitLab, Rootly+141 to 4 hours later1 vendor, 1 blamed CloudflareKlaviyoLater2 vendors, 2 blamed CloudflareBitrise, Sigma Computing
Rendered on the server with pele from the Mermaid source below. Each box lists the first few vendors; every vendor is listed further down.
Mermaid source
flowchart LR
  root["Cloudflare<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>18 vendors, 18 blamed Cloudflare<br/>Unbounce, Expo, GitLab, Rootly +14"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>1 vendor, 1 blamed Cloudflare<br/>Klaviyo"]:::blames
  root --> h4
  later["Later<br/>2 vendors, 2 blamed Cloudflare<br/>Bitrise, Sigma Computing"]:::blames
  root --> later

Vendors that named Cloudflare

In their own words. “Blames” means a causal phrase sits next to the name (“due to”, “upstream provider”…).

Within an hour

18 vendors

  • +0 min

    Blames Cloudflare

    Major incident

    UnbounceLive Pages Not Loading

    …Live Pages Not Loading On December 5, 2025, between 08:47 and 09:12 UTC, Cloudflare experienced an outage that affected all Unbounce pages. During this period, all live pages were unavailable, and no…

  • +13 min

    Blames Cloudflare

    Incident, no impact listed

    ExpoDisruption due to an upstream provider outage

    …bout 10 minutes and manifested in expo.dev returning a 500 when accessed. This was due to Cloudflare Service Issues which have since been resolved. See https://www.cloudflarestatus.com/ for more detai…

  • +14 min

    Blames Cloudflare

    Critical incident

    GitLabGitLab.com is down due to Cloudflare outage

    …GitLab.com is down due to Cloudflare outage GitLab.com functionality has returned to normal after Cloudflare applied a fix at 09:12 UTC. For more details, see https://gitlab.com/gitlab-com/gl-infra/pr…

  • +15 min

    Blames Cloudflare

    Minor incident

    RootlyRootly.com Marketing Site Loading Issues

    …m31y6sw9q Our Rootly.com homepage are seeing 500 errors due to upstream service provider (Cloudflare) issues. No impact to On-Call, Web, Slack, or any other part of our application. The issues have be…

  • +16 min

    Blames Cloudflare

    Major incident

    PrismaPrisma Console is experiencing a partial outage

    …experiencing a partial outage This incident has been resolved. A fix has been deployed by Cloudflare and our all services appear to have come back online. We're continuing to monitor. An upstream infr…

  • +17 min

    Blames Cloudflare

    Incident, no impact listed

    CursorService Degradation due to Cloudflare Outage

    …Service Degradation due to Cloudflare Outage This incident has been resolved.…

  • +18 min

    Blames Cloudflare

    Major incident

    OptimizelyCloudflare experiences global Dashboard and Cloudflare API service issues affecting Optimizely services

    …Cloudflare experiences global Dashboard and Cloudflare API service issues affecting Optimizely services Optimizely’s monitoring confirm continuous service health since 09:12 (UTC). Incident Resolved.…

  • +22 min

    Blames Cloudflare

    Critical incident

    CanvaCanva is down due to Cloudflare outage

    …Canva is down due to Cloudflare outage Canva services have fully recovered following the Cloudflare outage. All systems are now operational. Canva is down due to Cloudflare outage Canva services have…

  • +23 min

    Blames Cloudflare

    Incident, no impact listed

    HubSpotHubSpot is currently unavailable for all customers.

    …customers in all regions experienced issues with all impaired tools. This was caused by a Cloudflare outage. As of 05:20 PM (UTC +08:00), our all impaired tools are working properly and the incident h…

  • +24 min

    Blames Cloudflare

    Critical incident

    DrataIssues loading Drata sites due to upstream provider outage

    …Issues loading Drata sites due to upstream provider outage Cloudflare has implemented a fix. All Drata sites are working as expected. Cloudflare has implemented a fix. All Drata sites are working as e…

  • +24 min

    Blames Cloudflare

    Incident, no impact listed

    Monday.comConnectivity Issues across accounts and devices

    …:** This incident was caused by a major outage at our third-party cloud service provider, Cloudflare. This outage led to widespread disruptions across many platforms, including [monday.com](http://mon…

  • +28 min

    Blames Cloudflare

    Major incident

    CoralogixCloudflare is experiencing an incident that is affecting Coralogix

    …Cloudflare is experiencing an incident that is affecting Coralogix This incident has been resolved.…

  • +30 min

    Blames Cloudflare

    Critical incident

    LatticeIssue with upstream provider

    …Issue with upstream provider Cloudflare is reporting that a fix has been implemented and the issue has been resolved, and we're seeing the Lattice application load successfully. Our Engineering Team w…

  • +30 min

    Blames Cloudflare

    Incident, no impact listed

    Sprout SocialCloudfare issues - degraded performance

    …en restored and are now fully operational. Thank you for your patience and understanding. Cloudflare is currently experiencing issues that are affecting Sprout’s access for some customers. We are watc…

  • +30 min

    Blames Cloudflare

    Minor incident

    ChargebeeCloudflare Service Impact

    …Cloudflare Service Impact This incident has been resolved. This incident has been resolved. We are currently experiencing disruptions to our support ticketing and chat systems. Certain integrations an…

  • +31 min

    Blames Cloudflare

    Major incident

    MakeMake services currently not accessible

    …ccessible again. This correlates with a status update shared by our third-party provider, Cloudflare, indicating that a fix has been implemented on their side. We are closely monitoring the system. So…

  • +38 min

    Blames Cloudflare

    Incident, no impact listed

    Grafana CloudHosted Grafana is currently being impacted as a result of the Cloudflare outage

    …Hosted Grafana is currently being impacted as a result of the Cloudflare outage This incident has been resolved.…

  • +43 min

    Blames Cloudflare

    Minor incident

    LiveKitCloud Dashboard Outage Due to Cloudflare Outage

    …Cloud Dashboard Outage Due to Cloudflare Outage User traffic was not impacted, but our customer dashboard was not operational because of a major Cloudflare outage. It lasted roughly from 08:45 - 09:15…

1 to 4 hours later

1 vendor

  • +1 h 55 min

    Blames Cloudflare

    Incident, no impact listed

    KlaviyoCloudflare incident disrupting Klaviyo

    …Cloudflare incident disrupting Klaviyo Between 3:48am (US Eastern) and 4:10am (US Eastern) Cloudflare experienced an outage which affected Klaviyo. During this time, users were unable to access Klaviy…

Later

2 vendors

  • +6 h 14 min

    Blames Cloudflare

    Incident, no impact listed

    Bitrisewww.bitrise.io down

    …itrise.io down We observed high error rates affecting our static site (bitrise.io) due to Cloudflare’s incident between 8:56 - 9:12 UTC app.bitrise.io was unaffected We observed high error rates affec…

  • +7 h 21 min

    Blames Cloudflare

    Incident, no impact listed

    Sigma ComputingSigma Service Disruption Due to Cloudflare Incident

    …Sigma Service Disruption Due to Cloudflare Incident At 08:56 UTC Cloudflare's scheduled maintenance to their Web Application Firewalls failed and an incident was declared. At 09:12 UTC a fix was deplo…

Same window, did not name anyone

24 incidents started during the event without naming Cloudflare or another vendor. Some are part of it, some are a normal day’s background (about 21 in these hours).

Show all 24

Detected automatically from 35 status pages opening incidents in the peak hour (normally at most 8). Mentions are matched by name in each incident’s title and updates, then classified as cause, location or integration; quoted text is the vendor’s. Vendors that share one status page are shown once.