Skip to content
AWS · Cloud and hostingJul 31, 2026, 17:33 UTC

Elevated Packet Loss

MinorConfig changeUpdated 17h ago
Jul 31, 17:33 UTCJul 31, 18:54 UTC
Duration
1h 21m
Impact
Minor
Root cause
Config change
AWS, 90 days
12 incidents
Affected
Directconnectap-south-1
Status page

Final update

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.

Timeline

  1. Resolved · Jul 31, 18:54 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.
  2. Update · Jul 31, 18:27 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. Update · Jul 31, 17:33 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.

More from AWS

Full history
StartedIncidentDuration
Sep 2123:26 UTCIncreased Error Rates58m
Sep 321:49 UTCIncreased API Error Rates2h 18m
Aug 2102:02 UTCIncreased Error Rates38m
Aug 1915:15 UTCIncreased Error Rates3h 32m
Aug 1503:42 UTCIncreased Packet loss3d
Jul 2411:40 UTCConnectivity Issues1h 21m

Also caused by configuration change

All
StartedIncidentDuration
Sep 2218:20 UTCPhone Number APIs and Console Were Returning Incorrect 404 ResponsesTwilio0m
Sep 1622:30 UTCHyperdrive Elevated Origin Connection Failure RatesCloudflare0m
Sep 1211:04 UTCSome customers experiencing blurry image previews and download issuesSlack8h 56m
Sep 1107:18 UTCINC20000213Snowflake6h 1m
Sep 407:34 UTCINC20000199Snowflake2h 36m
Sep 109:58 UTCINC20000190Snowflake3h 52m

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.