- Level
- confirmed
- Worst impact
- Degraded
- Components
- AP-Northeast-1 (Tokyo)
- Regions
- ap-northeast-1, apac
- Down Index
- 28of 100
What to do
Check whether you use Wasabi AP-Northeast-1 (Tokyo) in ap-northeast-1, apac. 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 3h 20m it lasted.
Anything that failed between 2025-05-21 09:47 UTC and 2025-05-21 13:07 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 5
- investigating
We are currently experiencing system errors in our AP-NORTHEAST-1 region. Customers may experience elevated HTTP 5XX error responses when interacting with their Wasabi bucket(s)/objects. We will update this page as we have more information.
provider
- identified
The issue has been identified and we are working towards to a solution.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved, please contact support@wasabi.com with any outstanding questions.
provider
- postmortem
On 21 May 2025 at 02:45 UTC, Wasabi’s Tokyo vault was impacted by system errors, causing client requests to result in 5xx errors for any API calls to their S3 buckets. This issue was due to an internal failure in the Tokyo Region where the backend server had a hardware fault, impacting the cluster of which it was a member. Our Operations Team identified the failure and took corrective action by performing a cluster failover to resolve the issue, which returned the service back to an operational state at 10:55 UTC 21 May 2025.
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-778e939879
Is Wasabi still down?
No, this incident was resolved 2025-05-21 13:07 UTC. For Wasabi's live state, see https://down.guide/wasabi.
How long did it last?
3h 20m, from 2025-05-21 09:47 UTC to 2025-05-21 13:07 UTC, by the times Wasabi posted.
What was affected?
Wasabi named AP-Northeast-1 (Tokyo) in ap-northeast-1, apac.
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.