outages.live
Live
CloudflareIncident ·

Network Performance Issues in Chicago

ResolvedOfficial update
0

Between 04:55-05:12 UTC 7th Dec Cloudflare experienced issues with network performance in Chicago.

The latest update from Cloudflare.

State

Resolved

Started

Lasted

17 min

Worst impact

Degraded

Timeline

1 update
04:5504:5905:0305:0705:12
NoticeUpdate postedTimes in UTC

Resolved

17 min 100%

Updates

Times in UTC

As posted by Cloudflare

Resolved

Between 04:55-05:12 UTC 7th Dec Cloudflare experienced issues with network performance in Chicago.

Affected components

4
NetworkChicago, United States - (ORD)North America - Chicago, United States - (ORD)Network Services - Network

Cloudflare in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

77

Days with an incident

72

Median duration

1 h 33 min

This incident

82% 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 33 min
90 days agoToday

Other Cloudflare incidents

All incidents

Cloudflare·Spectrum Availability Issue in Phoenix

Cloudflare Spectrum is degraded in Phoenix. This issue can affect the availability of existing Spectrum applications. Cloudflare reports that the status is monitoring. The issue started 115 minutes ago and is not resolved.

Degraded

Cloudflare·Fedramp Customers have Delayed Purges

Cloudflare CDN Cache Purge has delayed purges for FedRAMP customers. The problem started 13 minutes ago. Cloudflare has identified the issue and continues to work on a fix. Stale content may be served until it expires. Other customers are not affected.

Degraded

Cloudflare·Partial System Outage

Cloudflare reported a partial system outage. The outage affected 20 locations, including Albuquerque, Bangalore, Sydney, Kyiv, and Nairobi. Cloudflare reports that the outage is resolved. It lasted 7 hours and 3 minutes.

Resolved · 1 affected

Cloudflare·Wrangler Deployments, Pages, and Workers Builds failures

Cloudflare Wrangler deployments, Pages, and Workers Builds failed. The incident affected Pages, Workers Builds, Wrangler, Developer Services - Pages, and Developer Services - Workers Builds. Cloudflare reported the incident as resolved after 21 minutes.

Resolved

Cloudflare·Network Performance Issues in Singapore

Cloudflare reported network performance issues in the Singapore (SIN) region. Cloudflare reports that the incident is resolved. The incident lasted about 1 hour and 50 minutes.

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