- Level
- confirmed
- Worst impact
- Degraded
- Regions
- apac, us
What to do
Check whether you use Cloudflare in apac, 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 0m it lasted.
Anything that failed between 2026-08-23 02:00 UTC and 2026-08-23 02:00 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 23rd August 2026, 01:06 UTC - 01:54 UTC, some customers may have experienced elevated 5xx errors and timeouts for traffic between North American origins and our Singapore data centre. This issue is now resolved.
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-7aa8867853
Is Cloudflare still down?
No, this incident was resolved 2026-08-23 02:00 UTC. For Cloudflare's live state, see https://down.guide/cloudflare.
How long did it last?
0m, from 2026-08-23 02:00 UTC to 2026-08-23 02:00 UTC, by the times Cloudflare posted.
What was affected?
Cloudflare named in apac, 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.