CHYP.ai · ORBIT // Cloudy_Day Security Suite

OUTAGE DISSECTOR · CASE FILE · NetWeather event

Akamai: Customer Security Advisory: Remote code execution vulnerability in the Apache HTTP Server's HTTP/2 module

Akamai advisory M4.4 Squall since Nov 17, 5:36 AM PT

Akamai reported “Akamai: Customer Security Advisory: Remote code execution vulnerability in the Apache HTTP Server's HTTP/2 mo…” starting Nov 17, 5:36 AM PT.

  • 5d 1hDurationand counting
  • 2Systems namedfrom the source
  • —Places named0 on the map
  • 1Dependentscatalogued, inferred
  • 3/4Evidence kindsindependent families
  • 1Updatesofficial revisions

1Scrub the outage

full window
Severityofficial state Nov 17, 8 AMNov 18, 7 AMNov 19, 6 AMNov 20, 5 AMNov 21, 4 AMNov 22, 2 AM Official statusNov 17, 4:46 AM PT · Vendor incident opened: Customer Security Advisory: Remote code execution vulnerability in the Apache H… (minor)Nov 17, 9:40 AM PT · Vendor incident opened: Edge Delivery Issues in Singapore and Japan Regions (minor)Nov 18, 1:31 AM PT · Vendor incident opened: Customer Security Advisory: CVE-2026-114938 (none)Nov 19, 3:38 AM PT · Akamai: Customer Security Advisory: Remote code execution vulnerability in the Apache HTTP Server's HTTP/2 moduleNov 19, 7:20 PM PT · Vendor incident opened: Reporting Issues (minor)Network & routingNov 20, 2:12 AM PT · Akamai Cloud (Linode): Service Issue - Linode Kubernetes EngineNov 20, 1:43 AM PT · Akamai: Reporting IssuesNov 19, 7:20 PM PT · Akamai: 1 component degraded performanceNov 18, 1:31 AM PT · Akamai: Customer Security Advisory: CVE-2026-114938Nov 22, 3:00 AM PT · AS20940 (Akamai) BGP update churn -0.7σ vs 24hEarly signalsnothing in this windowNews & chatterNov 18, 1:31 AM PT · Customer Security Advisory: CVE-2026-114938Nov 18, 2:37 PM PT · Configuration Deployment delaysNov 19, 8:59 AM PT · Edge Delivery Issues in Singapore and Japan RegionsNov 19, 7:20 PM PT · Reporting IssuesCoincidence (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

Akamai reported “Akamai: Customer Security Advisory: Remote code execution vulnerability in the Apache HTTP Server's HTTP/2 mo…” starting Nov 17, 5:36 AM PT.

What broke

Reporting, Customer Security Advisory.

Who was hit

1 catalogued service run on Akamai (inferred). Hit: global/unspecified.

How it recovered

Still open after 5d 1h.

2Blast radius

Linode (Akamai Cloud) · OperationalLinode (Akamai …Akamai1 dependents

Center: Akamai. Inner ring: what it runs on. Outer ring: catalogued services that run on it, coloured by their official status right now. Dependencies are inferred from public information.

3Blast map

No place names in the public text. Region tag: global/unspecified.

Places come from names in the public text (cities, PoP codes, countries, regions). Approximate.

4Failure-mode fingerprint

RetriesControl planeConfig pushCascadeCapacity
  • Control-plane coupling“login”
  • Retry amplificationno sign
  • Config propagationno sign
  • Dependency cascadeno sign
  • Capacity exhaustionno sign

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

5Evidence matrix

Official statusOfficial status · Nov 16, 11:36 PM PT: 1 itemOfficial status · Nov 17, 4:55 AM PT: 1 itemOfficial status · Nov 17, 10:14 AM PT: 0 itemsOfficial status · Nov 17, 3:32 PM PT: 0 itemsOfficial status · Nov 17, 8:51 PM PT: 1 itemOfficial status · Nov 18, 2:10 AM PT: 0 itemsOfficial status · Nov 18, 7:29 AM PT: 0 itemsOfficial status · Nov 18, 12:47 PM PT: 0 itemsOfficial status · Nov 18, 6:06 PM PT: 0 itemsOfficial status · Nov 18, 11:25 PM PT: 1 itemOfficial status · Nov 19, 4:44 AM PT: 0 itemsOfficial status · Nov 19, 10:02 AM PT: 0 itemsOfficial status · Nov 19, 3:21 PM PT: 1 itemOfficial status · Nov 19, 8:40 PM PT: 0 itemsOfficial status · Nov 20, 1:59 AM PT: 0 itemsOfficial status · Nov 20, 7:17 AM PT: 0 itemsOfficial status · Nov 20, 12:36 PM PT: 0 itemsOfficial status · Nov 20, 5:55 PM PT: 0 itemsOfficial status · Nov 20, 11:14 PM PT: 0 itemsOfficial status · Nov 21, 4:33 AM PT: 0 itemsOfficial status · Nov 21, 9:51 AM PT: 0 itemsOfficial status · Nov 21, 3:10 PM PT: 0 itemsOfficial status · Nov 21, 8:29 PM PT: 0 itemsOfficial status · Nov 22, 1:48 AM PT: 0 itemsNetwork & routingNetwork & routing · Nov 16, 11:36 PM PT: 0 itemsNetwork & routing · Nov 17, 4:55 AM PT: 0 itemsNetwork & routing · Nov 17, 10:14 AM PT: 0 itemsNetwork & routing · Nov 17, 3:32 PM PT: 0 itemsNetwork & routing · Nov 17, 8:51 PM PT: 1 itemNetwork & routing · Nov 18, 2:10 AM PT: 0 itemsNetwork & routing · Nov 18, 7:29 AM PT: 0 itemsNetwork & routing · Nov 18, 12:47 PM PT: 0 itemsNetwork & routing · Nov 18, 6:06 PM PT: 0 itemsNetwork & routing · Nov 18, 11:25 PM PT: 0 itemsNetwork & routing · Nov 19, 4:44 AM PT: 0 itemsNetwork & routing · Nov 19, 10:02 AM PT: 0 itemsNetwork & routing · Nov 19, 3:21 PM PT: 1 itemNetwork & routing · Nov 19, 8:40 PM PT: 1 itemNetwork & routing · Nov 20, 1:59 AM PT: 1 itemNetwork & routing · Nov 20, 7:17 AM PT: 0 itemsNetwork & routing · Nov 20, 12:36 PM PT: 0 itemsNetwork & routing · Nov 20, 5:55 PM PT: 0 itemsNetwork & routing · Nov 20, 11:14 PM PT: 0 itemsNetwork & routing · Nov 21, 4:33 AM PT: 0 itemsNetwork & routing · Nov 21, 9:51 AM PT: 0 itemsNetwork & routing · Nov 21, 3:10 PM PT: 0 itemsNetwork & routing · Nov 21, 8:29 PM PT: 0 itemsNetwork & routing · Nov 22, 1:48 AM PT: 1 itemEarly signalsEarly signals · Nov 16, 11:36 PM PT: 0 itemsEarly signals · Nov 17, 4:55 AM PT: 0 itemsEarly signals · Nov 17, 10:14 AM PT: 0 itemsEarly signals · Nov 17, 3:32 PM PT: 0 itemsEarly signals · Nov 17, 8:51 PM PT: 0 itemsEarly signals · Nov 18, 2:10 AM PT: 0 itemsEarly signals · Nov 18, 7:29 AM PT: 0 itemsEarly signals · Nov 18, 12:47 PM PT: 0 itemsEarly signals · Nov 18, 6:06 PM PT: 0 itemsEarly signals · Nov 18, 11:25 PM PT: 0 itemsEarly signals · Nov 19, 4:44 AM PT: 0 itemsEarly signals · Nov 19, 10:02 AM PT: 0 itemsEarly signals · Nov 19, 3:21 PM PT: 0 itemsEarly signals · Nov 19, 8:40 PM PT: 0 itemsEarly signals · Nov 20, 1:59 AM PT: 0 itemsEarly signals · Nov 20, 7:17 AM PT: 0 itemsEarly signals · Nov 20, 12:36 PM PT: 0 itemsEarly signals · Nov 20, 5:55 PM PT: 0 itemsEarly signals · Nov 20, 11:14 PM PT: 0 itemsEarly signals · Nov 21, 4:33 AM PT: 0 itemsEarly signals · Nov 21, 9:51 AM PT: 0 itemsEarly signals · Nov 21, 3:10 PM PT: 0 itemsEarly signals · Nov 21, 8:29 PM PT: 0 itemsEarly signals · Nov 22, 1:48 AM PT: 0 itemsNews & chatterNews & chatter · Nov 16, 11:36 PM PT: 0 itemsNews & chatter · Nov 17, 4:55 AM PT: 0 itemsNews & chatter · Nov 17, 10:14 AM PT: 0 itemsNews & chatter · Nov 17, 3:32 PM PT: 0 itemsNews & chatter · Nov 17, 8:51 PM PT: 1 itemNews & chatter · Nov 18, 2:10 AM PT: 0 itemsNews & chatter · Nov 18, 7:29 AM PT: 0 itemsNews & chatter · Nov 18, 12:47 PM PT: 1 itemNews & chatter · Nov 18, 6:06 PM PT: 0 itemsNews & chatter · Nov 18, 11:25 PM PT: 0 itemsNews & chatter · Nov 19, 4:44 AM PT: 1 itemNews & chatter · Nov 19, 10:02 AM PT: 0 itemsNews & chatter · Nov 19, 3:21 PM PT: 1 itemNews & chatter · Nov 19, 8:40 PM PT: 0 itemsNews & chatter · Nov 20, 1:59 AM PT: 0 itemsNews & chatter · Nov 20, 7:17 AM PT: 0 itemsNews & chatter · Nov 20, 12:36 PM PT: 0 itemsNews & chatter · Nov 20, 5:55 PM PT: 0 itemsNews & chatter · Nov 20, 11:14 PM PT: 0 itemsNews & chatter · Nov 21, 4:33 AM PT: 0 itemsNews & chatter · Nov 21, 9:51 AM PT: 0 itemsNews & chatter · Nov 21, 3:10 PM PT: 0 itemsNews & chatter · Nov 21, 8:29 PM PT: 0 itemsNews & chatter · Nov 22, 1:48 AM PT: 0 itemsCoincidence (KEV)Coincidence (KEV) · Nov 16, 11:36 PM PT: 0 itemsCoincidence (KEV) · Nov 17, 4:55 AM PT: 0 itemsCoincidence (KEV) · Nov 17, 10:14 AM PT: 0 itemsCoincidence (KEV) · Nov 17, 3:32 PM PT: 0 itemsCoincidence (KEV) · Nov 17, 8:51 PM PT: 0 itemsCoincidence (KEV) · Nov 18, 2:10 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 7:29 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 12:47 PM PT: 0 itemsCoincidence (KEV) · Nov 18, 6:06 PM PT: 0 itemsCoincidence (KEV) · Nov 18, 11:25 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 4:44 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 10:02 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 3:21 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 8:40 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 1:59 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 7:17 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 12:36 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 5:55 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 11:14 PM PT: 0 itemsCoincidence (KEV) · Nov 21, 4:33 AM PT: 0 itemsCoincidence (KEV) · Nov 21, 9:51 AM PT: 0 itemsCoincidence (KEV) · Nov 21, 3:10 PM PT: 0 itemsCoincidence (KEV) · Nov 21, 8:29 PM PT: 0 itemsCoincidence (KEV) · Nov 22, 1:48 AM PT: 0 itemsNov 16, 11:36 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 17, 5:36 AM PTORBIT first saw itNov 19, 3:38 AM PTLatest source updateNov 17, 5:36 AM PTLast checkedNov 22, 7:06 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 5d 1h. At that age this is a standing condition, not an incident. It deserves its own runbook and its own SLO conversation.
  • 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.
  • 3 independent kinds of public evidence line up in the same window. Corroboration, still not causation.

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 Akamai.

8Dissection capsule

Share card for this dissection

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

JSON capsuleMarkdownShare card (SVG)

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

Embed this card
<a href="https://www.chyp.ai/dissect/event-nw-20e2ef18a32e4369/"><img src="https://www.chyp.ai/dissect/event-nw-20e2ef18a32e4369/card.svg" alt="Akamai: Customer Security Advisory: Remote code execution v… · 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.