CHYP.ai · ORBIT // Cloudy_Day Security Suite

OUTAGE DISSECTOR · CASE FILE · NetWeather event

Akamai Cloud (Linode): Service Issue - Block Storage (BR-GRU)

Linode (Akamai Cloud) monitoring M4.1 Squall since Oct 28, 1:18 PM PT

Linode (Akamai Cloud) reported “Akamai Cloud (Linode): Service Issue - Block Storage (BR-GRU)” starting Oct 28, 1:18 PM PT.

  • 23d 16hDurationand counting
  • 3Systems namedfrom the source
  • 1Places named1 on the map
  • 0Dependentscatalogued, inferred
  • 2/4Evidence kindsindependent families
  • 1Updatesofficial revisions

1Scrub the outage

full window
Severityofficial state Oct 30, 2026Nov 3, 2026Nov 7, 2026Nov 11, 2026Nov 16, 2026Nov 20, 2026 Official statusOct 28, 1:17 PM PT · Vendor incident opened: Service Issue - Block Storage (BR-GRU) (none)Nov 19, 3:38 AM PT · Akamai Cloud (Linode): Service Issue - Block Storage (BR-GRU)Nov 20, 12:27 AM PT · Vendor incident opened: Service Issue - Linode Kubernetes Engine (minor)Nov 20, 1:22 AM PT · Official status Operational → Degraded / minor incidentNov 20, 2:40 AM PT · Official status Degraded / minor incident → OperationalNov 20, 10:45 PM PT · Official status Operational → Degraded / minor incidentNov 21, 2:12 AM PT · Official status Degraded / minor incident → OperationalNetwork & routingNov 20, 2:12 AM PT · Akamai Cloud (Linode): Service Issue - Linode Kubernetes EngineEarly signalsnothing in this windowNews & chatternothing in this windowCoincidence (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

Linode (Akamai Cloud) reported “Akamai Cloud (Linode): Service Issue - Block Storage (BR-GRU)” starting Oct 28, 1:18 PM PT.

What broke

US-ORD (Chicago), US-SEA (Seattle), BR-GRU (São Paulo) Block Storage.

Who was hit

Hit: 1 named location (São Paulo (GRU)). No catalogued services depend on Linode (Akamai Cloud).

How it recovered

Still open after 23d 16h.

2Blast radius

Akamai · Degraded / minor incidentAkamaiLinode (Akama…0 dependents

Center: Linode (Akamai Cloud). 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

Chicago (ORD) · monitoring · US-ORD (Chicago), US-SEA (… · same provider, other region: Akamai Cloud (Linode): Service Issue - Linode Kubernetes EngineSão Paulo (GRU) · monitoring · BR-GRU (São Paulo) Block S…
  1. São Paulo (GRU)

Bright: this event. Dim: the same provider's other open events (1). 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 · Oct 28, 7:18 AM PT: 1 itemOfficial status · Oct 29, 7:14 AM PT: 0 itemsOfficial status · Oct 30, 7:10 AM PT: 0 itemsOfficial status · Oct 31, 7:05 AM PT: 0 itemsOfficial status · Nov 1, 6:01 AM PT: 0 itemsOfficial status · Nov 2, 5:57 AM PT: 0 itemsOfficial status · Nov 3, 5:53 AM PT: 0 itemsOfficial status · Nov 4, 5:49 AM PT: 0 itemsOfficial status · Nov 5, 5:44 AM PT: 0 itemsOfficial status · Nov 6, 5:40 AM PT: 0 itemsOfficial status · Nov 7, 5:36 AM PT: 0 itemsOfficial status · Nov 8, 5:32 AM PT: 0 itemsOfficial status · Nov 9, 5:28 AM PT: 0 itemsOfficial status · Nov 10, 5:23 AM PT: 0 itemsOfficial status · Nov 11, 5:19 AM PT: 0 itemsOfficial status · Nov 12, 5:15 AM PT: 0 itemsOfficial status · Nov 13, 5:11 AM PT: 0 itemsOfficial status · Nov 14, 5:07 AM PT: 0 itemsOfficial status · Nov 15, 5:02 AM PT: 0 itemsOfficial status · Nov 16, 4:58 AM PT: 0 itemsOfficial status · Nov 17, 4:54 AM PT: 0 itemsOfficial status · Nov 18, 4:50 AM PT: 1 itemOfficial status · Nov 19, 4:46 AM PT: 3 itemsOfficial status · Nov 20, 4:41 AM PT: 2 itemsNetwork & routingNetwork & routing · Oct 28, 7:18 AM PT: 0 itemsNetwork & routing · Oct 29, 7:14 AM PT: 0 itemsNetwork & routing · Oct 30, 7:10 AM PT: 0 itemsNetwork & routing · Oct 31, 7:05 AM PT: 0 itemsNetwork & routing · Nov 1, 6:01 AM PT: 0 itemsNetwork & routing · Nov 2, 5:57 AM PT: 0 itemsNetwork & routing · Nov 3, 5:53 AM PT: 0 itemsNetwork & routing · Nov 4, 5:49 AM PT: 0 itemsNetwork & routing · Nov 5, 5:44 AM PT: 0 itemsNetwork & routing · Nov 6, 5:40 AM PT: 0 itemsNetwork & routing · Nov 7, 5:36 AM PT: 0 itemsNetwork & routing · Nov 8, 5:32 AM PT: 0 itemsNetwork & routing · Nov 9, 5:28 AM PT: 0 itemsNetwork & routing · Nov 10, 5:23 AM PT: 0 itemsNetwork & routing · Nov 11, 5:19 AM PT: 0 itemsNetwork & routing · Nov 12, 5:15 AM PT: 0 itemsNetwork & routing · Nov 13, 5:11 AM PT: 0 itemsNetwork & routing · Nov 14, 5:07 AM PT: 0 itemsNetwork & routing · Nov 15, 5:02 AM PT: 0 itemsNetwork & routing · Nov 16, 4:58 AM PT: 0 itemsNetwork & routing · Nov 17, 4:54 AM PT: 0 itemsNetwork & routing · Nov 18, 4:50 AM PT: 0 itemsNetwork & routing · Nov 19, 4:46 AM PT: 1 itemNetwork & routing · Nov 20, 4:41 AM PT: 0 itemsEarly signalsEarly signals · Oct 28, 7:18 AM PT: 0 itemsEarly signals · Oct 29, 7:14 AM PT: 0 itemsEarly signals · Oct 30, 7:10 AM PT: 0 itemsEarly signals · Oct 31, 7:05 AM PT: 0 itemsEarly signals · Nov 1, 6:01 AM PT: 0 itemsEarly signals · Nov 2, 5:57 AM PT: 0 itemsEarly signals · Nov 3, 5:53 AM PT: 0 itemsEarly signals · Nov 4, 5:49 AM PT: 0 itemsEarly signals · Nov 5, 5:44 AM PT: 0 itemsEarly signals · Nov 6, 5:40 AM PT: 0 itemsEarly signals · Nov 7, 5:36 AM PT: 0 itemsEarly signals · Nov 8, 5:32 AM PT: 0 itemsEarly signals · Nov 9, 5:28 AM PT: 0 itemsEarly signals · Nov 10, 5:23 AM PT: 0 itemsEarly signals · Nov 11, 5:19 AM PT: 0 itemsEarly signals · Nov 12, 5:15 AM PT: 0 itemsEarly signals · Nov 13, 5:11 AM PT: 0 itemsEarly signals · Nov 14, 5:07 AM PT: 0 itemsEarly signals · Nov 15, 5:02 AM PT: 0 itemsEarly signals · Nov 16, 4:58 AM PT: 0 itemsEarly signals · Nov 17, 4:54 AM PT: 0 itemsEarly signals · Nov 18, 4:50 AM PT: 0 itemsEarly signals · Nov 19, 4:46 AM PT: 0 itemsEarly signals · Nov 20, 4:41 AM PT: 0 itemsNews & chatterNews & chatter · Oct 28, 7:18 AM PT: 0 itemsNews & chatter · Oct 29, 7:14 AM PT: 0 itemsNews & chatter · Oct 30, 7:10 AM PT: 0 itemsNews & chatter · Oct 31, 7:05 AM PT: 0 itemsNews & chatter · Nov 1, 6:01 AM PT: 0 itemsNews & chatter · Nov 2, 5:57 AM PT: 0 itemsNews & chatter · Nov 3, 5:53 AM PT: 0 itemsNews & chatter · Nov 4, 5:49 AM PT: 0 itemsNews & chatter · Nov 5, 5:44 AM PT: 0 itemsNews & chatter · Nov 6, 5:40 AM PT: 0 itemsNews & chatter · Nov 7, 5:36 AM PT: 0 itemsNews & chatter · Nov 8, 5:32 AM PT: 0 itemsNews & chatter · Nov 9, 5:28 AM PT: 0 itemsNews & chatter · Nov 10, 5:23 AM PT: 0 itemsNews & chatter · Nov 11, 5:19 AM PT: 0 itemsNews & chatter · Nov 12, 5:15 AM PT: 0 itemsNews & chatter · Nov 13, 5:11 AM PT: 0 itemsNews & chatter · Nov 14, 5:07 AM PT: 0 itemsNews & chatter · Nov 15, 5:02 AM PT: 0 itemsNews & chatter · Nov 16, 4:58 AM PT: 0 itemsNews & chatter · Nov 17, 4:54 AM PT: 0 itemsNews & chatter · Nov 18, 4:50 AM PT: 0 itemsNews & chatter · Nov 19, 4:46 AM PT: 0 itemsNews & chatter · Nov 20, 4:41 AM PT: 0 itemsCoincidence (KEV)Coincidence (KEV) · Oct 28, 7:18 AM PT: 0 itemsCoincidence (KEV) · Oct 29, 7:14 AM PT: 0 itemsCoincidence (KEV) · Oct 30, 7:10 AM PT: 0 itemsCoincidence (KEV) · Oct 31, 7:05 AM PT: 0 itemsCoincidence (KEV) · Nov 1, 6:01 AM PT: 0 itemsCoincidence (KEV) · Nov 2, 5:57 AM PT: 0 itemsCoincidence (KEV) · Nov 3, 5:53 AM PT: 0 itemsCoincidence (KEV) · Nov 4, 5:49 AM PT: 0 itemsCoincidence (KEV) · Nov 5, 5:44 AM PT: 0 itemsCoincidence (KEV) · Nov 6, 5:40 AM PT: 0 itemsCoincidence (KEV) · Nov 7, 5:36 AM PT: 0 itemsCoincidence (KEV) · Nov 8, 5:32 AM PT: 0 itemsCoincidence (KEV) · Nov 9, 5:28 AM PT: 0 itemsCoincidence (KEV) · Nov 10, 5:23 AM PT: 0 itemsCoincidence (KEV) · Nov 11, 5:19 AM PT: 0 itemsCoincidence (KEV) · Nov 12, 5:15 AM PT: 0 itemsCoincidence (KEV) · Nov 13, 5:11 AM PT: 0 itemsCoincidence (KEV) · Nov 14, 5:07 AM PT: 0 itemsCoincidence (KEV) · Nov 15, 5:02 AM PT: 0 itemsCoincidence (KEV) · Nov 16, 4:58 AM PT: 0 itemsCoincidence (KEV) · Nov 17, 4:54 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 4:50 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 4:46 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 4:41 AM PT: 0 itemsOct 28, 7:18 AM 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 beganOct 28, 1:18 PM PTORBIT first saw itNov 19, 3:38 AM PTLatest source updateOct 28, 1:18 PM PTLast checkedNov 21, 4:36 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 23d 16h. 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.

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 Linode (Akamai Cloud).

8Dissection capsule

Share card for this dissection

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

JSON capsuleMarkdownShare card (SVG)

Open Linode (Akamai Cloud) in the War Room →NetWeather evidence page →Status page →

Embed this card
<a href="https://www.chyp.ai/dissect/event-nw-9c546dbf2c35c57e/"><img src="https://www.chyp.ai/dissect/event-nw-9c546dbf2c35c57e/card.svg" alt="Akamai Cloud (Linode): Service Issue - Block Storage (BR-GR… · 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.
  • 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.