- Level
- confirmed
- Worst impact
- Degraded
- Cloudflare says
- 2026-11-15 01:30 to 03:00 UTC (1h 30m)
- Components
- Bogotá, Colombia - (BOG)
- Down Index
- 34of 100
Summary
Cloudflare says customers reaching Bogotá, CO may have experienced elevated latency and a number of 4xx errors between 01:30 and 03:00 UTC. The incident is resolved.
Written by anthropic/claude-haiku-5.5 from Cloudflare's own updates.
What to do
Check whether you use Cloudflare Bogotá, Colombia - (BOG). Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 30m it lasted.
Anything that failed between 2026-11-15 01:30 UTC and 2026-11-15 03: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 01:30-03:00 UTC customers reaching Bogotá, CO may have experienced an elevated latency and a number of 4xx errors.
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-a1e5ab81af
Is Cloudflare still down?
No, this incident was resolved 2026-11-15 03:00 UTC. For Cloudflare's live state, see https://down.guide/providers/cloudflare.
How long did it last?
1h 30m, from 2026-11-15 01:30 UTC to 2026-11-15 03:00 UTC, by the times Cloudflare posted.
What was affected?
Cloudflare named Bogotá, Colombia - (BOG).
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.