Wasabi: System Errors in EU-WEST-3 Region

What to do

Check whether you use Wasabi in eu, eu-west-3. 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 0m it lasted.
Anything that failed between 2025-04-11 15:16 UTC and 2025-04-08 20:00 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.

resolvedApr 8, 2025, 8:00 PM UTC
On 08 April 2025 from 20:05 UTC to approximately 20:16 UTC, Wasabi services in our London (eu-west-3) region was unavailable due to an internal routing issue which impacted the region's ability to process incoming customer requests. At 20:05 UTC, our Operations Team was notified by our internal monitoring service that customer traffic was being impacted within the region. Upon investigation, it was found that internal DNS routing within the eu-west-3 region was failing to resolve internal hosts. Wasabi's Operations Team re-deployed the DNS stack and once re-deployment was completed at 20:16 UTC, customer connections to the region was restored.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

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

Is Wasabi still down?

No, this incident was resolved 2025-04-08 20:00 UTC. For Wasabi's live state, see https://down.guide/wasabi.

How long did it last?

0m, from 2025-04-11 15:16 UTC to 2025-04-08 20:00 UTC, by the times Wasabi posted.

What was affected?

Wasabi named in eu, eu-west-3.

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.