Cloud SWG: General Product Maintenance (Multiple EMEA POPs) February 19 - 28, 2025

Update

Please note, the maintenance for the London, England (GGBLO) POP has been cancelled. We are working on an updated schedule and a new notification will be issued once a revised schedule is finalized.

The maintenance for the remaining POPs listed as part of this maintenance was completed as scheduled.

Update

Please be advised that the date/time for this maintenance has been changed. The impact however remains unchanged. Here is the updated schedule:

Updated Schedule

• Start Date: February 19, 2025 19:00 UTC
• End Date: February 28, 2025 04:00 UTC

Updated POP Schedule

• London, England (GGBLO) :
  • Start Date: February 27, 2025 19:00 UTC
  • Start Date: February 28, 2025 04:00 UTC

The scheduled maintenance is now underway. We'll keep you updated on our progress.

Update

Please be advised that the date/time for this maintenance has been changed. The impact however remains unchanged. Here is the updated schedule:

Updated Schedule

• Start date: February 19, 2025; 19:00 UTC
• End Date: February 28, 2025; 01:00 UTC

Updated POP Schedule

• London, England (GGBLO) : February 27, 2025; 19:00 UTC - February 28, 2025; 01:00 UTC

Broadcom will perform general maintenance to the Cloud SWG POPs in Stockholm, Sweden (GSESK), London, England (GGBLO) and Frankfurt, Germany (GDEFR) on February 19, 2025, starting at 19:00 UTC and completing on February 22, 2025 at 01:00 UTC. This maintenance includes the addition of IPv6 egress addresses to the sites. Please refer to the details below for location-specific information.

Ingress IP Address:

• Stockholm, Sweden (GSESK) : 199.247.35.164 - NO CHANGE
• London, England (GGBLO) : 148.64.26.164 - NO CHANGE
• Frankfurt, Germany (GDEFR) : 199.247.38.164 - NO CHANGE

Egress IP Addresses:

• Stockholm, Sweden (GSESK) :
  • 199.247.35.0/24 - NO CHANGE
  • 2604:b040:0013:0d00:0002:0000:0000:0000/80 - NEW on February 19, 2025
• London, England (GGBLO) :
  • 148.64.9.0/24 - NO CHANGE
  • 148.64.26.0/24 - NO CHANGE
  • 148.64.27.0/24 - NO CHANGE
  • 148.64.28.0/24 - NO CHANGE
  • 148.64.29.0/24 - NO CHANGE
  • 148.64.30.0/24 - NO CHANGE
  • 46.235.154.0/24 - NO CHANGE
  • 34.39.35.128/26 - NO CHANGE
  • 2604:b040:0013:1000:0000:0000:0000:0000/80 - NEW on February 20, 2025
• Frankfurt, Germany (GDEFR) :
  • 199.247.38.0/24 - NO CHANGE
  • 2604:b040:0013:1100:0001:0000:0000:0000/80 - NEW on February 21, 2025

Impact

Expect the site to be completely unavailable during the maintenance window.

Following this maintenance, the new IPv6 addresses will be available to Cloud SWG proxies to communicate with content providers when the following conditions are true:

• The content provider serves content over IPv6 ONLY (not IPv4/IPv6 dual stack)
• The content is accessed by the client via explicit proxy using the hostname (not IPv6 address)

Please note: Cloud SWG prefers IPv4 when it encounters dual-stack (IPv4 and IPv6) content sources. Broader IPv6 capabilities will be introduced in future releases.

IP address maintenance will be performed as part of this maintenance. If you have restrictive access policies based on our network ranges and you will access IPv6-only content, you should update your access policies to include the new IPv6 egress ranges. Please review our best practices and published network ranges in this article.

Timing

• Stockholm, Sweden (GSESK) : February 19, 2025 19:00 UTC - February 20, 2025 10:00 UTC
• London, England (GGBLO) : February 20, 2025 19:00 UTC - February 21, 2025 01:00 UTC
• Frankfurt, Germany (GDEFR) : February 21, 2025 19:00 UTC - February 22, 2025 01:00 UTC

Required Action

Prior to the maintenance date:

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

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: Switch to your secondary tunnel prior to the maintenance window.
• Explicit proxy and proxy forwarding: Customers directing traffic to proxy.threatpulse.net will be automatically redirected by the service to the nearest alternate site during the maintenance window.
• Agent: no actions required.

Technical Support

Experiencing issues? Contact technical support by visiting here.

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