Live

Network connectivity issues affecting services in North America

This incident has been resolved.

The latest update from Cloudflare.

State

Resolved

Started

9 d ago

2026-10-23 15:47 UTC

Lasted

2 h 56 min

until 2026-10-23 18:43 UTC

Worst impact

Partial outage

Timeline

8 updates
15:4716:3117:1517:5918:43
Partial outageUpdate postedTimes in UTC

Investigating

21 min 12%

Identified

1 h 39 min 56%

Monitoring

57 min 32%

Updates

Times in UTC

As posted by Cloudflare

Resolved2026-10-23 18:43 UTC

This incident has been resolved.

Monitoring2026-10-23 18:18 UTC

Our network team has rerouted traffic around the impacted paths and we are no longer seeing packet drops. Our connectivity provider reports that its service has been restored, but some links are still being brought back, so we are keeping our traffic management changes in place.

Identified2026-10-23 17:33 UTC

The team is continuing to perform traffic engineering actions to route around impacted paths. The team will continue performing traffic engineering actions until all packet drops are mitigated.

Identified2026-10-23 17:03 UTC

The infrastructure provider has experienced a recurrence of the failure. Cloudflare is continuing to apply traffic management actions to further remediate the issue.

Identified2026-10-23 16:59 UTC

We are continuing to work on a fix for the issue.

Monitoring2026-10-23 16:27 UTC

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

Identified2026-10-23 16:07 UTC

We have identified a connectivity provider outage causing network congestion and degraded performance for some customers in North America. Affected customers may experience increased latency, packet loss, and intermittent errors across multiple services. Our network team is rerouting traffic away from affected paths, and we are working directly with our provider on restoration.

Investigating2026-10-23 15:47 UTC

We are investigating degraded network performance affecting some traffic between our Ashburn and Atlanta data centers. Some customers may see increased latency, packet loss, or intermittent errors on Workers and other services in the Eastern US. Our network team is actively working on mitigation.

Affected components

1
Network

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

2.4× 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

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