Cloud SWG: Jakarta, Indonesia (GIDJK) POP Maintenance July 30, 2024

The maintenance is now complete. Thanks for your patience.

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

Broadcom will perform maintenance to the Cloud SWG service in Jakarta, Indonesia (GIDJK) POP on July 30, 2024, starting at 18:00 UTC for a duration of 6 hours.

After the maintenance, in addition to agent traffic, you will also be able to use this location with IPSec, proxy forwarding and explicit proxy traffic.

Impact

• Expect the site to be completely unavailable during the maintenance window
• No IP address changes will occur with this maintenance for agent traffic
• Please read carefully in case you are planning to use the location for IPSec, proxy forwarding or explicit proxy traffic

Ingress IP Address for IPSec will be available after July 30, 2024

• 168.149.180.164

Egress IP Addresses - NO CHANGES

• 168.149.180.0/24

Required Action by Connection Method

• WSS Agent / SEA (Single Enterprise Agent): The service automatically redirects connections to active data pods within the closest geographic location. This is for information only, and the customer does not need to take any action
• Explicit proxy/ Proxy Forwarding: no actions need to be performed
• IPSec: no actions need to be performed

Required Action

In case you are planning to use this location for IPSec, proxy forwarding or explicit proxy traffic after the maintenance window, make sure to follow the instructions below:

• Firewall rules regulating connectivity to/from your network to Cloud SWG should be adjusted to allow traffic to pass through the egress IP network above
• Third party applications that regulate connections by source IP address should be updated to accept connections from the egress IP network listed above to ensure traffic proxied through Cloud SWG can reach the application
• Auth Connector must be able to communicate with the egress range listed above on TCP 443, where applicable. In case you are planning to use this location for IPSec, make sure to configure a secondary location for DPD

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).

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.