User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Health
1800contacts.com · Health
The site answers but blocks automated checks, so we rely on user reports and the official status. 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.
Not enough checks
Last check reached it in 79 ms · 1 min ago.
No status feed
1-800 Contacts does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 12:30 | 0 | 0.0 | 87 ms | 0 |
| 12:45 | 0 | 0.0 | 94 ms | 0 |
| 13:00 | 0 | 0.0 | 102 ms | 0 |
| 13:15 | 0 | 0.0 | 72 ms | 0 |
| 13:30 | 0 | 0.0 | 146 ms | 0 |
| 13:45 | 0 | 0.0 | 42 ms | 0 |
| 14:00 | 0 | 0.0 | 153 ms | 0 |
| 14:15 | 0 | 0.0 | 185 ms | 0 |
| 14:30 | 0 | 0.0 | 144 ms | 0 |
| 14:45 | 0 | 0.0 | 146 ms | 0 |
| 15:00 | 0 | 0.0 | 103 ms | 0 |
| 15:15 | 0 | 0.0 | 96 ms | 0 |
| 15:30 | 0 | 0.0 | 151 ms | 0 |
| 15:45 | 0 | 0.0 | 212 ms | 0 |
| 16:00 | 0 | 0.0 | 416 ms | 0 |
| 16:15 | 0 | 0.0 | 225 ms | 0 |
| 16:30 | 0 | 0.0 | 220 ms | 0 |
| 16:45 | 0 | 0.0 | 2386 ms | 0 |
| 17:00 | 0 | 0.0 | 139 ms | 0 |
| 17:15 | 0 | 0.0 | 1031 ms | 0 |
| 17:30 | 0 | 0.0 | 132 ms | 0 |
| 17:45 | 0 | 0.0 | 85 ms | 0 |
| 18:00 | 0 | 0.0 | 107 ms | 0 |
| 18:15 | 0 | 0.0 | 127 ms | 0 |
| 18:30 | 0 | 0.0 | 169 ms | 0 |
| 18:45 | 0 | 0.0 | 184 ms | 0 |
| 19:00 | 0 | 0.0 | 122 ms | 0 |
| 19:15 | 0 | 0.0 | 91 ms | 0 |
| 19:30 | 0 | 0.0 | 236 ms | 0 |
| 19:45 | 0 | 0.0 | 180 ms | 0 |
| 20:00 | 0 | 0.0 | 158 ms | 0 |
| 20:15 | 0 | 0.0 | 114 ms | 0 |
| 20:30 | 0 | 0.0 | 141 ms | 0 |
| 20:45 | 0 | 0.0 | 79 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 1-800 Contacts 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 1-800 Contacts goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send 1-800 Contacts alerts to Slack, Discord or a webhook — free.
We track 1-800 Contacts (1800contacts.com) as part of the Health group. Live checks and user reports.
1-800 Contacts has no official status feed we can read, so this page relies on our own checks and user reports.
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 1 day of checks. No public incidents logged since monitoring began 1 day ago.
Response time over the last 24 hours: 249 ms average, 42–4500 ms range across 62 successful checks.
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
We have not recorded a public 1-800 Contacts incident since monitoring began 1 day ago.
From our own checks: 100% over 1 day of checks.
249 ms on average over the last 24 hours (42–4500 ms).
Not one we can read. This page uses independent checks of 1800contacts.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 1-800 Contacts here at once, the problem is on 1-800 Contacts's side.