Virginia Capacity Expansion ActivitiesTo ensure the highest levels of security and performance, our team has scheduled expansion activities within the Virginia data center beginning on Friday February 24th, with completion by Tuesday February 28th. During this time, we are performing proactive IP address space maintenance in preparation for increased capacity at this datacenter.

Since there is implementation of additional IP addresses, please note that specific customer action may be required (see impact statements below).

Auth Ingress IP

Egress IP

38.134.125.133

38.134.125.0/27

38.134.125.141

38.134.125.32/27

38.134.125.149

38.134.125.64/27

38.134.125.157

38.134.125.96/27

38.134.125.197

38.134.125.160/27

38.134.125.205

38.134.125.224/27

TimingThe implementation of additional IP addresses for the Virginia datacenter will begin on Friday February 24th and be completed by Tuesday February 28th.

Service ImpactThis set of activities will have no impact on the existing connectivity of data traffic passing through the service. Please note the possible impact on new connections below.

Customer Impact & ActionIf connectivity to the Web Security Service is behind stringent firewall rules, firewall rules may need to be adjusted to allow traffic to pass.

The following describes what happens for each access method when the new capacity becomes available:• Explicit Proxy, Unified Agent, and Proxy Forwarding: If these devices are behind a protected network, the datapod egress IP addresses noted above should be accommodated by traffic firewall rules.• IPSec, Unified Agent: If the firewall restricts outbound authentication traffic to the Web Security Service, please allow the authentication traffic to connect to the authentication ingress IP address.