Changes / Wasabi / System Errors in AP-NORTHEAST-2 Region
Wasabi: Major incident: System Errors in AP-NORTHEAST-2 Region
Summary
Summary pending. The diff below shows exactly what changed.
What changed
Before: not present
After: System Errors in AP-NORTHEAST-2 Region
Before: not present
After: major
Before: not present
After: postmortem
Before: not present
After: 2025-04-08 14:41 UTC
Before: not present
After: 2025-04-08 15:23 UTC
Before: not present
After: AP-Northeast-2 (Osaka)
Before: not present
After: We are currently investigating system errors in our AP-NORTHEAST-2 region. Our team is working to isolate the issue and provide a resolution.
Before: not present
After: 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.
Before: not present
After: This incident has been resolved.
Before: not present
After: 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.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: System Errors in AP-NORTHEAST-2 Region (this change) | Major incident |