[Action Required] Cloud SWG Localization Zone Relocation Announcement: Bahrain (GBHMA)

Wednesday, 19 August 23 hours and 59 minutes
Scheduled
Scheduled

The Localization Zone for Bahrain (GBHMA), will be relocated from its current home in Mumbai, India, to the Cloud SWG compute point-of-presence (POP) in Dammam, Saudi Arabia (GSADA). The date of this change is August 19, 2026.

The new IPs will be available on August 19, 2026. The old IPs will be retired on September 23, 2026. Carefully review the information below to avoid disruption of service.

Relocation Date: August 19, 2026

Ingress IP addresses

  • 148.64.17.164 (GSADA) - MOVE YOUR IPSEC tunnels to this IP after August 19, 2026

Egress IP ranges

  • 109.68.63.0/24 (GSADA)
  • 34.166.201.32/28 (GSADA)
  • 2604:b040:13:1600::/80 (GSADA)
  • 199.19.254.160/28 (GBHMA) - NEW on August 19, 2026
  • 148.64.13.128/26 - TO BE RETIRED on SEPTEMBER 23, 2026

Required Action

Prior to the relocation date:

  • Firewall rules regulating connectivity to/from your network to Cloud SWG should be adjusted to allow traffic to pass to the egress 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 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 GSADA ingress IP address before September 23, 2026. This change can be made after August 19, 2026.
  • 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:

https://knowledge.broadcom.com/external/article/167174/web-security-service-wss-ingress-and-egr.html

Technical Support

Experiencing issues? Contact technical support by visiting: https://support.broadcom.com/security.

For service status and maintenance updates visit and subscribe to Broadcom Service Status: https://status.broadcom.com/services/cloud-secure-web-gateway/.

Affected components
  • Cloud Secure Web Gateway
    • Point of Presence (POP) - APAC
      • Mumbai, India (GINMU)
    • Point of Presence (POP) - Europe And The Middle East
      • Dammam, Saudi Arabia (GSADA)
      • Manama, Bahrain (GBHMA)