Wasabi incident

System Errors in AP-NORTHEAST-1

Minor Resolved View vendor source →

Wasabi experienced a minor incident on May 21, 2026 affecting AP-Northeast-1 (Tokyo), lasting 1h 46m. The incident has been resolved; the full update timeline is below.

Started
May 21, 2026, 01:37 AM UTC
Resolved
May 21, 2026, 03:24 AM UTC
Duration
1h 46m
Detected by Pingoru
May 21, 2026, 01:37 AM UTC

Affected components

AP-Northeast-1 (Tokyo)

Update timeline

  1. investigating May 21, 2026, 01:37 AM UTC

    We are currently investigating System errors. Some customers experiencing HTTP 5XX error responses when interacting with their Wasabi buckets is AP-NORTHEAST-1 region.

  2. monitoring May 21, 2026, 02:03 AM UTC

    The issue was identified and team performed the actions to resolve it. We are currently monitoring our systems.

  3. resolved May 21, 2026, 03:24 AM UTC

    Incident resolved.

  4. postmortem May 28, 2026, 12:56 AM UTC

    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.