Cloud SWG POP Upgrade: Johannesburg and Localization Zones for Angola, Botswana, Kenya, Malawi, Mauritius, ​​Mozambique, Namibia, Zambia, Zimbabwe

The maintenance is now complete. Thanks for your patience.

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

We are pleased to announce that the Johannesburg Localization Zone (GZAJB) will be upgraded to a compute point-of-presence (POP) in Johannesburg, South Africa. The new POP, GZASO, is engineered to service customers in South Africa and the surrounding region. GZASO is hosted in the new Google Cloud region africa-south1 in Johannesburg and will be available on July 22, 2024.

Additionally, as part of this upgrade, the Localization Zones for Angola, Botswana, Kenya, Malawi, Mauritius, Mozambique, Namibia, Zambia, Zimbabwe will be moved to africa-south1.

What are Localization Zones?

Localization Zones allow Cloud SWG to request content in a manner that gives content providers the ability to return content in the optimal language for the user, better matching their native web experience. Please note that content providers choose whether or not to localize their content and what localizations they support.

Impact

This upgrade requires some IP changes. Please carefully review the information below to avoid disruption of service.

New POP GZASO General Availability Date: July 22, 2024

GZAJB Decommission Date: August 12, 2024

Ingress IP Addresses:

• 199.19.251.164 - NEW July 22, 2024 (GZASO)
• 109.68.58.164 - TO BE RETIRED August 12, 2024 (existing GZAJB ingress IP address)

Egress IP Addresses:

• 199.19.251.0/24 - NEW July 22, 2024 (GZASO)
• 109.68.58.0/24 - TO BE RETIRED August 12, 2024 (existing GZAJB egress IP range)

The Localization Zones for Angola, Botswana, Kenya, Malawi, Mauritius, Mozambique, Namibia, Zambia and Zimbabwe use the following new egress IP addresses:

• Angola

  • 199.19.254.0/28 - NEW July 22, 2024
  • 46.235.158.0/27 - TO BE RETIRED July 22, 2024

• Botswana

  • 99.19.254.16/28 - NEW July 22, 2024
  • 46.235.158.32/27 - TO BE RETIRED July 22, 2024

• Kenya

  • 99.19.254.32/28 - NEW July 22, 2024
  • 46.235.158.64/27 - TO BE RETIRED July 22, 2024

• Malawi

  • 199.19.254.48/28 -NEW July 22, 2024
  • 46.235.158.96/27 - TO BE RETIRED July 22, 2024

• Mauritius

  • 199.19.254.64/28 - NEW July 22, 2024
    
  • 46.235.157.96/27 -TO BE RETIRED July 22, 2024

• Mozambique

  • 199.19.254.80/28 - NEW July 22, 2024
  • 46.235.157.96/27 -TO BE RETIRED July 22, 2024

• Namibia

  • 199.19.254.96/28 - NEW July 22, 2024
  • 46.235.157.96/27 -TO BE RETIRED July 22, 2024

• Zambia

  • 199.19.254.112/28 - NEW July 22, 2024
    
  • 46.235.157.96/27 -TO BE RETIRED July 22, 2024

• Zimbabwe

  • 199.19.254.128/28 - NEW July 22, 2024
    
  • 46.235.157.96/27 -TO BE RETIRED July 22, 2024

Required Action

Prior to the General Availability Date: July 22, 2024

• 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 NEW egress IP networks listed above to ensure traffic proxied through Cloud SWG can reach the application.
• Auth Connector must be able to communicate with all egress ranges 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: Customers must update their tunnel configurations to point to the NEW ingress IP address before August 12, 2024. This change can be made after July 22, 2024.
• Agents: Traffic from all supported agents will be automatically directed to the new POP where appropriate. No action is required.
• Explicit proxy, proxy forwarding: Customers directing traffic to proxy.threatpulse.net will be automatically redirected to the new POP. No customer action is required.
• Regardless of the connection method, any configuration pointing to a specific POP hostname or IP address (not recommended) must be manually switched to the new 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.