Resolved after 3 hours 42 minutes, affecting AP-Southeast-2 (Sydney), on June 18, 2025.
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.
Affected components
Update timeline
- identified Jun 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.
- monitoring Jun 19, 2025, 12:44 AM UTC
We continue to monitor AP-Southeast-2 (Sydney) access and it is stable, no further issues.
- resolved Jun 19, 2025, 03:28 AM UTC
The networking access to Sydney region continue normal and we are resolving this incident.
- postmortem Jun 25, 2025, 02: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.
Your product runs on more than Wasabi
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services