Notice of Datacenter Migration of Qualys US01 Platform

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

Last updated on: April 10, 2025

Table of Contents

This advance notification is to inform customers with subscriptions on the US01 platform that we will be migrating from our existing colocation datacenter to another colocation datacenter. This migration is scheduled to take place on 30th May 2025, from 5:00 PM PST, and will require 15 hours’ 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

What is the scope of the migration activity?

The Qualys US01 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.

When is this activity scheduled?

This migration will take place on 30th May 2025,from 5:00 PM PST. It will take place during the scheduled Quarterly Maintenance Downtime for the US01 Platform.

Which customers are affected by this migration?

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

What testing has been done?

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.

Will there be any impact on customers during this migration?

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 Cloud Agents / Scanner Appliances / Qualys Gateway Appliance/ Qualys sensor, and the Shared Cloud Platform will change.

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 requested to allowlist Qualys’ own IP subnets 69.67.176.0/24, 69.67.181.0/24, 64.39.105.0/24, 2602:fdaa:c1::/48, 2602:fdaa:c4::/48 and 2602:fdaa:c5::/48 in both directions for incoming & outgoing traffic, instead of individual IP, which will prevent customers from allowing individual IP.

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

URL/ServiceCurrent IP AddressAdditional IPs to whitelistServicesTraffic Direction
qualysapi.qualys.com64.39.96.1769.67.176.65HTTP, HTTPSOutgoing
qgadmin.qualys.com64.39.96.11069.67.176.66HTTP, HTTPSOutgoing
portal-bo.qualys.com64.39.96.11369.67.176.68HTTP, HTTPSOutgoing
dist01.sjdc01.qualys.com64.39.96.1669.67.176.69HTTP, HTTPSOutgoing
nochost.sjdc01.qualys.com64.39.96.23869.67.176.70HTTP, HTTPSOutgoing
scanservice1.qualys.com64.39.96.1869.67.176.71HTTP, HTTPSOutgoing
gateway.qg1.apps.qualys.com64.39.96.11569.67.176.72HTTP, HTTPSOutgoing
download.qualys.com64.39.96.4369.67.176.73HTTP, HTTPSOutgoing
certs.qualysguard.qualys.com64.39.96.18069.67.176.75HTTP, HTTPSOutgoing
sac-gateway-service.qg1.apps.qualys.com64.39.96.21969.67.176.77HTTP, HTTPSOutgoing
debug.qualys.com64.39.96.11269.67.176.78HTTP, HTTPSOutgoing
kube.qualys.com64.39.96.10769.67.176.79HTTP, HTTPSOutgoing
nac-le-service.qg1.apps.qualys.com64.39.96.22969.67.176.80HTTP, HTTPSOutgoing
camspm.qg1.apps.qualys.com64.39.96.18169.67.176.81HTTP, HTTPSOutgoing
camsrepo.qg1.apps.qualys.com64.39.96.18269.67.176.82HTTP, HTTPSOutgoing
camspublic.qg1.apps.qualys.com64.39.96.18369.67.176.83HTTP, HTTPSOutgoing
semca.qg1.apps.qualys.com64.39.96.11769.67.176.84HTTP, HTTPSOutgoing
wasoob-dns.us1.qualysperiscope.com64.39.96.10669.67.176.86DNSOutgoing
qagpublic.qg1.apps.qualys.com64.39.104.9364.39.105.52HTTP, HTTPSOutgoing
cmsqagpublic.qg1.apps.qualys.com64.39.104.9464.39.105.53HTTP, HTTPSOutgoing
qpatchpublic.qg1.apps.qualys.com64.39.104.9564.39.105.54HTTP, HTTPSOutgoing
qgadmin.qualys.com2602:fdaa:2:1::ac10:1182602:fdaa:c1:1::4543:b042HTTP, HTTPSOutgoing
scanservice1.qualys.com2602:fdaa:2:1::ac10:1112602:fdaa:c1:1::4543:b047HTTP, HTTPSOutgoing
dist01.sjdc01.qualys.com2602:fdaa:2:1::ac10:1ed2602:fdaa:c1:1::4543:b045HTTP, HTTPSOutgoing
nochost.sjdc01.qualys.com2602:fdaa:2:1::ac10:1ee2602:fdaa:c1:1::4543:b046HTTP, HTTPSOutgoing
qualysapi.qualys.com2602:fdaa:2:1::ac10:1102602:fdaa:c1:1::4543:b041HTTP, HTTPSOutgoing
qagpublic.qg1.apps.qualys.com2602:fdaa:0:4001::ac10:15d2602:fdaa:c4::4027:6934HTTP, HTTPSOutgoing
Scanner IPv6 block2600:c02:1020::/48 2603:c0f2:5001:4500::/56 2602:fdaa::/482602:fdaa:c5::/48ANYIncoming & Outgoing
Scanner IPv4 block64.39.96.0/20
139.87.112.0/23		69.67.181.0/24ANYIncoming & Outgoing  
Cloud Connectors64.39.96.35
64.39.96.220 – 64.39.96.221 64.39.96.94- 64.39.96.98 64.39.96.126- 64.39.96.127		69.67.176.100/30
69.67.176.104/29
69.67.176.112/28
69.67.176.128/28		HTTPSIncoming
Share your Comments

Comments

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