S3 (eu-central-2): Increased Error Rates

What to do

• Check whether you use AWS S3 in eu-central-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 1h 11m it lasted.

  Anything that failed between 2026-03-07 19:53 UTC and 2026-03-07 21:04 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 4

1. investigatingMar 7, 2026, 7:53 PM UTC

   We are investigating increased error rates in the EU-CENTRAL-2 Region.

   provider

2. investigatingMar 7, 2026, 8:17 PM UTC

   We can confirm substantial error rates for PUT and GET requests to Amazon S3 in the EU-CENTRAL-2 Region. Engineers engaged immediately based on automated alarming. We have triangulated the issue to a subsystem responsible for assembling objects from bytes in storage. We have begun implementing mitigations, and are observing some improvement in error rates. We continue to work to identify the root cause, and are working on multiple parallel paths to fully mitigate the issue. Other AWS Services (such as EC2 launches) that rely on S3 are also affected by this issue. Existing EC2 instances are unaffected by this issue. We will provide another update by 12:45 PM PST, or sooner if we have additional information to share.

   provider

3. investigatingMar 7, 2026, 8:28 PM UTC

   We are seeing early signs of recovery and continue to monitor and work toward full recovery.

   provider

4. investigatingMar 7, 2026, 9:04 PM UTC

   Between 11:27 AM and 12:20 PM PST we experienced substantial error rates for S3 PUT/GET requests in EU-CENTRAL-2 Region. Engineers were engaged immediately based on automated alarming. We identified the root cause as an issue with a subsystem responsible for assembling objects bytes in storage. At 12:04 PM PST, we implemented mitigations and began observing early signs of recovery for S3. Error rates continued to improve, and other AWS Services continued to recover until 12:50 PM PST when we observed full recovery. We continue to work toward backfilling Cloudwatch logs, and expect that to continue over the next couple hours. We recommend customers retry any failed requests. The issue has been resolved and all services are operating normally.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.