outages.live
Live
CloudflareIncident ·

Elevated number of errors in Bogotá

ResolvedOfficial update
0

Between 01:30-03:00 UTC customers reaching Bogotá, CO may have experienced an elevated latency and a number of 4xx errors.

The latest update from Cloudflare.

State

Resolved

Started

Lasted

1 h 30 min

Worst impact

Degraded

Timeline

1 update
01:3001:5202:1502:3703:00
NoticeUpdate postedTimes in UTC

Resolved

1 h 30 min 100%

Updates

Times in UTC

As posted by Cloudflare

Resolved

Between 01:30-03:00 UTC customers reaching Bogotá, CO may have experienced an elevated latency and a number of 4xx errors.

Affected components

2
Bogotá, Colombia - (BOG)Latin America & the Caribbean - Bogotá, Colombia - (BOG)

Cloudflare in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

100

Days with an incident

80

Median duration

1 h 30 min

This incident

About the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

56 days
median 1 h 30 min
90 days agoToday

Other Cloudflare incidents

All incidents

Cloudflare·Elevated error rates on Durable Objects in West North America

There were elevated error rates for WNAM based buckets from 19:41Z to 20:03Z UTC

Resolved

Cloudflare·Increased errors for R2 and Tiered Cache

Cloudflare reported increased errors for R2 and Tiered Cache in Chicago (ORD) and Newark (EWR), with lower error rates in other locations. Cloudflare reported the incident as resolved after 75 minutes, from 05:30 UTC to 06:45 UTC.

Resolved

Cloudflare·Issues with 1.1.1.1 public resolver in Canada

The 1.1.1.1 public resolver does not work for some users in Canada. The Recursive DNS component is affected. Cloudflare reports that the incident is resolved. The outage lasted about 68 minutes.

Resolved

Cloudflare·Cloudflare is seeing an issue with Workers API availability

Cloudflare reported an issue with the Workers API. Customers saw more 5xx errors when they deployed Workers or used other API actions. The incident is resolved and lasted 22 hours and 6 minutes.

Resolved

Cloudflare·Cloudflare is currently having an issue with the r8.im registry used for Replicate model publishing and builds is currently restricted

Cloudflare reports a problem with the r8.im registry. This problem restricts Replicate model publishing and builds. The incident is resolved. It lasted about 10 hours.

Resolved

Follow Cloudflare

Your coding agent knows when Cloudflare is down, and tells you when a failure is theirs, not yours. You can also get Cloudflare incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "cloudflare" and tell me if Cloudflare has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=cloudflare
Slack
/feed subscribe https://outages.live/feed.xml?providers=cloudflare

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane