Wasabi incident

System Errors in AP-NORTHEAST-2 Region

Major Resolved View vendor source →

Wasabi experienced a major incident on April 8, 2025 affecting AP-Northeast-2 (Osaka), lasting 42m. The incident has been resolved; the full update timeline is below.

Started
Apr 08, 2025, 02:41 PM UTC
Resolved
Apr 08, 2025, 03:23 PM UTC
Duration
42m
Detected by Pingoru
Apr 08, 2025, 02:41 PM UTC

Affected components

AP-Northeast-2 (Osaka)

Update timeline

  1. investigating Apr 08, 2025, 02:41 PM UTC

    We are currently investigating system errors in our AP-NORTHEAST-2 region. Our team is working to isolate the issue and provide a resolution.

  2. monitoring Apr 08, 2025, 02:45 PM UTC

    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 [email protected] for assistance.

  3. resolved Apr 08, 2025, 03:23 PM UTC

    This incident has been resolved.

  4. postmortem Apr 11, 2025, 03:05 PM UTC

    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.