Live

Network Performance Issues in Chicago datacenter (ORD)

0

Cloudflare reported degraded network performance in the Chicago datacenter (ORD). The affected components were Durable Objects, D1, R2, and the Chicago, United States (ORD) region. Cloudflare reports that the incident is resolved and that it lasted 39 minutes.

State

Resolved

Started

Lasted

39 min

Worst impact

Degraded

Timeline

4 updates
00:3200:4200:5201:0201:11
DegradedUpdate postedTimes in UTC

Investigating

12 min 32%

Monitoring

27 min 68%

Updates

Times in UTC

As posted by Cloudflare

Resolved

This incident has been resolved.

Monitoring

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

Investigating

We are continuing to investigate the issue.

Investigating

Cloudflare is investigating issues with network performance in Chicago datacenter, ORD. We are working to analyze and mitigate this problem. More updates to follow shortly.

Affected components

5
Durable ObjectsD1Chicago, United States - (ORD)R2North America - Chicago, United States - (ORD)

Cloudflare in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

129

Days with an incident

87

Median duration

1 h 31 min

This incident

57% shorter than the median

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

56 days
median 1 h 31 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.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