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

What to do

• Check whether you use Akamai Cloud (Linode) US-East (Newark), US-Central (Dallas), US-West (Fremont), US-Southeast (Atlanta) and 10 more in apac, in, us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 4d 7h it lasted.

  Anything that failed between 2026-07-31 17:49 UTC and 2026-08-05 01:34 UTC may need a replay.

• Subscribe to Akamai Cloud (Linode)'s feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=linode works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Akamai Cloud (Linode) 5

1. investigatingJul 31, 2026, 5:49 PM UTC

   Our team is investigating packet loss on some paths from the in-maa & in-bom-2 data centers into the US region. During this time, users may experience connection timeouts and errors with services traversing between India and United States regions. We will share additional updates as we have more information.

   provider

2. identifiedJul 31, 2026, 6:25 PM UTC

   Our team has identified the cause of packet loss to our US data centers. We are working with our upstream provider to resolve this issue and we will provide an update as soon as the solution is in place.

   provider

3. identifiedAug 4, 2026, 6:36 PM UTC

   We are continuing to work with our upstream provider to resolve the packet loss affecting some paths between the in-maa and in-bom-2 data centers and the US region. We will share further updates as progress continues.

   provider

4. resolvedAug 5, 2026, 1:34 AM UTC

   At this time the upstream provider has been able to correct the issue causing packet loss on some routes from the in-maa & in-bom-2 data centers into the US region and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

   provider

5. postmortemAug 5, 2026, 5:49 PM UTC

   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 congestion between two alternative upstream providers, impacting some users. One provider acknowledged a bottleneck in the Asia region, and the alternate provider worked to reroute traffic away from affected links.  The initial impacted service provider confirmed that two fiber cuts in Mexico caused congestion on the impacted routes. One of these fiber cuts was resolved at 23:43 UTC on July 31, 2026, and no further issues were observed following this mitigation.  This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.