Cloud SWG Announcement Melbourne, Australia (GAUME) POP Failover Testing November 04, 2025

The Melbourne, Australia (GAUME) Cloud SWG site will undergo a data center failover test beginning on November 04, 2025 starting at 14:30 UTC, lasting for a duration of up to 36 hours. Failover testing is conducted on a regular basis to ensure the platform can gracefully handle a real outage. Carefully review the information below to avoid disruption of service.

Timing

• Failover : November 04, 2025 at 14:30 UTC
• Failback : November 05, 2025 at 14:30 UTC

Impact

The following describes what happens to connected clients during the testing window, based on access method:

• WSS Agent and SEP Agent: The service automatically redirects connections to alternate infrastructure within the same geographic location during the testing window.
• IPSec, Proxy Forwarding and Explicit methods will failover to Sydney, Australia (GAUSY) Cloud SWG site if recommendations have been followed in this Broadcom article, Cloud SWG backup sites, hostnames and VIPs for fixed locations

Cloud SWG Sydney, Australia (GAUSY) egress IP ranges (provided for convenience):

• 103.246.36.0/24
• 103.246.39.0/24
• 148.64.2.0/24
• 34.40.220.240/28 - Available after October 15, 2025
• 2604:b040:13:a00::/80

Cloud SWG Melbourne, Australia (GAUME) egress IP ranges (provided for convenience):

• 168.149.190.0/24
• 34.129.194.64/28 - To be added on November 03, 2025
• 2604:b040:13:b00::/80

Please reference this KB article for all Cloud SWG data center IP ranges.

Required Action

Prior to November 04 ,2025, please ensure that your agents can connect to any Cloud SWG data center to maximize failover opportunities. Although most agents will fail over to Sydney, some may failover to other data centers for various reasons. Failure to make these changes could prevent users from connecting to Cloud SWG, accessing third party web applications, or authenticating against the service using the Auth Connector (where applicable).

• Firewall rules regulating connectivity to/from your network to Cloud SWG should be adjusted to allow traffic to pass to the IP networks listed in the KB article above.
• Third party applications that regulate connections by source IP address should be updated to accept connections from the IP networks in the KB article above to ensure traffic proxied through Cloud SWG can reach the applications.
• Auth Connector must be able to communicate with all IP ranges listed in the KB article above, on TCP 443, where applicable.