Cloud SWG: General Product Maintenance (Multiple Americas POPs) February 17 - 21, 2025

Broadcom will perform general maintenance to the Cloud SWG POPs in Mexico City, Mexico (GMXMC), Washington, DC (GUSAS), Los Angeles, California (GUSLA), Columbia, South Carolina (GUSCO), and Des Moines, Iowa (GUSDM) on February 17, 2025, starting at 03:00 UTC and completing on February 21, 2025 at 09: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:

• Mexico City, Mexico (GMXMC) : 170.176.246.164 - NO CHANGE
• Washington, DC (GUSAS) : 170.176.240.164 - NO CHANGE
• Los Angeles, California (GUSLA) : 199.19.248.164 - NO CHANGE
• Columbia, South Carolina (GUSCO) : 168.149.137.164 - NO CHANGE
• Des Moines, Iowa (GUSDM) : 199.247.42.164 - NO CHANGE

Egress IP Addresses:

• Mexico City, Mexico (GMXMC)
  • 170.176.246.0/24 - NO CHANGE
  • 2604:b040:0013:2100:0000:0000:0000:0000/80 - NEW on February 17, 2025
• Washington, DC (GUSAS)
  • 168.149.142.0/24- NO CHANGE
  • 168.149.143.0/24- NO CHANGE
  • 168.149.144.0/24- NO CHANGE
  • 168.149.145.0/24- NO CHANGE
  • 168.149.146.0/24- NO CHANGE
  • 168.149.151.0/24- NO CHANGE
  • 168.149.152.0/24- NO CHANGE
  • 168.149.153.0/24- NO CHANGE
  • 168.149.157.0/24- NO CHANGE
  • 170.176.240.0/24- NO CHANGE
  • 2604:b040:0013:1e00:0000:0000:0000:0000/80 - NEW on February 18, 2025
• Los Angeles, California (GUSLA)
  • 148.64.18.0/24 - NO CHANGE
  • 199.19.248.0/24 - NO CHANGE
  • 2604:b040:0013:2100:0001:0000:0000:0000/80 - NEW on February 19, 2025
    
• Columbia, South Carolina (GUSCO)
  • 168.149.135.0/24- NO CHANGE
  • 168.149.137.0/24- NO CHANGE
  • 168.149.138.0/24- NO CHANGE
  • 168.149.139.0/24- NO CHANGE
  • 168.149.140.0/24- NO CHANGE
  • 168.149.141.0/24- NO CHANGE
  • 2604:b040:0013:1d00:0000:0000:0000:0000/80 - NEW on February 20, 2025
• Des Moines, Iowa (GUSDM)
  • 199.247.32.0/24 - NO CHANGE
  • 199.247.33.0/24 - NO CHANGE
  • 199.247.42.0/24 - NO CHANGE
  • 199.247.43.0/24 - NO CHANGE
  • 199.247.44.0/24 - NO CHANGE
  • 199.247.45.0/24 - NO CHANGE
  • 199.116.168.0/24 - NO CHANGE
  • 199.116.169.0/24 - NO CHANGE
  • 199.116.170.0/24 - NO CHANGE
  • 199.116.171.0/24 - NO CHANGE
  • 199.116.173.0/24 - NO CHANGE
  • 148.64.31.0/24 - NO CHANGE
  • 35.192.241.0/24 - NO CHANGE
  • 2604:b040:0013:1c00:0100: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 contents, 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

• Mexico City, Mexico (GMXMC) : February 17, 2025 03:00 UTC to 09:00 UTC
• Washington, DC (GUSAS): February 18, 2025 03:00 UTC to 09:00 UTC
• Los Angeles, California (GUSLA) : February 19, 2025 03:00 UTC to 09:00 UTC
• Columbia, South Carolina (GUSCO) : February 20, 2025 03:00 UTC to 09:00 UTC
• Des Moines, Iowa (GUSDM) : February 21, 2025 03:00 UTC to 09: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.