Networking availability impact in AP-SOUTHEAST-2

What to do

• Check whether you use Wasabi AP-Southeast-2 (Sydney) in ap-southeast-2, au. 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 3h 43m it lasted.

  Anything that failed between 2025-06-18 23:45 UTC and 2025-06-19 03:28 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 4

1. identifiedJun 18, 2025, 11:45 PM UTC

   Our Team had identified issues with network connectivity for AP-Southeast-2 (Sydney) for a few minutes ago (9:10 .. 09:30 am approximately) and it is already mitigated. We will keep updating once we have more information.

   provider

2. monitoringJun 19, 2025, 12:44 AM UTC

   We continue to monitor AP-Southeast-2 (Sydney) access and it is stable, no further issues.

   provider

3. resolvedJun 19, 2025, 3:28 AM UTC

   The networking access to Sydney region continue normal and we are resolving this incident.

   provider

4. postmortemJun 25, 2025, 2:03 PM UTC

   On 18 June 2025 at 23:10 UTC, Wasabi’s Sydney vault was impacted by Network issue at one of our network provider for 20 minutes, causing client requests to result in timeout when trying to reach to Wasabi endpoint in Sydney \([s3.ap-southeast-2.wasabisys.com](http://s3.ap-southeast-2.wasabisys.com)\). This issue was caused by one of the Networking providers in the region, which incorrectly blocked all traffic destined for Wasabi. The situation was restored to normal operation by migrating traffic to one of our other network providers until the routing issue was resolved.

   provider

Corrections

None so far.

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