- Level
- confirmed
- Worst impact
- Partial outage
- Components
- AP-Northeast-2 (Osaka)
- Regions
- ap-northeast-2, apac
- Down Index
- 35of 100
What to do
Check whether you use Wasabi AP-Northeast-2 (Osaka) in ap-northeast-2, 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 42m it lasted.
Anything that failed between 2025-04-08 14:41 UTC and 2025-04-08 15:23 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 in our AP-NORTHEAST-2 region. Our team is working to isolate the issue and provide a resolution.
provider
- monitoring
We have identified and resolved the issue. All affected resources are back in service. We are currently monitoring the status. If you see any error, please reach out to support@wasabi.com for assistance.
provider
- resolved
This incident has been resolved.
provider
- postmortem
On 08 April 2025 from 14:13 UTC to approximately 14:39 UTC, Wasabi services in our Osaka \(ap-northeast-2\) region was unavailable due to an internal routing issue which impacted the region's ability to process incoming customer requests. At 14:13 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 ap-northeast-2 region was failing to resolve internal hosts. Wasabi's Operations Team re-deployed the DNS stack and once re-deployment was completed at 14:39 UTC, customer connections to the region was restored.
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-4c88b34e60
Is Wasabi still down?
No, this incident was resolved 2025-04-08 15:23 UTC. For Wasabi's live state, see https://down.guide/wasabi.
How long did it last?
42m, from 2025-04-08 14:41 UTC to 2025-04-08 15:23 UTC, by the times Wasabi posted.
What was affected?
Wasabi named AP-Northeast-2 (Osaka) in ap-northeast-2, 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.