# Network Performance Issues in Chicago datacenter (ORD) · ORBIT Outage Dissector

- Provider: Cloudflare · state: monitoring · duration: 5h 36m
- CHYP Magnitude: **M4.6 Squall** (severity 0.45, breadth 0.19, duration 0.63, reach 0.54, corroboration 0.75)
- Content SHA-256: 89eb1490e385477244fa7b431987b5af10b765a432f259eaedc3f11a72ec59f9

## Story

- **What happened:** Cloudflare reported “Network Performance Issues in Chicago datacenter (ORD)” starting Nov 21, 4:32 PM PT.
- **What broke:** Ahmedabad, India - (AMD), Albuquerque, United States - (ABQ), Arica, Chile - (ARI), Annaba, Algeria - (AAE) and 2 more.
- **Who was hit:** 14 catalogued services run on Cloudflare (inferred); 2 of them show an official problem in the same window (coincidence, not causation). Hit: 1 named location (Chicago (ORD)).
- **How it recovered:** Still open after 5h 36m.

## Failure-mode fingerprint (automated keyword read (hypothesis, not root cause))

- Control-plane coupling: 60% (“workers”, “event subscription”)
- Config propagation: 30% (“changes”)
- Dependency cascade: 30% (2 dependents also unwell)
- Capacity exhaustion: 30% (“performance issues”)

## Timeline (PT)

### Official status
- Nov 9, 5:53 PM PT · Also open: Changes to Cloudflare Workers are not producing Event Subscription events (https://www.chyp.ai/dissect/vi/cloudflare~0ocqieaifg7h/)
- Nov 19, 9:00 PM PT · Also open: Network Performance Issues in Miami (https://www.chyp.ai/dissect/vi/cloudflare~4lv21sf5fzhm/)
- Nov 20, 12:35 PM PT · Also open: Network Performance Issues in Washington, DC datacenter (IAD) (https://www.chyp.ai/dissect/vi/cloudflare~oz6to8yacrxe/)
- Nov 20, 12:51 PM PT · Also open: Cache Purging Delays in Milan (https://www.chyp.ai/dissect/vi/cloudflare~akjr7qn5o622/)
- Nov 21, 4:32 PM PT · Incident opened: Network Performance Issues in Chicago datacenter (ORD)

### Network & routing
- Nov 21, 9:55 PM PT · Cloudflare: 6 components partial outage · AF (https://www.chyp.ai/dissect/event-nw-d945d5b95da2dfeb/)
- Nov 21, 7:00 PM PT · AS13335 (Cloudflare) BGP update churn -0.9σ vs 24h (https://www.chyp.ai/incident/event-nw-7ef1b996828d7b7e)

### Early signals
- Nov 21, 4:32 PM PT · Cloudflare: "Network Performance Issues in Chicago datacenter (ORD)" (minor) (https://www.chyp.ai/signals/)

### News

### Coincidence (KEV)

## Historical twins

- 69% · Cloudflare 2025-11-18: Bot Management feature file doubled and crashed traffic-routing software (3h 10m to core traffic; 5h 46m to all systems) https://www.chyp.ai/dissect/m/cf-bot-feature-file-2025-11-18/
- 68% · Cloudflare 2020-07-17: Backbone router configuration error overwhelmed Atlanta (27m) https://www.chyp.ai/dissect/m/cf-backbone-2020-07-17/
- 56% · Cloudflare 2022-06-21: Network configuration change took 19 data centers offline (75m) https://www.chyp.ai/dissect/m/cf-mcp-bgp-2022-06-21/

## Cloudy_Day take (automated)

- The public wording leans control plane (APIs, dashboards, purges, provisioning). If that holds, it's the management layer on the critical path again. Worth asking.
- 2 services that sit on Cloudflare are unwell at the same time. That's a lead to check, not proof of a cascade.
- By the clock it has outlasted 10 of 19 indexed meltdowns (median 3h 48m). By impact it isn't close. That's why ORBIT ranks by magnitude, not minutes.
- 3 independent kinds of public evidence line up in the same window. Corroboration, still not causation.

## Sources

- Cloudflare official status page: https://www.cloudflarestatus.com/incidents/d2m4kw94ut4f

## Limits

- Provider-stated: this repeats what the vendor's public status page said. It is not an independent root-cause verification.
- Temporal overlap with other events is coincidence, not causation, unless a provider states a causal link.
- Correlation is not causation.

> Cite: ORBIT by Cloudy_Day, Outage Dissector, https://www.chyp.ai/dissect/vi/cloudflare~d2m4kw94ut4f/
> Automated data from ORBIT (Cloudy_Day Security Suite). Independent research, not affiliated with any government agency, vendor or data provider. Not an official status source.
