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

What to do

• Check whether you use Wasabi in ap-southeast-1, apac. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-07-15 20:50 UTC and 2026-07-15 19:00 UTC may need a replay.

• Subscribe to Wasabi's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=wasabi works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Wasabi 1

1. resolvedJul 15, 2026, 7:00 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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.