User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
qualys.com · Cloud & developer
Something is off: the vendor has scheduled maintenance. Official status: Service Under Maintenance
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Reachable from all 4 regions we check from.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 26 ms · 1 min ago.
Maintenance
Service Under Maintenance Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 09:00 | 0 | 0.0 | 53 ms | 0 |
| 09:15 | 0 | 0.0 | 69 ms | 0 |
| 09:30 | 0 | 0.0 | 103 ms | 0 |
| 09:45 | 0 | 0.0 | 26 ms | 0 |
| 10:00 | 0 | 0.0 | 113 ms | 0 |
| 10:15 | 0 | 0.0 | 37 ms | 0 |
| 10:30 | 0 | 0.0 | 190 ms | 0 |
| 10:45 | 0 | 0.0 | 85 ms | 0 |
| 11:00 | 0 | 0.0 | 88 ms | 0 |
| 11:15 | 0 | 0.0 | 32 ms | 0 |
| 11:30 | 0 | 0.0 | 124 ms | 0 |
| 11:45 | 0 | 0.0 | 49 ms | 0 |
| 12:00 | 0 | 0.0 | 22 ms | 0 |
| 12:15 | 0 | 0.0 | 88 ms | 0 |
| 12:30 | 0 | 0.0 | 24 ms | 0 |
| 12:45 | 0 | 0.0 | 28 ms | 0 |
| 13:00 | 0 | 0.0 | 143 ms | 0 |
| 13:15 | 0 | 0.0 | 52 ms | 0 |
| 13:30 | 0 | 0.0 | 20 ms | 0 |
| 13:45 | 0 | 0.0 | 109 ms | 0 |
| 14:00 | 0 | 0.0 | 193 ms | 0 |
| 14:15 | 0 | 0.0 | 20 ms | 0 |
| 14:30 | 0 | 0.0 | 17 ms | 0 |
| 14:45 | 0 | 0.0 | 236 ms | 0 |
| 15:00 | 0 | 0.0 | 35 ms | 0 |
| 15:15 | 0 | 0.0 | 48 ms | 0 |
| 15:30 | 0 | 0.0 | 42 ms | 0 |
| 15:45 | 0 | 0.0 | 52 ms | 0 |
| 16:00 | 0 | 0.0 | 267 ms | 0 |
| 16:15 | 0 | 0.0 | 73 ms | 0 |
| 16:30 | 0 | 0.0 | 197 ms | 0 |
| 16:45 | 0 | 0.0 | 172 ms | 0 |
| 17:00 | 0 | 0.0 | 101 ms | 0 |
| 17:15 | 0 | 0.0 | 243 ms | 0 |
| 17:30 | 0 | 0.0 | 46 ms | 0 |
| 17:45 | 0 | 0.0 | 71 ms | 0 |
| 18:00 | 0 | 0.0 | 102 ms | 0 |
| 18:15 | 0 | 0.0 | 37 ms | 0 |
| 18:30 | 0 | 0.0 | 91 ms | 0 |
| 18:45 | 0 | 0.0 | 27 ms | 0 |
| 19:00 | 0 | 0.0 | 211 ms | 0 |
| 19:15 | 0 | 0.0 | 85 ms | 0 |
| 19:30 | 0 | 0.0 | 94 ms | 0 |
| 19:45 | 0 | 0.0 | 128 ms | 0 |
| 20:00 | 0 | 0.0 | 45 ms | 0 |
| 20:15 | 0 | 0.0 | 113 ms | 0 |
| 20:30 | 0 | 0.0 | 104 ms | 0 |
| 20:45 | 0 | 0.0 | 26 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Qualys yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Qualys goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Qualys alerts to Slack, Discord or a webhook — free.
Something is off: the vendor has scheduled maintenance. Official status: Service Under Maintenance
If Qualys is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Qualys's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.