CHYP.ai · ORBIT // Cloudy_Day Security Suite

OUTAGE DISSECTOR · CASE FILE · NetWeather event

Cloudflare: Network Performance Issues in Miami

Cloudflare resolved M4.8 Squall since Nov 19, 9:01 PM PT

Cloudflare reported “Cloudflare: Network Performance Issues in Miami” starting Nov 19, 9:01 PM PT.

  • 9h 27mDurationstart → resolved
  • 6Systems namedfrom the source
  • 1Places named1 on the map
  • 14Dependentscatalogued, inferred
  • 2/4Evidence kindsindependent families
  • 3Updatesofficial revisions

1Scrub the outage

full window
Severityofficial state Nov 19, 4 PMNov 19, 7 PMNov 19, 9 PMNov 20, 12 AMNov 20, 3 AMNov 20, 5 AM Official statusNov 19, 9:00 PM PT · Vendor incident opened: Network Performance Issues in Miami (minor)Nov 19, 9:02 PM PT · Cloudflare: Network Performance Issues in MiamiNov 19, 9:12 PM PT · Cloudflare: Network Performance Issues in MiamiNov 20, 6:28 AM PT · Cloudflare: Network Performance Issues in MiamiNetwork & routingNov 20, 12:43 AM PT · Cloudflare: 5 components partial outage · AFNov 19, 10:15 PM PT · Cloudflare: 4 components partial outage · SANov 20, 3:00 AM PT · Cloudflare: 3 components partial outage · NANov 19, 3:34 PM PT · Cloudflare: 2 components partial outage · EUNov 20, 6:28 AM PT · AS13335 (Cloudflare) BGP update churn -0.2σ vs 24hEarly signalsnothing in this windowNews & chatterNov 19, 5:58 PM PT · nginx2root: Five new nginx vulnerabilities, and how Cloudflare protects origins from the worst of t…Coincidence (KEV)nothing in this window ▼ startresolved ▼

Drag or press Play to replay what was public at each moment. Each dot links to its evidence. Lanes are kept separate on purpose.

What happened

Cloudflare reported “Cloudflare: Network Performance Issues in Miami” starting Nov 19, 9:01 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 (Miami (MIA)).

How it recovered

Resolved after 9h 27m.

2Blast radius

Cloudflare DNS (1.1.1.1) · Degraded / minor incident · unwell in the same window (coincidence, not causation)Cloudflare DNS …Cloudflare Zero Trust · Degraded / minor incident · unwell in the same window (coincidence, not causation)Cloudflare Zero…Canva · OperationalCanvaClerk · OperationalClerkDiscord · OperationalDiscordDocker Hub · OperationalDocker HubKinsta · OperationalKinstaNotion · OperationalNotionnpm · OperationalnpmOpenAI (ChatGPT & API) · OperationalOpenAI (ChatGPT…Shopify · OperationalShopifyVercel · OperationalVercelWebflow · OperationalWebflowOpenRouter · no official feed / staleOpenRouterCloudflare14 dependents

Center: Cloudflare. Inner ring: what it runs on. Outer ring: catalogued services that run on it, coloured by their official status right now. 2 are unwell in the same window: a lead, not proof of a cascade. Dependencies are inferred from public information.

3Blast map

India ×4 · Ahmedabad, India - (AMD); Kanpur, India - (KNU); Nagpur, India - (NAG); Patna, India - (PAT) · same provider, other region: Cloudflare: 18 components partial outage · ASChina ×4 · Qingdao, China - (TAO); Shenzhen, China - (SZX); Chongqing, China - (CKG); Xiangyang, China - (XFN) · same provider, other region: Cloudflare: 18 components partial outage · ASAsia · Hagatna, Guam - (GUM) · same provider, other region: Cloudflare: 18 components partial outage · ASPakistan · Islamabad, Pakistan - (ISB) · same provider, other region: Cloudflare: 18 components partial outage · ASMalaysia · Johor Bahru, Malaysia - (JHB) · same provider, other region: Cloudflare: 18 components partial outage · ASKolkata (CCU) · Kolkata, India - (CCU) · same provider, other region: Cloudflare: 18 components partial outage · ASAlgeria · Annaba, Algeria - (AAE) · same provider, other region: Cloudflare: 5 components partial outage · AFMozambique · Maputo, Mozambique - (MPM) · same provider, other region: Cloudflare: 5 components partial outage · AFCongo · Kinshasa, Congo - Kinshasa - (FIH) · same provider, other region: Cloudflare: 5 components partial outage · AFNamibia · Windhoek, Namibia - (WDH) · same provider, other region: Cloudflare: 5 components partial outage · AFMalawi · Lilongwe, Malawi - (LLW) · same provider, other region: Cloudflare: 5 components partial outage · AFBrazil ×2 · Joinville, Brazil - (JOI) (Latin Americ…; Palmas, Brazil - (PMW) (Latin America &… · same provider, other region: Cloudflare: 4 components partial outage · SAChile · Arica, Chile - (ARI) (Latin America & t… · same provider, other region: Cloudflare: 4 components partial outage · SASouth America · St. George's, Grenada - (GND) (Latin Am… · same provider, other region: Cloudflare: 4 components partial outage · SAUnited States of America ×2 · Albuquerque, United States - (ABQ); Norfolk, United States - (ORF) · same provider, other region: Cloudflare: 3 components partial outage · NANorth America · Santo Domingo, Dominican Republic - (SD… · same provider, other region: Cloudflare: 3 components partial outage · NABelarus · Minsk, Belarus - (MSQ) · same provider, other region: Cloudflare: 2 components partial outage · EURussia · Saint Petersburg, Russia - (LED) · same provider, other region: Cloudflare: 2 components partial outage · EUAustralia · Canberra, Australia - (CBR) · same provider, other region: Cloudflare: 2 components partial outage · OCOceania · Tahiti, French Polynesia - (PPT) · same provider, other region: Cloudflare: 2 components partial outage · OCMiami (MIA) · identified · Miami, United States - (MI…
  1. Miami (MIA)

Bright: this event. Dim: the same provider's other open events (8). Places come from names in the public text (cities, PoP codes, countries, regions). Approximate.

4Failure-mode fingerprint

RetriesControl planeConfig pushCascadeCapacity
  • Control-plane coupling“workers”, “event subscription”
  • Config propagation“changes”
  • Dependency cascade2 dependents also unwell
  • Capacity exhaustion“performance issues”
  • Retry amplificationno sign

Automated keyword read of the public updates. A hypothesis to test, never a root cause.

5Evidence matrix

Official statusOfficial status · Nov 19, 3:01 PM PT: 0 itemsOfficial status · Nov 19, 3:40 PM PT: 0 itemsOfficial status · Nov 19, 4:18 PM PT: 0 itemsOfficial status · Nov 19, 4:57 PM PT: 0 itemsOfficial status · Nov 19, 5:35 PM PT: 0 itemsOfficial status · Nov 19, 6:14 PM PT: 0 itemsOfficial status · Nov 19, 6:53 PM PT: 0 itemsOfficial status · Nov 19, 7:31 PM PT: 0 itemsOfficial status · Nov 19, 8:10 PM PT: 0 itemsOfficial status · Nov 19, 8:49 PM PT: 3 itemsOfficial status · Nov 19, 9:27 PM PT: 0 itemsOfficial status · Nov 19, 10:06 PM PT: 0 itemsOfficial status · Nov 19, 10:44 PM PT: 0 itemsOfficial status · Nov 19, 11:23 PM PT: 0 itemsOfficial status · Nov 20, 12:02 AM PT: 0 itemsOfficial status · Nov 20, 12:40 AM PT: 0 itemsOfficial status · Nov 20, 1:19 AM PT: 0 itemsOfficial status · Nov 20, 1:58 AM PT: 0 itemsOfficial status · Nov 20, 2:36 AM PT: 0 itemsOfficial status · Nov 20, 3:15 AM PT: 0 itemsOfficial status · Nov 20, 3:54 AM PT: 0 itemsOfficial status · Nov 20, 4:32 AM PT: 0 itemsOfficial status · Nov 20, 5:11 AM PT: 0 itemsOfficial status · Nov 20, 5:49 AM PT: 0 itemsNetwork & routingNetwork & routing · Nov 19, 3:01 PM PT: 1 itemNetwork & routing · Nov 19, 3:40 PM PT: 0 itemsNetwork & routing · Nov 19, 4:18 PM PT: 0 itemsNetwork & routing · Nov 19, 4:57 PM PT: 0 itemsNetwork & routing · Nov 19, 5:35 PM PT: 0 itemsNetwork & routing · Nov 19, 6:14 PM PT: 0 itemsNetwork & routing · Nov 19, 6:53 PM PT: 0 itemsNetwork & routing · Nov 19, 7:31 PM PT: 0 itemsNetwork & routing · Nov 19, 8:10 PM PT: 0 itemsNetwork & routing · Nov 19, 8:49 PM PT: 0 itemsNetwork & routing · Nov 19, 9:27 PM PT: 0 itemsNetwork & routing · Nov 19, 10:06 PM PT: 1 itemNetwork & routing · Nov 19, 10:44 PM PT: 0 itemsNetwork & routing · Nov 19, 11:23 PM PT: 0 itemsNetwork & routing · Nov 20, 12:02 AM PT: 0 itemsNetwork & routing · Nov 20, 12:40 AM PT: 1 itemNetwork & routing · Nov 20, 1:19 AM PT: 0 itemsNetwork & routing · Nov 20, 1:58 AM PT: 0 itemsNetwork & routing · Nov 20, 2:36 AM PT: 1 itemNetwork & routing · Nov 20, 3:15 AM PT: 0 itemsNetwork & routing · Nov 20, 3:54 AM PT: 0 itemsNetwork & routing · Nov 20, 4:32 AM PT: 0 itemsNetwork & routing · Nov 20, 5:11 AM PT: 0 itemsNetwork & routing · Nov 20, 5:49 AM PT: 0 itemsEarly signalsEarly signals · Nov 19, 3:01 PM PT: 0 itemsEarly signals · Nov 19, 3:40 PM PT: 0 itemsEarly signals · Nov 19, 4:18 PM PT: 0 itemsEarly signals · Nov 19, 4:57 PM PT: 0 itemsEarly signals · Nov 19, 5:35 PM PT: 0 itemsEarly signals · Nov 19, 6:14 PM PT: 0 itemsEarly signals · Nov 19, 6:53 PM PT: 0 itemsEarly signals · Nov 19, 7:31 PM PT: 0 itemsEarly signals · Nov 19, 8:10 PM PT: 0 itemsEarly signals · Nov 19, 8:49 PM PT: 0 itemsEarly signals · Nov 19, 9:27 PM PT: 0 itemsEarly signals · Nov 19, 10:06 PM PT: 0 itemsEarly signals · Nov 19, 10:44 PM PT: 0 itemsEarly signals · Nov 19, 11:23 PM PT: 0 itemsEarly signals · Nov 20, 12:02 AM PT: 0 itemsEarly signals · Nov 20, 12:40 AM PT: 0 itemsEarly signals · Nov 20, 1:19 AM PT: 0 itemsEarly signals · Nov 20, 1:58 AM PT: 0 itemsEarly signals · Nov 20, 2:36 AM PT: 0 itemsEarly signals · Nov 20, 3:15 AM PT: 0 itemsEarly signals · Nov 20, 3:54 AM PT: 0 itemsEarly signals · Nov 20, 4:32 AM PT: 0 itemsEarly signals · Nov 20, 5:11 AM PT: 0 itemsEarly signals · Nov 20, 5:49 AM PT: 0 itemsNews & chatterNews & chatter · Nov 19, 3:01 PM PT: 0 itemsNews & chatter · Nov 19, 3:40 PM PT: 0 itemsNews & chatter · Nov 19, 4:18 PM PT: 0 itemsNews & chatter · Nov 19, 4:57 PM PT: 0 itemsNews & chatter · Nov 19, 5:35 PM PT: 1 itemNews & chatter · Nov 19, 6:14 PM PT: 0 itemsNews & chatter · Nov 19, 6:53 PM PT: 0 itemsNews & chatter · Nov 19, 7:31 PM PT: 0 itemsNews & chatter · Nov 19, 8:10 PM PT: 0 itemsNews & chatter · Nov 19, 8:49 PM PT: 0 itemsNews & chatter · Nov 19, 9:27 PM PT: 0 itemsNews & chatter · Nov 19, 10:06 PM PT: 0 itemsNews & chatter · Nov 19, 10:44 PM PT: 0 itemsNews & chatter · Nov 19, 11:23 PM PT: 0 itemsNews & chatter · Nov 20, 12:02 AM PT: 0 itemsNews & chatter · Nov 20, 12:40 AM PT: 0 itemsNews & chatter · Nov 20, 1:19 AM PT: 0 itemsNews & chatter · Nov 20, 1:58 AM PT: 0 itemsNews & chatter · Nov 20, 2:36 AM PT: 0 itemsNews & chatter · Nov 20, 3:15 AM PT: 0 itemsNews & chatter · Nov 20, 3:54 AM PT: 0 itemsNews & chatter · Nov 20, 4:32 AM PT: 0 itemsNews & chatter · Nov 20, 5:11 AM PT: 0 itemsNews & chatter · Nov 20, 5:49 AM PT: 0 itemsCoincidence (KEV)Coincidence (KEV) · Nov 19, 3:01 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 3:40 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 4:18 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 4:57 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 5:35 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 6:14 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 6:53 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 7:31 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 8:10 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 8:49 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 9:27 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 10:06 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 10:44 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 11:23 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 12:02 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 12:40 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 1:19 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 1:58 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 2:36 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 3:15 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 3:54 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 4:32 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 5:11 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 5:49 AM PT: 0 itemsNov 19, 3:01 PM PTNov 20, 6:28 AM PT

Correlation is not causation

Five independent lanes across the window. Brighter = stronger item. Items landing in the same column are coincidence unless the provider says otherwise.

6Four clocks

Source says it beganNov 19, 9:01 PM PTORBIT first saw itNov 19, 9:02 PM PTLatest source updateNov 19, 9:10 PM PTLast checkedNov 22, 4:12 AM PT

Detection gap: 1m between the source's start time and ORBIT's first sighting.

Public status always trails reality. These are the times each public record states, in PT.

7Historical twins

Nearest matches in the Control-Plane Meltdown Index (1.0.0, vendor-sourced, tracked since 2024 with earlier landmark cases). Similarity = provider + failure modes + scope.

Cloudy_Day take

  • 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 16 of 19 indexed meltdowns (median 3h 48m). By impact it isn't close. That's why ORBIT ranks by magnitude, not minutes.

Automated take: rules written by Cloudy_Day, applied to public data. Not a human verdict on this incident, not a root-cause finding, not affiliated with Cloudflare.

8Dissection capsule

Share card for this dissection

Everything above as one shareable, citable capsule with a content hash.

JSON capsuleMarkdownShare card (SVG)

Open Cloudflare in the War Room →NetWeather evidence page →Status page →

Embed this card
<a href="https://www.chyp.ai/dissect/event-nw-457e9bab08a404e7/"><img src="https://www.chyp.ai/dissect/event-nw-457e9bab08a404e7/card.svg" alt="Cloudflare: Network Performance Issues in Miami · ORBIT Outage Dissector" width="600"></a>

Sources & 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.
  • NetWeather is independent research, not an official status source. Confirm with the provider.
  • Correlation is not causation. Lanes are kept apart so overlap never reads as cause.
  • ORBIT is passive: it never contacts the provider or probes its systems. Independent researcher, not affiliated.