rewindex

RewindexOutage eventsOct 23, 2026

Cloudflare outage, Oct 23, 2026

4 linked vendors posted 4 incidents between and . 3 vendors named Cloudflare in 3 incidents (3 of them blamed it); 1 more are tied in by a known dependency. Cloudflare posted “Network connectivity issues affecting services in North America” at 15:47 UTC. 17 other vendors had incidents in the same window; nothing links them to Cloudflare (listed below).

Observed, not verified. A line means a vendor’s incident named another vendor, or a known dependency (declared by the vendor and named as a cause before). It is not a proven cause. Incidents that only share the time window are listed apart.

Times are in UTC; lags are from when Cloudflare posted ().

    23. Cloudflare posted
Named CloudflareNamed another vendor or depends on oneEach 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: a known dependency, not named in the incident.

Swipe sideways to see the whole diagram.

depends on CloudflareCloudflareposted 15:47 UTCWithin an hour3 vendors, 3 blamed CloudflareHubSpot, Ashby, PipedriveKnown dependency1 vendorWorkOS
depends on CloudflareCloudflareposted 15:47 UTCWithin an hour3 vendors, 3 blamed CloudflareHubSpot, Ashby, PipedriveKnown dependency1 vendorWorkOS
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/>posted 15:47 UTC"]:::root
  h1["Within an hour<br/>3 vendors, 3 blamed Cloudflare<br/>HubSpot, Ashby, Pipedrive"]:::blames
  root --> h1
  dr["Known dependency<br/>1 vendor<br/>WorkOS"]:::hop2
  root -.->|"depends on Cloudflare"| dr

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

3 vendors

  • +21 min

    Blames Cloudflare

    Incident, no impact listed

    HubSpotSome HubSpot tools may be unavailable for some users

    …time of the update. HubSpot is currently unavailable for users in North America due to a Cloudflare outage - https://www.cloudflarestatus.com/incidents/sufgcbe8rrwt We are working with Cloudflare to…

  • +23 min

    Blames Cloudflare

    Minor incident

    AshbySporadic reports of Ashby unavailable

    …. This appears related to a network connectivity issue reported by our upstream provider, Cloudflare. Access appears to be recovering, and we’re monitoring for further disruption. This incident has be…

  • +30 min

    Blames Cloudflare

    Minor incident

    PipedriveCloudflare service disruption affecting some US customers

    …Cloudflare service disruption affecting some US customers Cloudflare rerouted traffic around the affected network paths and has confirmed that its service is back to normal. Pipedrive should now be wo…

Linked by a known dependency

These incidents did not name Cloudflare, but the vendor declares the vendor shown as a dependency and has named it as a cause before.

Also happening at the same time (not linked)

17 incidents from 17 vendors started in this window without naming Cloudflare or a linked vendor, and with no known dependency on them. Listed for context only; they are not counted as part of the event (an ordinary week has about 42 incidents in these hours).

Show all 15

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