Companies / Wasabi / incidents

Wasabi: Networking availability impact in AP-SOUTHEAST-2

Affected components: AP-Southeast-2 (Sydney)

Timeline of updates

1. identified2025-06-18 23:45 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.

2. monitoring2025-06-19 00:44 UTC

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

3. resolved2025-06-19 03:28 UTC

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

4. postmortem2025-06-25 14:03 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.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Wasabi profile · Recent Wasabi incidents · Markdown · JSON