- Level
- confirmed
- Worst impact
- Degraded
- Components
- Network, Tokyo, Japan - (NRT)
- Regions
- apac, jp
- Down Index
- 27of 100
What to do
Check whether you use Cloudflare Network, Tokyo, Japan - (NRT) in apac, jp. 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 54m it lasted.
Anything that failed between 2026-11-04 13:39 UTC and 2026-11-04 15:33 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 4
- investigating
We are currently investigating a network latency issue in NRT
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been 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-975e474044
Is Cloudflare still down?
No, this incident was resolved 2026-11-04 15:33 UTC. For Cloudflare's live state, see https://down.guide/cloudflare.
How long did it last?
1h 54m, from 2026-11-04 13:39 UTC to 2026-11-04 15:33 UTC, by the times Cloudflare posted.
What was affected?
Cloudflare named Network, Tokyo, Japan - (NRT) in apac, jp.
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.