User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Health
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps 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. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 429 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 445 ms | 0 |
| Mon 14 | 0 | 0.0 | 334 ms | 0 |
| Mon 16 | 0 | 0.0 | 346 ms | 0 |
| Mon 18 | 0 | 0.0 | 355 ms | 0 |
| Mon 20 | 0 | 0.0 | 664 ms | 0 |
| Mon 22 | 0 | 0.0 | 362 ms | 0 |
| Tue 00 | 0 | 0.0 | 395 ms | 0 |
| Tue 02 | 0 | 0.0 | 306 ms | 0 |
| Tue 04 | 0 | 0.0 | 360 ms | 0 |
| Tue 07 | 0 | 0.0 | 343 ms | 0 |
| Tue 09 | 0 | 0.0 | 377 ms | 0 |
| Tue 11 | 0 | 0.0 | 396 ms | 0 |
| Tue 13 | 0 | 0.0 | 302 ms | 0 |
| Tue 15 | 0 | 0.0 | 373 ms | 0 |
| Tue 17 | 0 | 0.0 | 335 ms | 0 |
| Tue 20 | 0 | 0.0 | 348 ms | 0 |
| Tue 22 | 0 | 0.0 | 338 ms | 0 |
| Wed 00 | 0 | 0.0 | 360 ms | 0 |
| Wed 02 | 0 | 0.0 | 332 ms | 0 |
| Wed 05 | 0 | 0.0 | 345 ms | 0 |
| Wed 07 | 0 | 0.0 | 361 ms | 0 |
| Wed 09 | 0 | 0.0 | 373 ms | 0 |
| Wed 11 | 0 | 0.0 | 333 ms | 0 |
| Wed 13 | 0 | 0.0 | 285 ms | 0 |
| Wed 16 | 0 | 0.0 | 552 ms | 0 |
| Wed 18 | 0 | 0.0 | 406 ms | 0 |
| Wed 20 | 0 | 0.0 | 350 ms | 0 |
| Wed 22 | 0 | 0.0 | 382 ms | 0 |
| Thu 00 | 0 | 0.0 | 341 ms | 0 |
| Thu 02 | 0 | 0.0 | 375 ms | 0 |
| Thu 04 | 0 | 0.0 | 333 ms | 0 |
| Thu 06 | 0 | 0.0 | 330 ms | 0 |
| Thu 08 | 0 | 0.0 | 316 ms | 0 |
| Thu 11 | 0 | 0.0 | 372 ms | 0 |
| Thu 13 | 0 | 0.0 | 338 ms | 0 |
| Thu 15 | 0 | 0.0 | 420 ms | 0 |
| Thu 16 | 0 | 0.0 | 374 ms | 0 |
| Thu 19 | 0 | 0.0 | 445 ms | 0 |
| Thu 21 | 0 | 0.0 | 345 ms | 0 |
| Thu 22 | 0 | 0.0 | 320 ms | 0 |
| Fri 01 | 0 | 0.0 | 319 ms | 0 |
| Fri 03 | 0 | 0.0 | 351 ms | 0 |
| Fri 05 | 0 | 0.0 | 329 ms | 0 |
| Fri 07 | 0 | 0.0 | 355 ms | 0 |
| Fri 09 | 0 | 0.0 | 360 ms | 0 |
| Fri 11 | 0 | 0.0 | 379 ms | 0 |
| Fri 13 | 0 | 0.0 | 326 ms | 0 |
| Fri 15 | 0 | 0.0 | 429 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for ConsumerLab 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 ConsumerLab goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send ConsumerLab alerts to Slack, Discord or a webhook — free.
ConsumerLab, at consumerlab.com, is one of the Health services we monitor. Independent test results, reviews, ratings, and comparisons of vitamins, supplements, herb and nutrition products to consumers and healthcare providers.
ConsumerLab publishes an official status page at status.consumerlab.com; when we can read it, its incident level is folded into the status shown here.
Common problems for 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 356 ms average, 313–445 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public ConsumerLab incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
356 ms on average over the last 24 hours (313–445 ms).
Yes, at https://status.consumerlab.com.
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 ConsumerLab here at once, the problem is on ConsumerLab's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with ConsumerLab. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.