Amazon Marketplace Web Service incident

AWS Direct Connect — Mumbai: [RESOLVED] Elevated Packet Loss

Resolved after 1 day 1 hour, affecting AWS Direct Connect — ap-south-1, on July 31, 2026.

monitoring Jul 31, 2026, 06:54 PM UTC

Between 9:42 AM and 11:44 AM PDT, we experienced elevated network packet loss impacting AWS Direct Connect connectivity in the AP-SOUTH-1 Region. Our engineering team was automatically engaged at 9:46 AM to begin investigating. By 10:51 AM, we understood the root cause to be a configuration change made to a system responsible for assigning routes to devices. As we gained confidence in our mitigation steps, we parallelized our efforts to further reduce the packet loss. The issue is resolved and the service is operating normally.

Started
Jul 31, 2026, 05:33 PM UTC
Resolved
Aug 01, 2026, 06:44 PM UTC
Duration
1d 1h
Detected by Pingoru
Jul 31, 2026, 05:33 PM UTC

Affected components

AWS Direct Connect — ap-south-1

Update timeline

  1. monitoring Jul 31, 2026, 05:33 PM UTC

    We can confirm elevated network packet loss, impacting AWS Direct Connect connectivity in AP-SOUTH-1 Region. Our engineering team was automatically engaged at 9:54 AM to begin investigating the issue. There are no workarounds available at this time. We will provide another update by 11:30 AM PDT.

  2. monitoring Jul 31, 2026, 06:27 PM UTC

    We have identified the root cause to be related to a change made to a configuration system responsible for assigning routes to the devices. We have begun the work to reduce the packet loss that is impacting AWS Direct Connect in the AP-SOUTH-1 Region, and we expect recovery to take place gradually over the next 30 minutes. As we gain confidence in these efforts, we will seek to parallelize our efforts to speed recovery. We will provide another update by 12:00 PM PDT.

  3. monitoring Jul 31, 2026, 06:54 PM UTC

    Between 9:42 AM and 11:44 AM PDT, we experienced elevated network packet loss impacting AWS Direct Connect connectivity in the AP-SOUTH-1 Region. Our engineering team was automatically engaged at 9:46 AM to begin investigating. By 10:51 AM, we understood the root cause to be a configuration change made to a system responsible for assigning routes to devices. As we gained confidence in our mitigation steps, we parallelized our efforts to further reduce the packet loss. The issue is resolved and the service is operating normally.

Your product runs on more than Amazon Marketplace Web Service

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →