- Level
- confirmed
- Worst impact
- Degraded
- Components
- Access
- Down Index
- 18of 100
What to do
Check whether you use Cloudflare Access. 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 1h 36m it lasted.
Anything that failed between 2026-03-10 13:28 UTC and 2026-03-10 15:04 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
An interim solution has been identified. Users can open a new tab in Firefox, enter `about:config`, and locate the `dom.events.testing.asyncClipboard` setting, and set it to `true`.
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-f39ae4160c
Is Cloudflare still down?
No, this incident was resolved 2026-03-10 15:04 UTC. For Cloudflare's live state, see https://down.guide/cloudflare.
How long did it last?
1h 36m, from 2026-03-10 13:28 UTC to 2026-03-10 15:04 UTC, by the times Cloudflare posted.
What was affected?
Cloudflare named Access.
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.