Companies/Wasabi/Incidents

Wasabi: System Errors in AP-NORTHEAST-2

Timeline of updates

1. resolved2026-06-29 00:15 UTC

   Between 00:10 UTC and 18:00 UTC on June 29, some customers may have experienced increased latency and elevated HTTP 5XX error responses when performing API operations against buckets in the AP-NORTHEAST-2 (Osaka) region.

   The issue has been resolved. It was caused by a backend storage infrastructure issue that affected request processing performance. Our engineering team identified the cause, implemented corrective actions, and fully restored normal service.

2. postmortem2026-07-02 01:37 UTC

   Between 00:10 UTC and 18:00 UTC on June 29, some customers may have experienced increased latency and elevated HTTP 5XX error responses when performing API operations against buckets in AP-NORTHEAST-2. The issue was related to an infrastructure configuration introduced during expansion activities completed in June 2026. At the time of deployment, the environment operated within expected parameters and no customer impact was observed. Under subsequent production workload, the configuration resulted in degraded routing for a portion of storage traffic, leading to increased request latency and intermittent write timeouts for a subset of customer workloads.

   Once the issue was identified and correlated to the underlying configuration, the affected configuration was corrected and impacted storage services were restarted, restoring normal operation.

   Following the incident, Wasabi completed the following actions:

   • Corrected the infrastructure configuration responsible for the traffic routing issue.
   • Restored affected storage services and verified normal system performance.
   • Validated storage operation across the affected infrastructure before returning the environment to normal service.

   In order to avoid similar events in the future, Wasabi has implemented additional validation procedures during infrastructure deployment and configuration activities. These enhancements are intended to verify infrastructure configuration prior to production use and further strengthen deployment quality controls.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Wasabi profileRecent Wasabi incidentsAll outages on June 29, 2026Wasabi in June 2026MarkdownJSON