User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Health
stanfordhealthcare.org · 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 301 ms · 3 min ago.
No status feed
Stanford Health Care does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 13:45 | 0 | 0.0 | 503 ms | 0 |
| 14:00 | 0 | 0.0 | 939 ms | 0 |
| 14:15 | 0 | 0.0 | 383 ms | 0 |
| 14:30 | 0 | 0.0 | 287 ms | 0 |
| 14:45 | 0 | 0.0 | 248 ms | 0 |
| 15:00 | 0 | 0.0 | 355 ms | 0 |
| 15:15 | 0 | 0.0 | 463 ms | 0 |
| 15:30 | 0 | 0.0 | 290 ms | 0 |
| 15:45 | 0 | 0.0 | 662 ms | 0 |
| 16:00 | 0 | 0.0 | 430 ms | 0 |
| 16:15 | 0 | 0.0 | 144 ms | 0 |
| 16:30 | 0 | 0.0 | 697 ms | 0 |
| 16:45 | 0 | 0.0 | 282 ms | 0 |
| 17:00 | 0 | 0.0 | 840 ms | 0 |
| 17:15 | 0 | 0.0 | 155 ms | 0 |
| 17:30 | 0 | 0.0 | 359 ms | 0 |
| 17:45 | 0 | 0.0 | 732 ms | 0 |
| 18:00 | 0 | 0.0 | 718 ms | 0 |
| 18:15 | 0 | 0.0 | 168 ms | 0 |
| 18:30 | 0 | 0.0 | 665 ms | 0 |
| 18:45 | 0 | 0.0 | 160 ms | 0 |
| 19:00 | 0 | 0.0 | 316 ms | 0 |
| 19:15 | 0 | 0.0 | 382 ms | 0 |
| 19:30 | 0 | 0.0 | 484 ms | 0 |
| 19:45 | 0 | 0.0 | 890 ms | 0 |
| 20:00 | 0 | 0.0 | 776 ms | 0 |
| 20:15 | 0 | 0.0 | 689 ms | 0 |
| 20:30 | 0 | 0.0 | 756 ms | 0 |
| 20:45 | 0 | 0.0 | 733 ms | 0 |
| 21:00 | 0 | 0.0 | 814 ms | 0 |
| 21:15 | 0 | 0.0 | 798 ms | 0 |
| 21:30 | 0 | 0.0 | 240 ms | 0 |
| 21:45 | 0 | 0.0 | 414 ms | 0 |
| 22:00 | 0 | 0.0 | 1073 ms | 0 |
| 22:15 | 0 | 0.0 | 672 ms | 0 |
| 22:30 | 0 | 0.0 | 476 ms | 0 |
| 22:45 | 0 | 0.0 | 440 ms | 0 |
| 23:00 | 0 | 0.0 | 580 ms | 0 |
| 23:15 | 0 | 0.0 | 1010 ms | 0 |
| 23:30 | 0 | 0.0 | 155 ms | 0 |
| 23:45 | 0 | 0.0 | 242 ms | 0 |
| 00:00 | 0 | 0.0 | 375 ms | 0 |
| 00:15 | 0 | 0.0 | 1204 ms | 0 |
| 00:30 | 0 | 0.0 | 265 ms | 0 |
| 00:45 | 0 | 0.0 | 331 ms | 0 |
| 01:00 | 0 | 0.0 | 217 ms | 0 |
| 01:15 | 0 | 0.0 | 513 ms | 0 |
| 01:30 | 0 | 0.0 | 559 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 2 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Stanford Health Care 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 Stanford Health Care goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Stanford Health Care alerts to Slack, Discord or a webhook — free.
We track Stanford Health Care (stanfordhealthcare.org) as part of the Health group. Live checks and user reports.
Stanford Health Care 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 2 days of checks. No public incidents logged since monitoring began 2 days ago.
Response time over the last 24 hours: 510 ms average, 46–1419 ms range across 100 successful checks.
Checks are succeeding and user reports are near the baseline.
We have not recorded a public Stanford Health Care incident since monitoring began 2 days ago.
From our own checks: 100% over 2 days of checks.
510 ms on average over the last 24 hours (46–1419 ms).
Not one we can read. This page uses independent checks of stanfordhealthcare.org 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 Stanford Health Care here at once, the problem is on Stanford Health Care's side.