Cloud SWG Localization Zone Relocation Announcement Copenhagen, Denmark (GDKCP)

The Localization Zones (LZ) for Copenhagen, Denmark (GDKCP) will be relocated from its current home to the new Cloud SWG compute point-of-presence (POP) in Amsterdam, Netherland (GNLAM).

The new IPs will be available on October 15, 2025. The old IPs will be retired on November 17, 2025. More Information

Localization Zones allow Cloud SWG to request web content using IP addresses that match the country of the end user when there is no Cloud SWG POP in the end user’s country. This results in more content being properly localized, yielding a better end user experience.

Carefully review the information below to avoid disruption of service.

Relocation Date: October 15, 2025

Ingress IP addresses

• 98.158.252.164 (GNLAM) - TO BE USED for IPSEC connections after October 15, 2025
• 34.178.0.16/28 (GNLAM) - NEW - PLEASE ENSURE ACCESS TO THIS RANGE IS ALLOWED
• 148.64.14.164 - TO BE RETIRED on November 15, 2025

Egress IP ranges

• 98.158.252.0/24 (GNLAM) - EXISTING - PLEASE ENSURE ACCESS FROM THIS RANGE IS ALLOWED
• 98.158.253.0/24 (GNLAM) - EXISTING - PLEASE ENSURE ACCESS FROM THIS RANGE IS ALLOWED
• 199.247.32.32/27 (GDKCP) - NEW on October 16, 2025
• 148.64.14.0/24 - TO BE RETIRED on November 16, 2025

Required Action

Prior to the relocation date:

• Firewall rules regulating connectivity from your network to Cloud SWG should be adjusted to allow traffic to the ingress IP networks listed above.
• Third party applications that regulate connections by source IP address should be updated to accept connections from the egress IP networks listed above to ensure traffic proxied through Cloud SWG can reach the applications.

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 GNLAM ingress IP address before November 16, 2025. This change can be made after October 15, 2025.
• 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 will be automatically redirected to the replacement POP. No customer action is required.
• 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 Cloud SWG.

Technical Support

Experiencing issues? Contact technical support by visiting here.

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