- Level
- confirmed
- Worst impact
- Partial outage
- Components
- MULTIPLESERVICES
- Regions
- eu-central-1
- Down Index
- 59of 100
What to do
Check whether you use AWS MULTIPLESERVICES in eu-central-1. 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 13m it lasted.
Anything that failed between 2026-07-15 23:11 UTC and 2026-07-16 01:24 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 3
- investigating
We are investigating elevated connectivity issues with a single Avalability zone (euc1-az2) in the EU-CENTRAL-1 Region.
provider
- investigating
We are seeing early signs of recovery and continue to work toward full resolution. We will continue to provide updates.
provider
- investigating
Between 2:56 PM and 6:07 PM PDT, we experienced connectivity issues to a subset of EC2 instances in a single Availability Zone (euc1-az2) in the EU-CENTRAL-1 Region. During this time, customers may also have experienced increased error rates and latencies for new instance launches in the affected zone, along with some AWS APIs that use the affected EC2 instances. Some AWS Services also experienced connectivity issues and increased error rates within the affected zone. Engineers were automatically engaged and immediately began investigating. As part of our recovery effort, we shifted traffic away from the impacted Availability Zone for affected services at 3:04 PM. At 3:05 PM we identified the root cause to be a recent networking change causing the impact. Engineers immediately began reverting this change which completed at 4:28 PM. This resulted in restoration of network connectivity to the affected zone at 4:30 PM. We continued to work until we fully recovered the impacts at 6:07 PM. We do not expect this issue to reoccur. 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-887708b5fd
Is AWS still down?
No, this incident was resolved 2026-07-16 01:24 UTC. For AWS's live state, see https://down.guide/aws.
How long did it last?
2h 13m, from 2026-07-15 23:11 UTC to 2026-07-16 01:24 UTC, by the times AWS posted.
What was affected?
AWS named MULTIPLESERVICES in eu-central-1.
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.