CHYP.ai · ORBIT // Cloudy_Day Security Suite

OUTAGE DISSECTOR · CASE FILE · NetWeather event

Cloudflare: 2 components degraded performance

Cloudflare active M5.0 Storm since Nov 14, 5:37 AM PT

Cloudflare reported “Cloudflare: 2 components degraded performance” starting Nov 14, 5:37 AM PT.

  • 6d 23hDurationand counting
  • 4Peak componentsnow 2
  • —Places named0 on the map
  • 14Dependentscatalogued, inferred
  • 2/4Evidence kindsindependent families
  • 13Updatesofficial revisions

1Scrub the outage

full window
Severitypeak 4 components Nov 14, 11 AMNov 15, 6 PMNov 17, 1 AMNov 18, 8 AMNov 19, 3 PMNov 20, 11 PM Official statusNov 19, 3:38 AM PT · Cloudflare: 2 components degraded performanceNov 19, 5:06 AM PT · Cloudflare: 4 components degraded performanceNov 19, 5:38 AM PT · Cloudflare: 2 components degraded performanceNov 19, 8:30 AM PT · Cloudflare: 3 components degraded performanceNov 19, 1:56 PM PT · Cloudflare: 2 components degraded performanceNov 19, 6:54 PM PT · Cloudflare: 4 components degraded performanceNov 19, 8:36 PM PT · Cloudflare: 2 components degraded performanceNov 19, 9:00 PM PT · Vendor incident opened: Network Performance Issues in Miami (minor)Nov 20, 10:02 AM PT · Cloudflare: 3 components degraded performanceNov 20, 11:42 AM PT · Cloudflare: 2 components degraded performanceNov 20, 12:35 PM PT · Vendor incident opened: Network Performance Issues in Washington, DC datacenter (IAD) (minor)Nov 20, 12:36 PM PT · Cloudflare: 3 components degraded performanceNov 20, 12:51 PM PT · Vendor incident opened: Cache Purging Delays in Milan (none)Nov 20, 12:58 PM PT · Cloudflare: 4 components degraded performanceNov 20, 2:26 PM PT · Cloudflare: 3 components degraded performanceNov 20, 11:44 PM PT · Cloudflare: 2 components degraded performanceNetwork & 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 18, 5:52 PM PT · Cloudflare: 2 components partial outage · OCNov 21, 1:00 AM PT · AS13335 (Cloudflare) BGP update churn -0.7σ vs 24hEarly signalsnothing in this windowNews & chatterNov 15, 5:17 AM PT · CVE-2026-129468 (MEDIUM 4.3): Netcccyun dnsmgr 2.18 before 2.22 contains a missing authorizationNov 17, 12:24 PM PT · Quad9’s withdrawal from France: A canary in the coal mineNov 18, 6:52 AM PT · How Cloudflare WAF helps protect against Java4Shell (CVE-2026-114938)Nov 18, 2:00 PM PT · An updated Clairic and Clairic-flash are now open-weight, from the new Workers AI Superintelligence…Nov 19, 1:10 AM PT · Java4Shell Exploitation Attempts Begin as Vendors Rush Out AdvisoriesNov 19, 6:00 AM PT · Internet traffic and attacks during the 2026 U.S. midterm electionsNov 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 “Cloudflare: 2 components degraded performance” starting Nov 14, 5:37 AM 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: global/unspecified.

How it recovered

Still open after 6d 23h, easing: 2 of a peak 4 components remain.

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: 19 components partial outage · ASChina ×4 · Qingdao, China - (TAO); Shenzhen, China - (SZX); Chongqing, China - (CKG); Xiangyang, China - (XFN) · same provider, other region: Cloudflare: 19 components partial outage · ASAsia · Hagatna, Guam - (GUM) · same provider, other region: Cloudflare: 19 components partial outage · ASPakistan · Islamabad, Pakistan - (ISB) · same provider, other region: Cloudflare: 19 components partial outage · ASMalaysia · Johor Bahru, Malaysia - (JHB) · same provider, other region: Cloudflare: 19 components partial outage · ASKolkata (CCU) · Kolkata, India - (CCU) · same provider, other region: Cloudflare: 19 components partial outage · ASAlgeria · Annaba, Algeria - (AAE) · same provider, other region: Cloudflare: 7 components partial outage · AFMozambique · Maputo, Mozambique - (MPM) · same provider, other region: Cloudflare: 7 components partial outage · AFCongo · Kinshasa, Congo - Kinshasa - (FIH) · same provider, other region: Cloudflare: 7 components partial outage · AFNamibia · Windhoek, Namibia - (WDH) · same provider, other region: Cloudflare: 7 components partial outage · AFUganda · Kampala, Uganda - (EBB) · same provider, other region: Cloudflare: 7 components partial outage · AFZambia · Lusaka, Zambia - (LUN) · same provider, other region: Cloudflare: 7 components partial outage · AFMalawi · Lilongwe, Malawi - (LLW) · same provider, other region: Cloudflare: 7 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 · SABelarus · Minsk, Belarus - (MSQ) · same provider, other region: Cloudflare: 3 components partial outage · EURussia · Saint Petersburg, Russia - (LED) · same provider, other region: Cloudflare: 3 components partial outage · EUKazakhstan · Aktobe, Kazakhstan - (AKX) · same provider, other region: Cloudflare: 3 components partial outage · EUUnited 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 · NAAustralia · 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 · OC

Bright: this event. Dim: the same provider's other open events (7). 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“degraded performance”
  • Retry amplificationno sign

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

5Evidence matrix

Official statusOfficial status · Nov 13, 11:37 PM PT: 0 itemsOfficial status · Nov 14, 6:50 AM PT: 0 itemsOfficial status · Nov 14, 2:03 PM PT: 0 itemsOfficial status · Nov 14, 9:16 PM PT: 0 itemsOfficial status · Nov 15, 4:28 AM PT: 0 itemsOfficial status · Nov 15, 11:41 AM PT: 0 itemsOfficial status · Nov 15, 6:54 PM PT: 0 itemsOfficial status · Nov 16, 2:07 AM PT: 0 itemsOfficial status · Nov 16, 9:20 AM PT: 0 itemsOfficial status · Nov 16, 4:33 PM PT: 0 itemsOfficial status · Nov 16, 11:45 PM PT: 0 itemsOfficial status · Nov 17, 6:58 AM PT: 0 itemsOfficial status · Nov 17, 2:11 PM PT: 0 itemsOfficial status · Nov 17, 9:24 PM PT: 0 itemsOfficial status · Nov 18, 4:37 AM PT: 0 itemsOfficial status · Nov 18, 11:49 AM PT: 0 itemsOfficial status · Nov 18, 7:02 PM PT: 0 itemsOfficial status · Nov 19, 2:15 AM PT: 4 itemsOfficial status · Nov 19, 9:28 AM PT: 1 itemOfficial status · Nov 19, 4:41 PM PT: 3 itemsOfficial status · Nov 19, 11:54 PM PT: 0 itemsOfficial status · Nov 20, 7:06 AM PT: 6 itemsOfficial status · Nov 20, 2:19 PM PT: 1 itemOfficial status · Nov 20, 9:32 PM PT: 1 itemNetwork & routingNetwork & routing · Nov 13, 11:37 PM PT: 0 itemsNetwork & routing · Nov 14, 6:50 AM PT: 0 itemsNetwork & routing · Nov 14, 2:03 PM PT: 0 itemsNetwork & routing · Nov 14, 9:16 PM PT: 0 itemsNetwork & routing · Nov 15, 4:28 AM PT: 0 itemsNetwork & routing · Nov 15, 11:41 AM PT: 0 itemsNetwork & routing · Nov 15, 6:54 PM PT: 0 itemsNetwork & routing · Nov 16, 2:07 AM PT: 0 itemsNetwork & routing · Nov 16, 9:20 AM PT: 0 itemsNetwork & routing · Nov 16, 4:33 PM PT: 0 itemsNetwork & routing · Nov 16, 11:45 PM PT: 0 itemsNetwork & routing · Nov 17, 6:58 AM PT: 0 itemsNetwork & routing · Nov 17, 2:11 PM PT: 0 itemsNetwork & routing · Nov 17, 9:24 PM PT: 0 itemsNetwork & routing · Nov 18, 4:37 AM PT: 0 itemsNetwork & routing · Nov 18, 11:49 AM PT: 1 itemNetwork & routing · Nov 18, 7:02 PM PT: 0 itemsNetwork & routing · Nov 19, 2:15 AM PT: 0 itemsNetwork & routing · Nov 19, 9:28 AM PT: 0 itemsNetwork & routing · Nov 19, 4:41 PM PT: 1 itemNetwork & routing · Nov 19, 11:54 PM PT: 1 itemNetwork & routing · Nov 20, 7:06 AM PT: 0 itemsNetwork & routing · Nov 20, 2:19 PM PT: 0 itemsNetwork & routing · Nov 20, 9:32 PM PT: 4 itemsEarly signalsEarly signals · Nov 13, 11:37 PM PT: 0 itemsEarly signals · Nov 14, 6:50 AM PT: 0 itemsEarly signals · Nov 14, 2:03 PM PT: 0 itemsEarly signals · Nov 14, 9:16 PM PT: 0 itemsEarly signals · Nov 15, 4:28 AM PT: 0 itemsEarly signals · Nov 15, 11:41 AM PT: 0 itemsEarly signals · Nov 15, 6:54 PM PT: 0 itemsEarly signals · Nov 16, 2:07 AM PT: 0 itemsEarly signals · Nov 16, 9:20 AM PT: 0 itemsEarly signals · Nov 16, 4:33 PM PT: 0 itemsEarly signals · Nov 16, 11:45 PM PT: 0 itemsEarly signals · Nov 17, 6:58 AM PT: 0 itemsEarly signals · Nov 17, 2:11 PM PT: 0 itemsEarly signals · Nov 17, 9:24 PM PT: 0 itemsEarly signals · Nov 18, 4:37 AM PT: 0 itemsEarly signals · Nov 18, 11:49 AM PT: 0 itemsEarly signals · Nov 18, 7:02 PM PT: 0 itemsEarly signals · Nov 19, 2:15 AM PT: 0 itemsEarly signals · Nov 19, 9:28 AM PT: 0 itemsEarly signals · Nov 19, 4:41 PM PT: 0 itemsEarly signals · Nov 19, 11:54 PM PT: 0 itemsEarly signals · Nov 20, 7:06 AM PT: 0 itemsEarly signals · Nov 20, 2:19 PM PT: 0 itemsEarly signals · Nov 20, 9:32 PM PT: 0 itemsNews & chatterNews & chatter · Nov 13, 11:37 PM PT: 0 itemsNews & chatter · Nov 14, 6:50 AM PT: 0 itemsNews & chatter · Nov 14, 2:03 PM PT: 0 itemsNews & chatter · Nov 14, 9:16 PM PT: 0 itemsNews & chatter · Nov 15, 4:28 AM PT: 1 itemNews & chatter · Nov 15, 11:41 AM PT: 0 itemsNews & chatter · Nov 15, 6:54 PM PT: 0 itemsNews & chatter · Nov 16, 2:07 AM PT: 0 itemsNews & chatter · Nov 16, 9:20 AM PT: 0 itemsNews & chatter · Nov 16, 4:33 PM PT: 0 itemsNews & chatter · Nov 16, 11:45 PM PT: 0 itemsNews & chatter · Nov 17, 6:58 AM PT: 1 itemNews & chatter · Nov 17, 2:11 PM PT: 0 itemsNews & chatter · Nov 17, 9:24 PM PT: 0 itemsNews & chatter · Nov 18, 4:37 AM PT: 1 itemNews & chatter · Nov 18, 11:49 AM PT: 1 itemNews & chatter · Nov 18, 7:02 PM PT: 1 itemNews & chatter · Nov 19, 2:15 AM PT: 1 itemNews & chatter · Nov 19, 9:28 AM PT: 0 itemsNews & chatter · Nov 19, 4:41 PM PT: 1 itemNews & chatter · Nov 19, 11:54 PM PT: 0 itemsNews & chatter · Nov 20, 7:06 AM PT: 2 itemsNews & chatter · Nov 20, 2:19 PM PT: 0 itemsNews & chatter · Nov 20, 9:32 PM PT: 0 itemsCoincidence (KEV)Coincidence (KEV) · Nov 13, 11:37 PM PT: 0 itemsCoincidence (KEV) · Nov 14, 6:50 AM PT: 0 itemsCoincidence (KEV) · Nov 14, 2:03 PM PT: 0 itemsCoincidence (KEV) · Nov 14, 9:16 PM PT: 0 itemsCoincidence (KEV) · Nov 15, 4:28 AM PT: 0 itemsCoincidence (KEV) · Nov 15, 11:41 AM PT: 0 itemsCoincidence (KEV) · Nov 15, 6:54 PM PT: 0 itemsCoincidence (KEV) · Nov 16, 2:07 AM PT: 0 itemsCoincidence (KEV) · Nov 16, 9:20 AM PT: 0 itemsCoincidence (KEV) · Nov 16, 4:33 PM PT: 0 itemsCoincidence (KEV) · Nov 16, 11:45 PM PT: 0 itemsCoincidence (KEV) · Nov 17, 6:58 AM PT: 0 itemsCoincidence (KEV) · Nov 17, 2:11 PM PT: 0 itemsCoincidence (KEV) · Nov 17, 9:24 PM PT: 0 itemsCoincidence (KEV) · Nov 18, 4:37 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 11:49 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 7:02 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 2:15 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 9:28 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 4:41 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 11:54 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 7:06 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 2:19 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 9:32 PM PT: 0 itemsNov 13, 11:37 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 14, 5:37 AM PTORBIT first saw itNov 19, 3:38 AM PTLatest source updateNov 19, 1:55 PM PTLast checkedNov 21, 4:44 AM PT

This event was already open when the NetWeather ledger started (Nov 19, 2026), so the detection gap isn't measurable.

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 6d 23h. 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 →NetWeather evidence page →Status page →

Embed this card
<a href="https://www.chyp.ai/dissect/event-nw-ff1dfba75976a9c0/"><img src="https://www.chyp.ai/dissect/event-nw-ff1dfba75976a9c0/card.svg" alt="Cloudflare: 2 components degraded performance · 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.
  • Region: global / unspecified. The source did not assert a region; none was inferred from publisher location.
  • 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.