Tokyo (GJPTK11) Site Maintenance

Duration: 12 hours
Complete
Complete
After 1 month, 2 days, 20 hours, and 22 minutes

The scheduled maintenance has been completed.

Underway
After 1 month, 2 days, 8 hours, and 23 minutes

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Scheduled
After 1 month, 22 hours, and 59 minutes

Please be advised that the date/time for this maintenance has been changed. The impact however remains unchanged. Here is the updated schedule:

Updated Schedule • Start Date: February 17, 2022, at 09:00 UTC • End Date: February 17, 2022, at 21:00 UTC

Scheduled
After 3 weeks, 3 days, 18 hours, and 56 minutes

Please be advised that the date/time for this maintenance has been changed. The impact however remains unchanged. Here is the updated schedule:

Updated Schedule • Start Date: February 16, 2022, at 09:00 UTC • End Date: February 16, 2022, at 21:00 UTC

Scheduled

The Tokyo (GJPTK11) WSS site will undergo maintenance beginning on February 15, 2022 starting at 9:00 UTC, lasting for a duration of up to 12 hours.

• IP address changes will occur so it is imperative to adjust access control lists appropriately. • No impact to WSS traffic is expected during the maintenance window. • Carefully review the information below to avoid disruption of service.

Ingress IP addresses • 223.29.218.164 - NO CHANGE

Egress IP ranges: • 223.29.218.0/24 - NO CHANGE • 168.149.158.0/24 - NEW on February 15, 2022

Impact No impact to WSS traffic is expected during the maintenance window.

Required Action prior to February 15, 2022 Failure to make these changes could prevent users from connecting to WSS, accessing third party web applications, or authenticating against the service using the Auth Connector (where applicable).

• Firewall rules regulating connectivity to/from your network to WSS should be adjusted to allow traffic to pass to the IP network 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 WSS can reach the application. • Auth Connector must be able to communicate with all egress ranges listed above on TCP 443, where applicable.

Please visit this KB article for a full list of IP networks used by WSS: https://knowledge.broadcom.com/external/article?legacyId=TECH242979

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://wss.status.broadcom.com.

Began at:

Affected components