Resolved
This incident has been resolved.
Posted Aug 28, 2025 - 03:30 UTC
Update
We are continuing to work on a fix for this issue.
Posted Aug 28, 2025 - 02:47 UTC
Identified
We have identified the issue and recovery is in progress.
Posted Aug 28, 2025 - 01:41 UTC
Investigating
Our engineers are currently working to confirm the impact, identify the root cause and implement a resolution.
Updates and additional details will be provided as new information becomes available.
Posted Aug 28, 2025 - 00:43 UTC
This incident affected: US (Pacific Northwest) (Remote Access VPN, Resource Connector), United Kingdom (Remote Access VPN, Resource Connector), Asia Pacific (Tokyo) (Remote Access VPN, Resource Connector), Asia Pacific (Singapore) (Remote Access VPN, Resource Connector), Asia Pacific (Hong Kong) (Remote Access VPN, Resource Connector), Australia (Sydney) (Remote Access VPN, Resource Connector), Asia Pacific (Jakarta) (Remote Access VPN, Resource Connector), India (West) (Remote Access VPN, Resource Connector), Israel (Tel Aviv) (Remote Access VPN, Resource Connector), Switzerland (Zurich) (Remote Access VPN, Resource Connector), Brazil (Remote Access VPN, Resource Connector), India (South) (Remote Access VPN, Resource Connector), Middle East (UAE) (Remote Access VPN, Resource Connector), Asia Pacific (Osaka) (Remote Access VPN, Resource Connector), Europe (Stockholm) (Remote Access VPN, Resource Connector), Africa (South Africa) (Remote Access VPN, Resource Connector), Saudi Arabia (Remote Access VPN (LA), Resource Connector (LA)), Europe (Germany) (Remote Access VPN, Resource Connector), US (Midwest) (Remote Access VPN, Resource Connector), US (California) (Remote Access VPN, Resource Connector), US (Virginia) (Remote Access VPN, Resource Connector), and Canada (Central) (Remote Access VPN, Resource Connector).