- 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 2026-03-09 18:02 UTC and 2026-03-09 18:02 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 investigated and fixed an issue that impacted users trying to view or modify Zero Trust Gateway Policies. During the impacted period, API users would have received 500 status code responses to GET requests to the /accounts/{account_id}/gateway/rules endpoint, whilst Zero Trust Dashboard users would have been unable to view or edit Zero Trust Gateway Policies in the "Firewall policies", "Egress policies" or "Resolver policies" pages would all have displayed the error "We ran into an error while fetching our data". This may have impacted customers on Mon 9th March, 2026 from 17:45 UTC to 18:02 UTC.
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-054e0344c5
Is Cloudflare still down?
No, this incident was resolved 2026-03-09 18:02 UTC. For Cloudflare's live state, see https://down.guide/cloudflare.
How long did it last?
0m, from 2026-03-09 18:02 UTC to 2026-03-09 18:02 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.