Linode (Akamai) outage, 31 July 2026
Upstream Loss - Some Paths (in-maa/in-bom-2 to US Region)
- Started
- Resolved
- 5 Aug 2026, 01:34 UTC (after 4 days)
- Impact
- Not stated
- Affected
- 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)
Last update from Linode (Akamai)
On July 31, 2026, at approximately 10:00 UTC, Akamai observed intermittent network losses affecting compute users accessing US locations from our India sites \(MAA and BOM\). Customers’ services in North America, particularly the Miami data center region, experienced increased latency, intermittent connectivity issues, slower data transfers, and difficulty reaching certain applications or services. Performance was unstable, with periods of normal operation followed by disruptions. To address the issue, Akamai applied a deny-all policy to the impacted upstream provider transit link, redirecting traffic around the impacted routes. Despite this mitigation, ongoing IPv6 losses occurred due to...
Read the full incident on the official Linode (Akamai) status page
Is Linode (Akamai) down now?
This page is the record of one past incident. For the live status, see Is Linode (Akamai) down right now? - it reads the official status page every 2 minutes.