[Action Required] Cloud SWG POP Retirement Announcement GUSPO (Portland) - August 27, 2026

The Cloud SWG datacenter for Portland, USA (GUSPO) will be retired on August 27, 2026. No performance impact is to be expected. Carefully review the information below to avoid disruption of service.

Retirement Date: August 27, 2026

Ingress IP addresses

• 168.149.133.164 (GUSLV) - MOVE YOUR IPSec TUNNELS TO THIS LOCATION before August 20
• 170.176.241.164 - TO BE RETIRED August 27, 2026

Egress IP ranges:

• 170.176.241.0/24 - TO BE RETIRED August 27, 2026
• 35.243.39.240/28 - TO BE RETIRED August 27, 2026
• 168.149.133.0/24 - REPLACEMENT (existing GUSLV1 egress IP ranges)
• 168.149.160.0/24 - REPLACEMENT (existing GUSLV1 egress IP ranges)
• 34.186.10.128/28 - REPLACEMENT (existing GUSLV1 egress IP ranges)

Required Action prior to August 27, 2026

• Firewall rules regulating connectivity to/from your network to Cloud SWG should be adjusted to allow traffic to pass to the replacement IP network listed above. This is required for all access methods, including WSS Agents running active in an office location.
• Third party applications that regulate connections by source IP address should be updated to accept connections from the replacement egress IP networks listed above to ensure traffic proxied through Cloud SWG can reach the application.

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).

• IPsec: Customers must update their tunnel configurations to point to the replacement ingress IP address before August 27, 2026. This change can be made immediately.
• WSS Agent, Symantec Enterprise Agent: Agent traffic will be automatically redirected to the replacement POP. No customer action is required.
• Explicit proxy and proxy forwarding:
  • Customers directing traffic to proxy.threatpulse.net or us.proxy.threatpulse.net will be automatically redirected to the replacement POP. No customer action is required.
  • Customers directing traffic to guspo1-vip[1-6].threatpulse.net will need to use guslv1-vip[1-6].threatpulse.net.
• Regardless of connection method, any configuration pointing to a specific POP hostname or IP address (not recommended) must be manually switched to the replacement POP prior to the decommissioning date to avoid an outage.

Please visit this KB article for a full list of IP networks used by WSS:

Technical Support

Experiencing issues? Contact technical support by visiting: .

For service status and maintenance updates visit and subscribe to Broadcom Service Status: .