User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Health
questdiagnostics.com · Health
Checks are succeeding and user reports are near the baseline.
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.
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 620 ms · 7 min ago.
No status feed
Quest Diagnostics does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 12:30 | 0 | 0.0 | 387 ms | 0 |
| 12:45 | 0 | 0.0 | 610 ms | 0 |
| 13:00 | 0 | 0.0 | 1206 ms | 0 |
| 13:15 | 0 | 0.0 | 658 ms | 0 |
| 13:30 | 0 | 0.0 | 1300 ms | 0 |
| 13:45 | 0 | 0.0 | 239 ms | 0 |
| 14:00 | 0 | 0.0 | 420 ms | 0 |
| 14:15 | 0 | 0.0 | 251 ms | 0 |
| 14:30 | 0 | 0.0 | 349 ms | 0 |
| 14:45 | 0 | 0.0 | 1156 ms | 0 |
| 15:00 | 0 | 0.0 | 598 ms | 0 |
| 15:15 | 0 | 0.0 | 1165 ms | 0 |
| 15:30 | 0 | 0.0 | 633 ms | 0 |
| 15:45 | 0 | 0.0 | 642 ms | 0 |
| 16:00 | 0 | 0.0 | 1056 ms | 0 |
| 16:15 | 0 | 0.0 | 447 ms | 0 |
| 16:30 | 0 | 0.0 | 845 ms | 0 |
| 16:45 | 0 | 0.0 | 972 ms | 0 |
| 17:00 | 0 | 0.0 | 733 ms | 0 |
| 17:15 | 0 | 0.0 | 522 ms | 0 |
| 17:30 | 0 | 0.0 | 910 ms | 0 |
| 17:45 | 0 | 0.0 | 159 ms | 0 |
| 18:00 | 0 | 0.0 | 1448 ms | 0 |
| 18:15 | 0 | 0.0 | 982 ms | 0 |
| 18:30 | 0 | 0.0 | 530 ms | 0 |
| 18:45 | 0 | 0.0 | 905 ms | 0 |
| 19:00 | 0 | 0.0 | 250 ms | 0 |
| 19:15 | 0 | 0.0 | 1282 ms | 0 |
| 19:30 | 0 | 0.0 | 1081 ms | 0 |
| 19:45 | 0 | 0.0 | 1187 ms | 0 |
| 20:00 | 0 | 0.0 | 1056 ms | 0 |
| 20:15 | 0 | 0.0 | 820 ms | 0 |
| 20:30 | 0 | 0.0 | 188 ms | 0 |
| 20:45 | 0 | 0.0 | 369 ms | 0 |
| 21:00 | 0 | 0.0 | 1028 ms | 0 |
| 21:15 | 0 | 0.0 | 354 ms | 0 |
| 21:30 | 0 | 0.0 | 655 ms | 0 |
| 21:45 | 0 | 0.0 | 747 ms | 0 |
| 22:00 | 0 | 0.0 | 620 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 Quest Diagnostics 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 Quest Diagnostics goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Quest Diagnostics alerts to Slack, Discord or a webhook — free.
Quest Diagnostics is listed in our Health category and checked at questdiagnostics.com. Live checks and user reports.
Quest Diagnostics has no official status feed we can read, so this page relies on our own checks and user reports.
What usually goes wrong with health services: patient portal and member sign-in failures, prescription refills or appointment booking not going through, and app errors.
Measured uptime from our checks: 100% over 1 day of checks. No public incidents logged since monitoring began 1 day ago.
Response time over the last 24 hours: 771 ms average, 109–2170 ms range across 73 successful checks.
Checks are succeeding and user reports are near the baseline.
We have not recorded a public Quest Diagnostics incident since monitoring began 1 day ago.
From our own checks: 100% over 1 day of checks.
771 ms on average over the last 24 hours (109–2170 ms).
Not one we can read. This page uses independent checks of questdiagnostics.com and user reports.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For health services, watch for patient portal and member sign-in failures, prescription refills or appointment booking not going through, and app errors. If many people report Quest Diagnostics here at once, the problem is on Quest Diagnostics's side.