- Level
- confirmed
- Worst impact
- Degraded
- Components
- US-Central-1 (Texas), US-East-1 (N. Virginia), US-East-2 (N. Virginia), US-West-1 (Oregon), EU-Central-1 (Amsterdam), EU-Central-2 (Frankfurt), EU-West-2 (Paris), AP-Northeast-1 (Tokyo), AP-Northeast-2 (Osaka), Wasabi Management Console
- Regions
- ap-northeast-1, ap-northeast-2, apac, eu, eu-central-1, eu-central-2, eu-west-1, eu-west-2, us, us-central-1, us-east-1, us-east-2, us-west-1
- Down Index
- 28of 100
What to do
Check whether you use Wasabi US-Central-1 (Texas), US-East-1 (N. Virginia), US-East-2 (N. Virginia), US-West-1 (Oregon) and 6 more in ap-northeast-1, ap-northeast-2, apac, eu. 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-03-27 22:09 UTC and 2025-03-27 22:09 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 2
- resolved
Between 10:09PM to 10:14PM UTC, we experienced errors with connecting to the Wasabi Web Console, STS, and IAM services. It was a temporary issue, auto-resolved and Operations Team validated it. There is no longer any further impact, and all services are now running without issue.
provider
- postmortem
On 27 March 2025 from 10:09 UTC to approximately 10:14 UTC, Wasabi services in our Ashburn \(us-east-1\), Manassas \(us-east-2\), Hillsboro \(us-west-1\), Plano \(us-central-1\), Amsterdam \(eu-central-1\), Tokyo \(ap-northeast-1\), Osaka \(ap-northeast-2\), London \(eu-west-1\), and Frankfurt \(eu-central-2\) regions were unavailable due to an issue, impacting customer traffic and Web Console connectivity. Wasabi Engineering and Operations teams were notified by our automated monitoring systems of an issue with a spike in connection between internal service worker nodes. This spike led to the inability to open new connections within the services. Wasabi’s Operations Team manually restarted the services, which corrected the issue and allowed for client connections to resume successfully. By 10:14 UTC, all internal services were restarted and all services returned to normal operating conditions.
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-f1ed3ee4b9
Is Wasabi still down?
No, this incident was resolved 2025-03-27 22:09 UTC. For Wasabi's live state, see https://down.guide/wasabi.
How long did it last?
0m, from 2025-03-27 22:09 UTC to 2025-03-27 22:09 UTC, by the times Wasabi posted.
What was affected?
Wasabi named US-Central-1 (Texas), US-East-1 (N. Virginia), US-East-2 (N. Virginia), US-West-1 (Oregon) and 6 more in ap-northeast-1, ap-northeast-2, apac, eu.
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.