- Level
- confirmed
- Worst impact
- Degraded
- Components
- Network
- Regions
- apac
- Down Index
- 21of 100
What to do
Check whether you use Cloudflare Network in apac. 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 58m it lasted.
Anything that failed between 2026-10-16 01:13 UTC and 2026-10-16 02:11 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 01:13 AM and 02:11 AM UTC, network performance at our ICN-A colo in Seoul was impacted. Users downstream of KINX may have experienced increased latency (TTFB) and elevated Network Error Logging (NEL) metrics due to network path congestion. Performance metrics have since returned to normal baselines, and the issue is now fully 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-0b707cae67
Is Cloudflare still down?
No, this incident was resolved 2026-10-16 02:11 UTC. For Cloudflare's live state, see https://down.guide/cloudflare.
How long did it last?
58m, from 2026-10-16 01:13 UTC to 2026-10-16 02:11 UTC, by the times Cloudflare posted.
What was affected?
Cloudflare named Network in apac.
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.