previously announced..." />

Web Security Service Announcement - Sydney Data Center Migration

Duration: 9 hours
Complete
Complete

An updated to the Sydney, Australia (SYD1) data center migration has been issued. You can find the updated information below.

https://wss.status.broadcom.com/incidents/qy74ttfsklr3

Scheduled

Please note: This scheduled maintenance has been moved to April 29, 2020, at 12:00 UTC and will last up to 9 hours.

New Schedule

  • Start Time April 29, 2020 at 12:00 UTC
  • End time April 29, 2020 at 21:00 UTC

  • Scheduled

    As part of the previously announced migration to Google Cloud Platform (GCP), the Sydney, Australia (SYD1) WSS site will be migrated on April 22, 2020, starting at 12:00 UTC. This maintenance will last up to 9 hours.

    At the conclusion of the maintenance, all WSS traffic for the Sydney site will be processed in the new GCP-based POP. The ingress and egress network IP addresses for the Sydney site will remain unchanged.

    Impact Expect the site to be completely unavailable during the maintenance window.

    Required Action IPSec: Customers should bring up their secondary tunnel prior during the maintenance window.

    Unified Agent and WSS Agent: No customer action is required. Customer traffic will be automatically redirected by Symantec to the nearest alternate site during the maintenance window.

    Symantec Endpoint Protection Web Traffic Redirector (SEP-WTR): No customer action is required. Customer traffic will be automatically redirected by Symantec to the nearest alternate site during the maintenance window. The underlying IP address for sep-wtr.threatpulse.net will not change as part of this migration.

    Explicit proxy and proxy forwarding: No customer action is required. Customers directing traffic to proxy.threatpulse.net will be automatically redirected by Symantec to the nearest alternate site during the maintenance window. The underlying IP address for proxy.threatpulse.net will not change as a part of this migration.

    Explicit over IPSec (“trans-proxy”): Customers that use explicit proxy through IPSec to ep.threatpulse.net should take the same action as IPSec customers and bring up their secondary tunnel during the maintenance. The underlying IP address for ep.threatpulse.net will not change as part of this migration.

    Others: Any customer, regardless of connection method, with a configuration pointing to a specific site or IP address must manually failover to a secondary site during the migration window to avoid an outage.

    Please visit these KB articles for a full list of IP networks used by WSS: Worldwide data center IP addresses: https://knowledge.broadcom.com/external/article?legacyId=TECH242979 Authentication IP addresses: https://knowledge.broadcom.com/external/article?legacyId=TECH240889

    Questions? Please visit this KB article for additional details on the Web Security Service Migration to Google Cloud Platform: https://knowledge.broadcom.com/external/article?legacyId=tech257356

    If you have further questions regarding this announcement, contact Technical Support. Support information is located at: https://support.broadcom.com/security

    For real time updates and status visit and subscribe to Broadcom Service Status: https://wss.status.broadcom.com

    Original Schedule

  • Start Date: April 22, 2020, at 12:00 UTC
  • End Date: April 22, 2020, at 21:00 UTC

  • Began at: