outages.live
Live
CloudflareIncident · 2026-10-29 10:31 UTC

Increased HTTP 429 Rate Limit Errors on Cloudflare Dashboard

ResolvedOfficial update

This incident has been resolved.

The latest update from Cloudflare.

State

Resolved

Started

3 d ago

2026-10-29 10:31 UTC

Lasted

1 h 39 min

until 2026-10-29 12:10 UTC

Worst impact

Degraded

Timeline

4 updates
10:3110:5611:2111:4612:10
DegradedUpdate postedTimes in UTC

Investigating

1 h 7 min 68%

Identified

21 min 21%

Monitoring

11 min 11%

Updates

Times in UTC

As posted by Cloudflare

Resolved2026-10-29 12:10 UTC

This incident has been resolved.

Monitoring2026-10-29 12:00 UTC

A fix has been implemented and we are monitoring the results.

Identified2026-10-29 11:39 UTC

The issue has been identified and a fix is being implemented.

Investigating2026-10-29 10:31 UTC

We are currently investigating reports of increased HTTP 429 (Rate Limit Exceeded) errors impacting users accessing dash.cloudflare.com. This issue primarily affects legitimate users connecting via shared egress networks (such as Cloudflare One default egress IPs or external corporate proxies). Our engineering team is actively investigating the root cause and adjusting rate-limiting thresholds to restore normal dashboard access.

Affected components

2
DashboardSupport Site

Cloudflare in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

51

Days with an incident

66

Median duration

1 h 15 min

This incident

1.3× the median

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

56 days
median 1 h 15 min
90 days agoToday

Other Cloudflare incidents

All incidents

Cloudflare·Partial System Outage

Cloudflare reports a partial outage that affects 20 locations, including Dallas, Frankfurt, Sydney, Nairobi, and Bangalore. Cloudflare is investigating the problem. The outage started at 21:45 UTC on 31 October 2026.

Partial outageupdated 4 min ago · 1 affected

Cloudflare·Cache purge delays in Qingdao Shandong, China

This incident has been resolved.

Resolvedresolved 24 h ago

Cloudflare·Increased Errors for Browser Run

This incident has been resolved.

Resolvedresolved 2 d ago

Cloudflare·R2 Elevated Latency in Eastern Europe

This incident has been resolved.

Resolvedresolved 2 d ago

Cloudflare·Increased Errors for Durable Objects and Downstream Services in Eastern North America (ENAM)

This incident has been resolved.

Resolvedresolved 3 d ago

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.cc/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.cc/feed.xml?providers=cloudflare
Slack
/feed subscribe https://outages.cc/feed.xml?providers=cloudflare

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane