- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Cloudflare. 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 0m it lasted.
Anything that failed between 2025-10-22 05:45 UTC and 2025-10-22 05:45 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
Between 05:45am and 06:25am UTC, Cloudflare has identified and mitigated an issue with our API which potentially impacted multiple customers: Performing bulk requests to our Custom Hostnames API endpoint might have returned unexpected timeouts. This did not affect the serving of cached files via the Cloudflare CDN or other security features at the Cloudflare Edge.
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-1792f33fc0
Is Cloudflare still down?
No, this incident was resolved 2025-10-22 05:45 UTC. For Cloudflare's live state, see https://down.guide/cloudflare.
How long did it last?
0m, from 2025-10-22 05:45 UTC to 2025-10-22 05:45 UTC, by the times Cloudflare posted.
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.