Wasabi incident

Intermittent Wasabi Console Access - Singapore (ap-southeast-1)

Notice Resolved View vendor source →

Wasabi experienced a notice incident on July 15, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
Jul 15, 2026, 07:00 PM UTC
Resolved
Jul 15, 2026, 07:00 PM UTC
Duration
—
Detected by Pingoru
Jul 15, 2026, 07:00 PM UTC

Update timeline

  1. resolved Jul 15, 2026, 08:50 PM UTC

    Between 2026-07-15 19:24 UTC and 20:26 UTC, a subset of customers experienced issues accessing the Wasabi Management Console when their requests were geo-routed through the Singapore console endpoint. Some affected customers also reported difficulty accessing bucket information through the Console. The incident occurred during the rollout of a new content delivery configuration for the Singapore console endpoint. Following deployment, some traffic routed through the new path experienced connectivity issues. Once the issue was identified, Wasabi rolled back the DNS changes, restoring the previous routing. Service recovered as DNS changes propagated globally. Following this incident, Wasabi is reviewing the deployment and validation process for regional console routing changes to improve pre-deployment testing, reduce customer impact during future rollouts, and strengthen monitoring of regional traffic after deployment.