- Level
- confirmed
- Worst impact
- Degraded
- Components
- Stream, Pipelines, R2
- Regions
- us
- Down Index
- 26of 100
What to do
Check whether you use Cloudflare Stream, Pipelines, R2 in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 9h 15m it lasted.
Anything that failed between 2026-11-03 13:00 UTC and 2026-11-03 22:15 UTC may need a replay.Subscribe to Cloudflare's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=cloudflare works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Cloudflare 1
- resolved
Cloudflare has resolved an issue affecting R2 and downstream services in the Western North America region. Some customers may have seen elevated latency and errors between approximately 13:00 and 22:15 UTC on November 3, 2026. This may also have affected downstream services such as Stream and Pipelines.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-552af41eb7
Is Cloudflare still down?
No, this incident was resolved 2026-11-03 22:15 UTC. For Cloudflare's live state, see https://down.guide/cloudflare.
How long did it last?
9h 15m, from 2026-11-03 13:00 UTC to 2026-11-03 22:15 UTC, by the times Cloudflare posted.
What was affected?
Cloudflare named Stream, Pipelines, R2 in us.
What caused it?
Cloudflare hasn't published a root cause. If it does, it shows here.
Where does this come from?
Cloudflare's official status page, https://www.cloudflarestatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.