CHYP.ai · ORBIT // Cloudy_Day Security Suite

OUTAGE DISSECTOR · CASE FILE · Vendor incident

Network Performance Issues in Miami

Cloudflare identified M4.5 Squall since Nov 19, 9:00 PM PT

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

  • 31h 37mDurationand counting
  • 6Systems namedfrom the source
  • 1Places named1 on the map
  • 14Dependentscatalogued, inferred
  • 2/4Evidence kindsindependent families
  • 4Updatesofficial revisions

1Scrub the outage

full window
Severityofficial state Nov 19, 7 PMNov 20, 1 AMNov 20, 8 AMNov 20, 2 PMNov 20, 8 PMNov 21, 3 AM Official statusNov 19, 9:00 PM PT · Incident opened: Network Performance Issues in MiamiNov 20, 12:35 PM PT · Also open: Network Performance Issues in Washington, DC datacenter (IAD)Nov 20, 12:51 PM PT · Also open: Cache Purging Delays in MilanNetwork & routingNov 21, 3:14 AM PT · Cloudflare: 19 components partial outage · ASNov 21, 4:28 AM PT · Cloudflare: 7 components partial outage · AFNov 19, 10:15 PM PT · Cloudflare: 4 components partial outage · SANov 21, 4:28 AM PT · Cloudflare: 3 components partial outage · EUNov 20, 3:00 AM PT · Cloudflare: 3 components partial outage · NANov 21, 1:00 AM PT · AS13335 (Cloudflare) BGP update churn -0.7σ 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…Nov 20, 12:00 PM PT · How Cloudflare WAF helps protect against phpAfterShell and other critical PHP flawsNov 20, 12:24 PM PT · How Cloudflare WAF protects against ruby2shell (CVE-2026-132825)Coincidence (KEV)nothing in this window ▼ startnow ▼

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 “Network Performance Issues in Miami” starting Nov 19, 9:00 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

Still open after 31h 37m.

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

Miami (MIA) · Network Performance Issues in Miami
  1. Miami (MIA)

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:00 PM PT: 0 itemsOfficial status · Nov 19, 4:34 PM PT: 0 itemsOfficial status · Nov 19, 6:08 PM PT: 0 itemsOfficial status · Nov 19, 7:43 PM PT: 1 itemOfficial status · Nov 19, 9:17 PM PT: 0 itemsOfficial status · Nov 19, 10:51 PM PT: 0 itemsOfficial status · Nov 20, 12:25 AM PT: 0 itemsOfficial status · Nov 20, 1:59 AM PT: 0 itemsOfficial status · Nov 20, 3:33 AM PT: 0 itemsOfficial status · Nov 20, 5:07 AM PT: 0 itemsOfficial status · Nov 20, 6:41 AM PT: 0 itemsOfficial status · Nov 20, 8:15 AM PT: 0 itemsOfficial status · Nov 20, 9:49 AM PT: 0 itemsOfficial status · Nov 20, 11:23 AM PT: 2 itemsOfficial status · Nov 20, 12:57 PM PT: 0 itemsOfficial status · Nov 20, 2:31 PM PT: 0 itemsOfficial status · Nov 20, 4:05 PM PT: 0 itemsOfficial status · Nov 20, 5:39 PM PT: 0 itemsOfficial status · Nov 20, 7:13 PM PT: 0 itemsOfficial status · Nov 20, 8:47 PM PT: 0 itemsOfficial status · Nov 20, 10:21 PM PT: 0 itemsOfficial status · Nov 20, 11:55 PM PT: 0 itemsOfficial status · Nov 21, 1:29 AM PT: 0 itemsOfficial status · Nov 21, 3:03 AM PT: 0 itemsNetwork & routingNetwork & routing · Nov 19, 3:00 PM PT: 0 itemsNetwork & routing · Nov 19, 4:34 PM PT: 0 itemsNetwork & routing · Nov 19, 6:08 PM PT: 0 itemsNetwork & routing · Nov 19, 7:43 PM PT: 0 itemsNetwork & routing · Nov 19, 9:17 PM PT: 1 itemNetwork & routing · Nov 19, 10:51 PM PT: 0 itemsNetwork & routing · Nov 20, 12:25 AM PT: 0 itemsNetwork & routing · Nov 20, 1:59 AM PT: 1 itemNetwork & routing · Nov 20, 3:33 AM PT: 0 itemsNetwork & routing · Nov 20, 5:07 AM PT: 0 itemsNetwork & routing · Nov 20, 6:41 AM PT: 0 itemsNetwork & routing · Nov 20, 8:15 AM PT: 0 itemsNetwork & routing · Nov 20, 9:49 AM PT: 0 itemsNetwork & routing · Nov 20, 11:23 AM PT: 0 itemsNetwork & routing · Nov 20, 12:57 PM PT: 0 itemsNetwork & routing · Nov 20, 2:31 PM PT: 0 itemsNetwork & routing · Nov 20, 4:05 PM PT: 0 itemsNetwork & routing · Nov 20, 5:39 PM PT: 0 itemsNetwork & routing · Nov 20, 7:13 PM PT: 0 itemsNetwork & routing · Nov 20, 8:47 PM PT: 0 itemsNetwork & routing · Nov 20, 10:21 PM PT: 0 itemsNetwork & routing · Nov 20, 11:55 PM PT: 1 itemNetwork & routing · Nov 21, 1:29 AM PT: 0 itemsNetwork & routing · Nov 21, 3:03 AM PT: 3 itemsEarly signalsEarly signals · Nov 19, 3:00 PM PT: 0 itemsEarly signals · Nov 19, 4:34 PM PT: 0 itemsEarly signals · Nov 19, 6:08 PM PT: 0 itemsEarly signals · Nov 19, 7:43 PM PT: 0 itemsEarly signals · Nov 19, 9:17 PM PT: 0 itemsEarly signals · Nov 19, 10:51 PM PT: 0 itemsEarly signals · Nov 20, 12:25 AM PT: 0 itemsEarly signals · Nov 20, 1:59 AM PT: 0 itemsEarly signals · Nov 20, 3:33 AM PT: 0 itemsEarly signals · Nov 20, 5:07 AM PT: 0 itemsEarly signals · Nov 20, 6:41 AM PT: 0 itemsEarly signals · Nov 20, 8:15 AM PT: 0 itemsEarly signals · Nov 20, 9:49 AM PT: 0 itemsEarly signals · Nov 20, 11:23 AM PT: 0 itemsEarly signals · Nov 20, 12:57 PM PT: 0 itemsEarly signals · Nov 20, 2:31 PM PT: 0 itemsEarly signals · Nov 20, 4:05 PM PT: 0 itemsEarly signals · Nov 20, 5:39 PM PT: 0 itemsEarly signals · Nov 20, 7:13 PM PT: 0 itemsEarly signals · Nov 20, 8:47 PM PT: 0 itemsEarly signals · Nov 20, 10:21 PM PT: 0 itemsEarly signals · Nov 20, 11:55 PM PT: 0 itemsEarly signals · Nov 21, 1:29 AM PT: 0 itemsEarly signals · Nov 21, 3:03 AM PT: 0 itemsNews & chatterNews & chatter · Nov 19, 3:00 PM PT: 0 itemsNews & chatter · Nov 19, 4:34 PM PT: 1 itemNews & chatter · Nov 19, 6:08 PM PT: 0 itemsNews & chatter · Nov 19, 7:43 PM PT: 0 itemsNews & chatter · Nov 19, 9:17 PM PT: 0 itemsNews & chatter · Nov 19, 10:51 PM PT: 0 itemsNews & chatter · Nov 20, 12:25 AM PT: 0 itemsNews & chatter · Nov 20, 1:59 AM PT: 0 itemsNews & chatter · Nov 20, 3:33 AM PT: 0 itemsNews & chatter · Nov 20, 5:07 AM PT: 0 itemsNews & chatter · Nov 20, 6:41 AM PT: 0 itemsNews & chatter · Nov 20, 8:15 AM PT: 0 itemsNews & chatter · Nov 20, 9:49 AM PT: 0 itemsNews & chatter · Nov 20, 11:23 AM PT: 2 itemsNews & chatter · Nov 20, 12:57 PM PT: 0 itemsNews & chatter · Nov 20, 2:31 PM PT: 0 itemsNews & chatter · Nov 20, 4:05 PM PT: 0 itemsNews & chatter · Nov 20, 5:39 PM PT: 0 itemsNews & chatter · Nov 20, 7:13 PM PT: 0 itemsNews & chatter · Nov 20, 8:47 PM PT: 0 itemsNews & chatter · Nov 20, 10:21 PM PT: 0 itemsNews & chatter · Nov 20, 11:55 PM PT: 0 itemsNews & chatter · Nov 21, 1:29 AM PT: 0 itemsNews & chatter · Nov 21, 3:03 AM PT: 0 itemsCoincidence (KEV)Coincidence (KEV) · Nov 19, 3:00 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 4:34 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 6:08 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 7:43 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 9:17 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 10:51 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 12:25 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 1:59 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 3:33 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 5:07 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 6:41 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 8:15 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 9:49 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 11:23 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 12:57 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 2:31 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 4:05 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 5:39 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 7:13 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 8:47 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 10:21 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 11:55 PM PT: 0 itemsCoincidence (KEV) · Nov 21, 1:29 AM PT: 0 itemsCoincidence (KEV) · Nov 21, 3:03 AM PT: 0 itemsNov 19, 3:00 PM PTnow

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:00 PM PTORBIT first saw itNov 20, 6:28 AM PTLast checkedNov 21, 4:37 AM PT

Detection gap not measurable from public clocks.

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

  • Open 31h 37m. At that age this is a standing condition, not an incident. It deserves its own runbook and its own SLO conversation.
  • 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 19 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 →Status page →

Embed this card
<a href="https://www.chyp.ai/dissect/vi/cloudflare~4lv21sf5fzhm/"><img src="https://www.chyp.ai/dissect/vi/cloudflare~4lv21sf5fzhm/card.svg" alt="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.
  • 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.