- Level
- confirmed
- Worst impact
- Degraded
- Components
- AP-Northeast-1 (Tokyo)
- Regions
- ap-northeast-1, apac
- Down Index
- 27of 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 1h 47m it lasted.
Anything that failed between 2026-05-21 01:37 UTC and 2026-05-21 03:24 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 4
- investigating
We are currently investigating System errors. Some customers experiencing HTTP 5XX error responses when interacting with their Wasabi buckets in AP-NORTHEAST-1 region.
provider
- monitoring
The issue was identified and team performed the actions to resolve it. We are currently monitoring our systems.
provider
- resolved
Incident resolved.
provider
- postmortem
Between 2026-05-20 17:57 UTC and 2026-05-21 01:44 UTC, a subset of customers operating in the AP-NORTHEAST-1 region experienced intermittent HTTP 5xx errors impacting object storage operations. The issue was triggered by failures on a portion of the underlying storage hosts, resulting in temporary service instability within the region. The host failures occurred under elevated internal system activity associated with platform health-management operations and concurrent storage reclamation workflows. Service impact was intermittent throughout the event window. Wasabi has implemented additional operational safeguards and recovery workflows to accelerate remediation of impacted internal nodes. These enhancements improve recovery efficiency across high-availability infrastructure and further reduce the risk and duration of future service-impacting events.
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-fc45b87d36
Is Wasabi still down?
No, this incident was resolved 2026-05-21 03:24 UTC. For Wasabi's live state, see https://down.guide/wasabi.
How long did it last?
1h 47m, from 2026-05-21 01:37 UTC to 2026-05-21 03:24 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.