# Service Issue - Linode Kubernetes Engine · ORBIT Outage Dissector

- Provider: Linode (Akamai Cloud) · state: monitoring · duration: 28h 35m
- CHYP Magnitude: **M3.0 Squall** (severity 0.45, breadth 0, duration 0.81, reach 0, corroboration 0.5)
- Content SHA-256: 750c81d24270bf5502f435c627dd5f4514a0d49c070f86776b664a27df20a46e

## Story

- **What happened:** Linode (Akamai Cloud) reported “Service Issue - Linode Kubernetes Engine” starting Nov 20, 12:27 AM PT.
- **What broke:** US-ORD (Chicago), US-SEA (Seattle), BR-GRU (São Paulo) Block Storage.
- **Who was hit:** Hit: location not stated. No catalogued services depend on Linode (Akamai Cloud).
- **How it recovered:** Still open after 28h 35m, easing: 0 of a peak 2 state remain.

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


## Timeline (PT)

### Official status
- Oct 28, 1:17 PM PT · Also open: Service Issue - Block Storage (BR-GRU) (https://www.chyp.ai/dissect/vi/linode~d5ksyyk5x9w5/)
- Nov 20, 12:27 AM PT · Incident opened: Service Issue - Linode Kubernetes Engine
- Nov 20, 1:22 AM PT · Official status Operational → Degraded / minor incident
- Nov 20, 2:40 AM PT · Official status Degraded / minor incident → Operational
- Nov 20, 10:45 PM PT · Official status Operational → Degraded / minor incident
- Nov 21, 2:12 AM PT · Official status Degraded / minor incident → Operational

### Network & routing
- Nov 20, 2:12 AM PT · Akamai Cloud (Linode): Service Issue - Linode Kubernetes Engine (https://www.chyp.ai/dissect/event-nw-7b708845b74af6fb/)

### Early signals

### News

### 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 28h 35m. 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.

## Sources

- Linode (Akamai Cloud) official status page: https://stspg.io/z5hhd4vz7jfv

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

> Cite: ORBIT by Cloudy_Day, Outage Dissector, https://www.chyp.ai/dissect/vi/linode~hgq6wzfbdr71/
> 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.
