Notice of Datacenter Migration of Qualys US2 Platform

Lane Smith
Lane Smith, Vice President, Global Customer Support, Qualys
- 4 min read

Table of Contents

This advance notification is to inform customers with subscriptions on the US2 platform that we will be migrating from our existing colocation datacenter to another colocation datacenter. This migration is scheduled to take place on 21st  March 2025, from 5:00 PM PST, and will require a 15-hour downtime.

Please refer to the Frequently Asked Questions (FAQs) below to learn more about this move and what is needed from customers to ensure a smooth transition

Frequently Asked Questions

Q1. What is the scope of the migration activity?

A1. The Qualys US2 Shared Cloud Platform (SCP) will undergo a migration to a new datacenter. All customer data will be moved along with all applications and services from the existing SCP environment in the current data center to the new data center environment.

Q2. When is this activity scheduled?

A2. This migration will take place on 21st March 2025, from 5:00 PM PST. It will take place during the scheduled Quarterly Maintenance Downtime for the US2 Platform.

Q3. Which customers are affected by this migration?

A3. Customers with subscriptions on the US2 platform will be affected. Please refer to https://www.qualys.com/platform-identification/ for help identifying your platform.

Q4. What testing has been done?

A4. Our operations team has completed extensive testing to ensure this migration will go through smoothly. We have also migrated our other shared cloud platforms successfully in the US and other regions in a similar manner over the last year.

Q5. Will there be any impact on customers during this migration?

A5. Qualys services will be unavailable during this migration as we migrate customer data along with applications and services to the new colocation data center environment. Scans using an external scanner might get interrupted until the platform is back online. Qualys recommends pausing scans and resuming them once the platform is back online.

The IP address used for communication between Qualys Agents / Scanner Appliances / Qualys Gateway Appliance and the Shared Cloud Platform will change.

Q6. What steps does the customer need to take?

As part of this migration, the IP addresses associated with the FQDNs (URLs) & the Qualys scanners will change. Customers are recommended to allowlist Qualys’ own IP subnets 69.67.177.0/24, 69.67.182.0/24 & 2602:FDAA:C2::/48 in both directions for incoming & outgoing traffic, instead of individual IP, which will prevent them from allowing individual IP.

Customers are requested not to remove the existing IP addresses until further notice. Additional IPv4 address blocks can also be found in Security Operations Center (SOC) netblock.

URL/ServiceCurrent IP AddressAdditional IP address to whitelistServicesTraffic Direction
qualysapi.qg2.apps.qualys.com64.39.96.20269.67.177.65HTTP, HTTPSOutgoing
qgadmin.qg2.apps.qualys.com64.39.96.20369.67.177.66HTTP, HTTPSOutgoing
portal.qg2.apps.qualys.com64.39.96.20769.67.177.67HTTP, HTTPSOutgoing
portal-bo.qg2.apps.qualys.com64.39.96.20869.67.177.68HTTP, HTTPSOutgoing
distribution.qg2.apps.qualys.com64.39.96.20569.67.177.69HTTP, HTTPSOutgoing
monitoring.qg2.apps.qualys.com64.39.96.20669.67.177.70HTTP, HTTPSOutgoing
scanservice1.qg2.apps.qualys.com64.39.96.20969.67.177.71HTTP, HTTPSOutgoing
gateway.qg2.apps.qualys.com64.39.96.20469.67.177.72HTTP, HTTPSOutgoing
download.qg2.apps.qualys.com64.39.96.21069.67.177.73HTTP, HTTPSOutgoing
rns.qg2.apps.qualys.com64.39.96.21269.67.177.74HTTP, HTTPSOutgoing
certs.qg2.apps.qualys.com64.39.96.19769.67.177.75HTTP, HTTPSOutgoing
debug.qg2.apps.qualys.com64.39.96.19469.67.177.78HTTP, HTTPSOutgoing
kube.qg2.apps.qualys.com64.39.96.21469.67.177.79HTTP, HTTPSOutgoing
nac-le-service.qg2.apps.qualys.com64.39.96.16969.67.177.80HTTP, HTTPSOutgoing
camspm.qg2.apps.qualys.com64.39.96.17769.67.177.81HTTP, HTTPSOutgoing
camsrepo.qg2.apps.qualys.com64.39.96.17869.67.177.82HTTP, HTTPSOutgoing
camspublic.qg2.apps.qualys.com64.39.96.17969.67.177.83HTTP, HTTPSOutgoing
semca.qg2.apps.qualys.com64.39.96.21169.67.177.84HTTP, HTTPSOutgoing
qepp-update.qg2.apps.qualys.com64.39.96.21569.67.177.85HTTP, HTTPSOutgoing
wasoob-dns.us2.qualysperiscope.com64.39.96.21369.67.177.86DNSOutgoing
qagpublic.qg2.apps.qualys.com64.39.104.10364.39.105.42HTTP, HTTPSOutgoing
cmsqagpublic.qg2.apps.qualys.com64.39.104.10564.39.105.43HTTP, HTTPSOutgoing
qpatchpublic.qg2.apps.qualys.com64.39.104.10464.39.105.44HTTP, HTTPSOutgoing
qgadmin.qg2.apps.qualys.com2602:fdaa:2:401::ac10:21cb2602:fdaa:c2:1::4543:b142HTTP, HTTPSOutgoing
scanservice1.qg2.apps.qualys.com 2602:fdaa:2:401::ac10:21d12602:fdaa:c2:1::4543:b147HTTP, HTTPSOutgoing
distribution.qg2.apps.qualys.com2602:fdaa:2:401::ac10:21cd2602:fdaa:c2:1::4543:b145HTTP, HTTPSOutgoing
monitoring.qg2.apps.qualys.com 2602:fdaa:2:401::ac10:21ce2602:fdaa:c2:1::4543:b146HTTP, HTTPSOutgoing
qualysapi.qg2.apps.qualys.com2602:fdaa:2:401::ac10:21ca2602:fdaa:c2:1::4543:b141HTTP, HTTPSOutgoing
qagpublic.qg2.apps.qualys.comNA2602:fdaa:c4:1::4027:692aHTTP, HTTPSOutgoing
download.qg2.apps.qualys.comNA2602:fdaa:c2:1::4543:b149HTTP, HTTPSOutgoing
Scanner IPv6 block2602: fdaa::/48
2600:c02:1020: :/48
2603:c0f2:5001:4500: :/56
2602: fdaa:c5: :/48ANYIncoming & Outgoing
Scanner IPv4 block64.39.96.0/20 139.87.112.0/2369.67.182.0/24ANY  Incoming & Outgoing  
Cloud Connectors64.39.96.25
64.39.96.34
64.39.96.226 – 232
64.39.96.216
64.39.96.158 – 159		69.67.177.100/30
69.67.177.104/29
69.67.177.112/28
69.67.177.128/28		HTTPSIncoming
Share your Comments

Comments

Your email address will not be published. Required fields are marked *