- Level
- confirmed
- Worst impact
- Degraded
- Components
- INTERNETCONNECTIVITY
- Regions
- eu-south-2
- Down Index
- 50of 100
What to do
Check whether you use AWS INTERNETCONNECTIVITY in eu-south-2. 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 2h 42m it lasted.
Anything that failed between 2026-10-04 16:14 UTC and 2026-10-04 18:56 UTC may need a replay.Subscribe to AWS's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=aws works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from AWS 6
- investigating
We are investigating elevated packet loss in the EU-SOUTH-2 Region.
provider
- investigating
We are experiencing elevated packet loss with a single Availability Zone (eus2-az1) in the EU-SOUTH-2 Region. This issue is also resulting in elevated API latencies and error rates for other workflows and AWS Services. Engineers were automatically engaged and are working to identify the root cause and to mitigate the issue. We will provide you with another update by 10:15 AM PDT or sooner as new information becomes available.
provider
- investigating
Our efforts to mitigate the elevated packet loss with a single Availability Zone (eus2-az1) in the EU-SOUTH-2 Region is still underway. We are seeing some signs of improvement as a result of multiple parallel efforts. We continue to work to confirm root cause and fully mitigate the issue. While we currently do not have an estimate for how long our actions will take, we will keep you informed of our progress and provide you with another update by 11:00 AM PDT or sooner as new information becomes available.
provider
- investigating
We have identified the root cause and are currently focusing our mitigation efforts to drive full recovery. While we don't have an exact estimate for how long our current efforts will take, we do expect to see incremental improvements as our efforts proceed. We will provide you with another update by 11:45 AM PDT, or sooner if new information becomes available.
provider
- investigating
We are seeing early signs of recovery. We will provide you with another update by 12:00 PM PDT.
provider
- investigating
Between 8:48 AM and 11:28 AM PDT, we experienced elevated packet loss within a single Availability Zone (eus2-az1) in the EU-SOUTH-2 Region. This issue resulted in elevated API latencies and error rates for multiple workflows and AWS Services. We were automatically alerted to the issue at 8:54 AM, and immediately began work to identify the root cause while taking multiple parallel paths to mitigate the issue. By 10:00 AM, our mitigation efforts had led to some improvements. By 10:38 AM, we identified the root cause as related to a networking configuration change that we were able to revert the change which led to full mitigation by 11:28 AM. The issue has been resolved and the service is operating normally.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-ead02183fb
Is AWS still down?
No, this incident was resolved 2026-10-04 18:56 UTC. For AWS's live state, see https://down.guide/aws.
How long did it last?
2h 42m, from 2026-10-04 16:14 UTC to 2026-10-04 18:56 UTC, by the times AWS posted.
What was affected?
AWS named INTERNETCONNECTIVITY in eu-south-2.
What caused it?
AWS hasn't published a root cause. If it does, it shows here.
Where does this come from?
AWS's official status page, https://health.aws.amazon.com/health/status, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.