GlobalOutageMap
← Live dashboard
Linode logoLinode

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

ResolvedminorOfficial source confirmedMulti-region impactFirst recorded update Jul 31, 2026, 05:49 PM · Resolved Aug 5, 2026, 01:34 AM

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

Linode live status →

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with Linode now? Check the current status

Affected services

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

Updates (5)

  1. Aug 5, 2026, 05:49 PM
    Upstream Loss - Some Paths (in-maa/in-bom-2 to US Region)

    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, redirecti

    Linode ↗
  2. Aug 5, 2026, 01:34 AM
    Upstream Loss - Some Paths (in-maa/in-bom-2 to US Region)

    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 <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.

    Linode ↗
  3. Aug 4, 2026, 06:36 PM
    Upstream Loss - Some Paths (in-maa/in-bom-2 to US Region)

    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.

    Linode ↗
  4. Jul 31, 2026, 06:25 PM
    Upstream Loss - Some Paths (in-maa/in-bom-2 to US Region)

    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.

    Linode ↗
  5. Jul 31, 2026, 05:49 PM
    Upstream Loss - Some Paths (in-maa/in-bom-2 to US Region)

    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.

    Linode ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow Linode's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.