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

Incident Report for Linode

Resolved

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.
Posted Aug 05, 2026 - 01:34 UTC

Update

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.
Posted Aug 04, 2026 - 18:36 UTC

Identified

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.
Posted Jul 31, 2026 - 18:25 UTC

Investigating

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.
Posted Jul 31, 2026 - 17:49 UTC
This incident affected: Regions (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)).