CHYP.ai · ORBIT // Cloudy_Day Security Suite

OUTAGE DISSECTOR · CASE FILE · NetWeather event

Akamai: Reporting Issues

Akamai monitoring M4.3 Squall since Nov 19, 7:20 PM PT

Akamai reported “Akamai: Reporting Issues” starting Nov 19, 7:20 PM PT.

  • 33h 30mDurationand counting
  • 2Systems namedfrom the source
  • —Places named0 on the map
  • 1Dependentscatalogued, inferred
  • 3/4Evidence kindsindependent families
  • 3Updatesofficial revisions

1Scrub the outage

full window
Severityofficial state Nov 19, 8 PMNov 20, 2 AMNov 20, 8 AMNov 20, 3 PMNov 20, 9 PMNov 21, 3 AM Official statusNov 19, 7:20 PM PT · Vendor incident opened: Reporting Issues (minor)Nov 19, 7:20 PM PT · Akamai: Reporting IssuesNov 19, 8:20 PM PT · Akamai: Reporting IssuesNov 20, 1:44 AM PT · Akamai: Reporting IssuesNetwork & routingNov 20, 2:12 AM PT · Akamai Cloud (Linode): Service Issue - Linode Kubernetes EngineNov 19, 7:20 PM PT · Akamai: 1 component degraded performanceNov 21, 1:00 AM PT · AS20940 (Akamai) BGP update churn -1.1σ vs 24hEarly signalsnothing in this windowNews & chatterNov 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: Reporting Issues” starting Nov 19, 7:20 PM 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 33h 30m, at or near its peak (1 state).

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
  • Retry amplificationno sign
  • Control-plane couplingno 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 19, 1:20 PM PT: 0 itemsOfficial status · Nov 19, 2:59 PM PT: 0 itemsOfficial status · Nov 19, 4:37 PM PT: 0 itemsOfficial status · Nov 19, 6:16 PM PT: 2 itemsOfficial status · Nov 19, 7:55 PM PT: 1 itemOfficial status · Nov 19, 9:34 PM PT: 0 itemsOfficial status · Nov 19, 11:12 PM PT: 0 itemsOfficial status · Nov 20, 12:51 AM PT: 1 itemOfficial status · Nov 20, 2:30 AM PT: 0 itemsOfficial status · Nov 20, 4:09 AM PT: 0 itemsOfficial status · Nov 20, 5:47 AM PT: 0 itemsOfficial status · Nov 20, 7:26 AM PT: 0 itemsOfficial status · Nov 20, 9:05 AM PT: 0 itemsOfficial status · Nov 20, 10:44 AM PT: 0 itemsOfficial status · Nov 20, 12:22 PM PT: 0 itemsOfficial status · Nov 20, 2:01 PM PT: 0 itemsOfficial status · Nov 20, 3:40 PM PT: 0 itemsOfficial status · Nov 20, 5:19 PM PT: 0 itemsOfficial status · Nov 20, 6:58 PM PT: 0 itemsOfficial status · Nov 20, 8:36 PM PT: 0 itemsOfficial status · Nov 20, 10:15 PM PT: 0 itemsOfficial status · Nov 20, 11:54 PM PT: 0 itemsOfficial status · Nov 21, 1:33 AM PT: 0 itemsOfficial status · Nov 21, 3:11 AM PT: 0 itemsNetwork & routingNetwork & routing · Nov 19, 1:20 PM PT: 0 itemsNetwork & routing · Nov 19, 2:59 PM PT: 0 itemsNetwork & routing · Nov 19, 4:37 PM PT: 0 itemsNetwork & routing · Nov 19, 6:16 PM PT: 1 itemNetwork & routing · Nov 19, 7:55 PM PT: 0 itemsNetwork & routing · Nov 19, 9:34 PM PT: 0 itemsNetwork & routing · Nov 19, 11:12 PM PT: 0 itemsNetwork & routing · Nov 20, 12:51 AM PT: 1 itemNetwork & routing · Nov 20, 2:30 AM PT: 0 itemsNetwork & routing · Nov 20, 4:09 AM PT: 0 itemsNetwork & routing · Nov 20, 5:47 AM PT: 0 itemsNetwork & routing · Nov 20, 7:26 AM PT: 0 itemsNetwork & routing · Nov 20, 9:05 AM PT: 0 itemsNetwork & routing · Nov 20, 10:44 AM PT: 0 itemsNetwork & routing · Nov 20, 12:22 PM PT: 0 itemsNetwork & routing · Nov 20, 2:01 PM PT: 0 itemsNetwork & routing · Nov 20, 3:40 PM PT: 0 itemsNetwork & routing · Nov 20, 5:19 PM PT: 0 itemsNetwork & routing · Nov 20, 6:58 PM PT: 0 itemsNetwork & routing · Nov 20, 8:36 PM PT: 0 itemsNetwork & routing · Nov 20, 10:15 PM PT: 0 itemsNetwork & routing · Nov 20, 11:54 PM PT: 1 itemNetwork & routing · Nov 21, 1:33 AM PT: 0 itemsNetwork & routing · Nov 21, 3:11 AM PT: 0 itemsEarly signalsEarly signals · Nov 19, 1:20 PM PT: 0 itemsEarly signals · Nov 19, 2:59 PM PT: 0 itemsEarly signals · Nov 19, 4:37 PM PT: 0 itemsEarly signals · Nov 19, 6:16 PM PT: 0 itemsEarly signals · Nov 19, 7:55 PM PT: 0 itemsEarly signals · Nov 19, 9:34 PM PT: 0 itemsEarly signals · Nov 19, 11:12 PM PT: 0 itemsEarly signals · Nov 20, 12:51 AM PT: 0 itemsEarly signals · Nov 20, 2:30 AM PT: 0 itemsEarly signals · Nov 20, 4:09 AM PT: 0 itemsEarly signals · Nov 20, 5:47 AM PT: 0 itemsEarly signals · Nov 20, 7:26 AM PT: 0 itemsEarly signals · Nov 20, 9:05 AM PT: 0 itemsEarly signals · Nov 20, 10:44 AM PT: 0 itemsEarly signals · Nov 20, 12:22 PM PT: 0 itemsEarly signals · Nov 20, 2:01 PM PT: 0 itemsEarly signals · Nov 20, 3:40 PM PT: 0 itemsEarly signals · Nov 20, 5:19 PM PT: 0 itemsEarly signals · Nov 20, 6:58 PM PT: 0 itemsEarly signals · Nov 20, 8:36 PM PT: 0 itemsEarly signals · Nov 20, 10:15 PM PT: 0 itemsEarly signals · Nov 20, 11:54 PM PT: 0 itemsEarly signals · Nov 21, 1:33 AM PT: 0 itemsEarly signals · Nov 21, 3:11 AM PT: 0 itemsNews & chatterNews & chatter · Nov 19, 1:20 PM PT: 0 itemsNews & chatter · Nov 19, 2:59 PM PT: 0 itemsNews & chatter · Nov 19, 4:37 PM PT: 0 itemsNews & chatter · Nov 19, 6:16 PM PT: 1 itemNews & chatter · Nov 19, 7:55 PM PT: 0 itemsNews & chatter · Nov 19, 9:34 PM PT: 0 itemsNews & chatter · Nov 19, 11:12 PM PT: 0 itemsNews & chatter · Nov 20, 12:51 AM PT: 0 itemsNews & chatter · Nov 20, 2:30 AM PT: 0 itemsNews & chatter · Nov 20, 4:09 AM PT: 0 itemsNews & chatter · Nov 20, 5:47 AM PT: 0 itemsNews & chatter · Nov 20, 7:26 AM PT: 0 itemsNews & chatter · Nov 20, 9:05 AM PT: 0 itemsNews & chatter · Nov 20, 10:44 AM PT: 0 itemsNews & chatter · Nov 20, 12:22 PM PT: 0 itemsNews & chatter · Nov 20, 2:01 PM PT: 0 itemsNews & chatter · Nov 20, 3:40 PM PT: 0 itemsNews & chatter · Nov 20, 5:19 PM PT: 0 itemsNews & chatter · Nov 20, 6:58 PM PT: 0 itemsNews & chatter · Nov 20, 8:36 PM PT: 0 itemsNews & chatter · Nov 20, 10:15 PM PT: 0 itemsNews & chatter · Nov 20, 11:54 PM PT: 0 itemsNews & chatter · Nov 21, 1:33 AM PT: 0 itemsNews & chatter · Nov 21, 3:11 AM PT: 0 itemsCoincidence (KEV)Coincidence (KEV) · Nov 19, 1:20 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 2:59 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 4:37 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 6:16 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 7:55 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 9:34 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 11:12 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 12:51 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 2:30 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 4:09 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 5:47 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 7:26 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 9:05 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 10:44 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 12:22 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 2:01 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 3:40 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 5:19 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 6:58 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 8:36 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 10:15 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 11:54 PM PT: 0 itemsCoincidence (KEV) · Nov 21, 1:33 AM PT: 0 itemsCoincidence (KEV) · Nov 21, 3:11 AM PT: 0 itemsNov 19, 1:20 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, 7:20 PM PTORBIT first saw itNov 19, 7:20 PM PTLatest source updateNov 20, 1:43 AM PTLast checkedNov 21, 4:50 AM PT

Detection gap: 0m 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

  • Open 33h 30m. 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-1f77e2d8c4caddc5/"><img src="https://www.chyp.ai/dissect/event-nw-1f77e2d8c4caddc5/card.svg" alt="Akamai: Reporting Issues · 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.