Web Security Service Maintenance Announcement

Tuesday, 26 February 1 minute

The scheduled maintenance has been completed.


This update is a clarification of the customer impact to the previously shared announcement

Updated Customer Impact The following describes what happens to connected clients, depending on access method used:

• Explicit proxy / Unified Agent / Proxy Forwarding: The service automatically redirects connections to active data pods within the same data center or geographic location. This is for information only, and the customer does not need to take any action. • IPSec: A short fail-over delay may occur as the load balancer directs traffic to another active data pod within the data center. This is for information only, and the customer does not need to take any action*.

*The creation of a backup tunnel to another data center (if not already configured) prior to the deployment is recommended for customers connecting to Oslo and Tel Aviv.


We will be conducting general maintenance. During this maintenance event all services will remain operational and available.

Timing The maintenance window will run from February 26, 2019, through March, 5, 2019. All maintenance will occur between 18:00 and 06:00 local data center time.

Original Customer Impact At times during the maintenance window, the portal may be intermittently unavailable for some administrator accounts. Existing authenticated sessions will be terminated. Administrators that have already authenticated with the portal will need to re-enter their credentials.

Additionally, users connecting to the WSS service via Auth Connector may disconnect from the portal and will not be able to reconnect until the maintenance is completed.

Reporting Problems If you experience issues following this maintenance, contact Technical Support. Support information is located at https://support.symantec.com/en_US.html or on the main Web Security Service Portal page at https://portal.threatpulse.com/. Please visit Symantec Status for periodic updates and to see other status of the service.

Began at:

Affected components