Vendor reports: operationalResolved · vendor status “postmortem”Official status API

Upstream Loss - Some Paths (in-maa/in-bom-2 to US Region)

Reported by Linode (Akamai) · Cloud & Infrastructure · source last read just now

Official source (opens in a new tab)
Vendor start
Jul 31, 2026, 17:49 UTC
Vendor's clock
Resolved
Aug 5, 2026, 01:34 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
4 d 7 h
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Linode (Akamai) reports operational: "Upstream Loss - Some Paths (in-maa/in-bom-2 to US Region)".[E1, E2]
  • The vendor marked it resolved at 2026-08-05 01:34 UTC.[E3, E7]

Affected products and regions

  • Components: US-East (Newark), US-Central (Dallas), US-West (Fremont), US-Southeast (Atlanta), US-IAD (Washington), US-ORD (Chicago), US-SEA (Seattle), IN-MAA (Chennai), US-MIA (Miami), US-LAX (Los Angeles), IN-BOM-2 (Mumbai 2), US-DEN (Denver), US-HOU (Houston), US-IAD-2 (Washington 2).[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-08-05 01:34 UTC · summary s1, evidence 89e813f2f79273f9

Evidence (7)
  1. E1Linode (Akamai) reports operational. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Upstream Loss - Some Paths (in-maa/in-bom-2 to US Region)". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "postmortem". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-07-31 17:49 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: US-East (Newark), US-Central (Dallas), US-West (Fremont), US-Southeast (Atlanta), US-IAD (Washington), US-ORD (Chicago), US-SEA (Seattle), IN-MAA (Chennai), US-MIA (Miami), US-LAX (Los Angeles), IN-BOM-2 (Mumbai 2), US-DEN (Denver), US-HOU (Houston), US-IAD-2 (Washington 2). (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-08-05 01:34 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: US-East (Newark), US-Central (Dallas), US-West (Fremont), US-Southeast (Atlanta), US-IAD (Washington), US-ORD (Chicago), US-SEA (Seattle), IN-MAA (Chennai), US-MIA (Miami), US-LAX (Los Angeles), IN-BOM-2 (Mumbai 2), US-DEN (Denver), US-HOU (Houston), US-IAD-2 (Washington 2)

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Linode (Akamai) is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Jul 31, 2026, 17:49 UTCVendor-reported startVendor time
  2. Aug 5, 2026, 01:34 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.