Skip to main content
Wasabi

System Errors affecting some Wasabi Regions

Degraded Lasted 2h 38m · started · Wasabi's page

Level
confirmed
Worst impact
Degraded
Components
US-East-1 (N. Virginia), US-East-2 (N. Virginia), EU-Central-1 (Amsterdam), EU-Central-2 (Frankfurt)
Regions
eu, eu-central-1, eu-central-2, us, us-east-1, us-east-2

What to do

  • Check whether you use Wasabi US-East-1 (N. Virginia), US-East-2 (N. Virginia), EU-Central-1 (Amsterdam), EU-Central-2 (Frankfurt) in eu, eu-central-1, eu-central-2, us. 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 38m it lasted.

    Anything that failed between 2024-12-05 21:11 UTC and 2024-12-05 23:49 UTC may need a replay.
  • Subscribe to Wasabi's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=wasabi works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Wasabi 3

  1. investigating

    We are currently investigating an increase in "Account Connection Limited" responses from the S3 system on a number of Wasabi Storage Regions. We will update this page as we have more information.

    provider

  2. monitoring

    We have isolated the issue "Account Connection Limited" errors and engineering has made changes to restore the service. We will update this page with any further information.

    provider

  3. resolved

    After monitoring, we have confirmed the issue is resolved and there is no further impact on our services.

    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-00d4eb00ae

Is Wasabi still down?

No, this incident was resolved 2024-12-05 23:49 UTC. For Wasabi's live state, see https://down.guide/wasabi.

How long did it last?

2h 38m, from 2024-12-05 21:11 UTC to 2024-12-05 23:49 UTC, by the times Wasabi posted.

What was affected?

Wasabi named US-East-1 (N. Virginia), US-East-2 (N. Virginia), EU-Central-1 (Amsterdam), EU-Central-2 (Frankfurt) in eu, eu-central-1, eu-central-2, us.

What caused it?

Wasabi hasn't published a root cause. If it does, it shows here.

Where does this come from?

Wasabi's official status page, https://status.wasabi.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.