# Akamai: Reporting Issues · ORBIT Outage Dissector

- Provider: Akamai · state: monitoring · duration: 33h 43m
- CHYP Magnitude: **M4.3 Squall** (severity 0.45, breadth 0.3, duration 0.83, reach 0.14, corroboration 0.75)
- Content SHA-256: 45ed090531aa3a08b7a55ff4e7ef8b217152c638b82760f0ae5f667092824306

## Story

- **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 43m, at or near its peak (1 state).

## Failure-mode fingerprint (automated keyword read (hypothesis, not root cause))


## Timeline (PT)

### Official status
- Nov 19, 7:20 PM PT · Vendor incident opened: Reporting Issues (minor) (https://www.chyp.ai/dissect/vi/akamai~bjf3f254x3rd/)
- Nov 19, 7:20 PM PT · Akamai: Reporting Issues
- Nov 19, 8:20 PM PT · Akamai: Reporting Issues
- Nov 20, 1:44 AM PT · Akamai: Reporting Issues

### Network & routing
- Nov 20, 2:12 AM PT · Akamai Cloud (Linode): Service Issue - Linode Kubernetes Engine (https://www.chyp.ai/dissect/event-nw-7b708845b74af6fb/)
- Nov 19, 7:20 PM PT · Akamai: 1 component degraded performance (https://www.chyp.ai/dissect/event-nw-0957faf58fbd16d2/)
- Nov 21, 1:00 AM PT · AS20940 (Akamai) BGP update churn -1.1σ vs 24h (https://www.chyp.ai/incident/event-nw-a9376ea4aaba5459)

### Early signals

### News
- Nov 19, 7:20 PM PT · Reporting Issues (https://www.akamaistatus.com/incidents/bjf3f254x3rd)

### Coincidence (KEV)

## Historical twins

- 20% · Amazon Web Services 2025-10-19: DynamoDB DNS automation wrote an empty record it could not repair (14h 32m overall (three distinct impact periods)) https://www.chyp.ai/dissect/m/aws-dynamodb-2025-10-19/
- 20% · Microsoft Azure 2024-09-27: ARM control plane blocked by a global Cosmos DB misconfiguration (1h 38m) https://www.chyp.ai/dissect/m/azure-arm-gov-2024-09-27/
- 20% · Amazon Web Services 2024-07-30: Kinesis cell-management misidentified healthy hosts during a deployment (6h 52m) https://www.chyp.ai/dissect/m/aws-kinesis-2024-07-30/

## Cloudy_Day take (automated)

- Open 33h 43m. 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.

## Sources

- Akamai official status page: https://stspg.io/h7t3df7yqy78
- NetWeather evidence page: https://www.chyp.ai/incident/event-nw-1f77e2d8c4caddc5

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

> Cite: ORBIT by Cloudy_Day, Outage Dissector, https://www.chyp.ai/dissect/event-nw-1f77e2d8c4caddc5/
> Automated data from ORBIT (Cloudy_Day Security Suite). Independent research, not affiliated with any government agency, vendor or data provider. Not an official status source.
