[Cancelled]Cloud SWG Localization Zone Relocation Announcement Dubai (GAEDX), Abu Dhabi (GAEAD) and Bahrain (GBHMA)

Tuesday, 24 September 23 hours and 59 minutes
Complete
Complete

This maintenance window has been cancelled. We are working on an updated schedule and a new notification will be issued once a revised schedule is finalized.

Scheduled

The Localization Zones (LZ) for Dubai, UAE (GAEDX), Abu Dhabi, UAE (GAEAD) and Manama, Bahrain (GBHMA), will be relocated from their respective current homes to the new Cloud SWG compute point-of-presence (POP) in Dammam, Saudi Arabia (GSADA). The date of this change is September 24, 2024.

The existing Dubai (GAEDX) and Abu Dhabi (GAEAD) LZ’s will be decommissioned on October 22, 2024.

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. Now that our Saudi Arabia compute POP is live in Dammam, the Localization Zones in Dubai and Abu Dhabi will benefit from a closer compute POP.

Carefully review the information below to avoid disruption of service.

Relocation Date: September 24, 2024

Ingress IP addresses

  • 148.64.17.164 (GSADA) - TO BE USED after SEPTEMBER 24, 2024
  • 34.65.98.164 - TO BE RETIRED on OCTOBER 22, 2024
  • 168.149.175.164 - TO BE RETIRED on OCTOBER 22, 2024

Egress IP ranges

  • 148.64.17.0/24 (GSADA)
  • 199.19.254.192/28 (GAEDX) - NEW on SEPTEMBER 24, 2024
  • 199.19.254.176/28 (GAEAD) - NEW on SEPTEMBER 24, 2024
  • 199.19.254.176/28 (GBHMA) - NEW on SEPTEMBER 24, 2024

  • 34.65.98.0/24 - TO BE RETIRED on OCTOBER 22, 2024

  • 168.149.175.0/24 TO BE RETIRED on OCTOBER 22, 2024

  • 148.64.6.64/27 TO BE RETIRED on OCTOBER 22, 2024

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 October 22, 2024. This change can be made after September 24, 2024.
  • 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: https://support.broadcom.com/security.

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

Began at:

Affected components
  • Cloud Secure Web Gateway
    • Point of Presence (POP) - Europe And The Middle East
      • Abu Dhabi, UAE (GAEAD)
      • Dubai, UAE (GAEDX)
      • Manama, Bahrain (GBHMA)