Rewindex

RewindexOutage eventsJul 14, 2025

Cloudflare outage, Jul 14, 2025

6 vendors posted 5 incidents between 22:00 and 23:00 UTC, against about 5 incidents from 3 vendors in the same hours on an ordinary week. 2 vendors named Cloudflare in 2 incidents (2 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.

    3. first vendor named Cloudflare 22:05
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 hour2 vendors, 2 blamed CloudflareCursor, Retell AI
Cloudflareown incident not archivedWithin an hour2 vendors, 2 blamed CloudflareCursor, Retell AI
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/>2 vendors, 2 blamed Cloudflare<br/>Cursor, Retell AI"]:::blames
  root --> h1

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

2 vendors

  • +0 min

    Blames Cloudflare

    Incident, no impact listed

    CursorDNS Connectivity Issues Impacting Background Agent

    …DNS Connectivity Issues Impacting Background Agent The upstream issue with Cloudflare DNS has been resolved.…

  • +15 min

    Blames Cloudflare

    Incident, no impact listed

    Retell AIPhone call not connecting

    …otential workarounds. Telephony provider confirmed that this is related to an outage with Cloudflare DNS, which they use in certain internal components. A change is being applied to mitigate. related…

Same window, did not name anyone

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

Show all 3

Detected automatically from 7 status pages opening incidents in the peak hour (normally at most 6). 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.