- Level
- confirmed
- Worst impact
- Degraded
- Regions
- ap-northeast-1
- Down Index
- 12of 100
What to do
Check whether you use Wasabi in ap-northeast-1. 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 2026-06-25 01:15 UTC and 2026-06-25 01:15 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 1
- resolved
Between 01:10 UTC and 02:15 UTC on June 25th, some customers may have experienced elevated HTTP 5XX error responses when accessing buckets in the AP-NORTHEAST-1 region. The issue has been resolved. It was caused by a transient issue affecting Wasabi backend components, which was automatically detected by our monitoring systems and promptly remediated by our engineering team.
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-ba2465a126
Is Wasabi still down?
No, this incident was resolved 2026-06-25 01:15 UTC. For Wasabi's live state, see https://down.guide/wasabi.
How long did it last?
0m, from 2026-06-25 01:15 UTC to 2026-06-25 01:15 UTC, by the times Wasabi posted.
What was affected?
Wasabi named in ap-northeast-1.
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.