User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Health
hopkinsmedicine.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 62 ms · 4 min ago.
No status feed
Johns Hopkins Medicine does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 13:45 | 0 | 0.0 | 280 ms | 0 |
| 14:00 | 0 | 0.0 | 308 ms | 0 |
| 14:15 | 0 | 0.0 | 194 ms | 0 |
| 14:30 | 0 | 0.0 | 154 ms | 0 |
| 14:45 | 0 | 0.0 | 159 ms | 0 |
| 15:00 | 0 | 0.0 | 236 ms | 0 |
| 15:15 | 0 | 0.0 | 382 ms | 0 |
| 15:30 | 0 | 0.0 | 300 ms | 0 |
| 15:45 | 0 | 0.0 | 213 ms | 0 |
| 16:00 | 0 | 0.0 | 190 ms | 0 |
| 16:15 | 0 | 0.0 | 164 ms | 0 |
| 16:30 | 0 | 0.0 | 117 ms | 0 |
| 16:45 | 0 | 0.0 | 118 ms | 0 |
| 17:00 | 0 | 0.0 | 153 ms | 0 |
| 17:15 | 0 | 0.0 | 225 ms | 0 |
| 17:30 | 0 | 0.0 | 255 ms | 0 |
| 17:45 | 0 | 0.0 | 384 ms | 0 |
| 18:00 | 0 | 0.0 | 87 ms | 0 |
| 18:15 | 0 | 0.0 | 412 ms | 0 |
| 18:30 | 0 | 0.0 | 325 ms | 0 |
| 18:45 | 0 | 0.0 | 122 ms | 0 |
| 19:00 | 0 | 0.0 | 126 ms | 0 |
| 19:15 | 0 | 0.0 | 304 ms | 0 |
| 19:30 | 0 | 0.0 | 216 ms | 0 |
| 19:45 | 0 | 0.0 | 303 ms | 0 |
| 20:00 | 0 | 0.0 | 172 ms | 0 |
| 20:15 | 0 | 0.0 | 211 ms | 0 |
| 20:30 | 0 | 0.0 | 191 ms | 0 |
| 20:45 | 0 | 0.0 | 202 ms | 0 |
| 21:00 | 0 | 0.0 | 227 ms | 0 |
| 21:15 | 0 | 0.0 | 413 ms | 0 |
| 21:30 | 0 | 0.0 | 251 ms | 0 |
| 21:45 | 0 | 0.0 | 80 ms | 0 |
| 22:00 | 0 | 0.0 | 182 ms | 0 |
| 22:15 | 0 | 0.0 | 436 ms | 0 |
| 22:30 | 0 | 0.0 | 156 ms | 0 |
| 22:45 | 0 | 0.0 | 167 ms | 0 |
| 23:00 | 0 | 0.0 | 198 ms | 0 |
| 23:15 | 0 | 0.0 | 255 ms | 0 |
| 23:30 | 0 | 0.0 | 38 ms | 0 |
| 23:45 | 0 | 0.0 | 289 ms | 0 |
| 00:00 | 0 | 0.0 | 172 ms | 0 |
| 00:15 | 0 | 0.0 | 202 ms | 0 |
| 00:30 | 0 | 0.0 | 187 ms | 0 |
| 00:45 | 0 | 0.0 | 152 ms | 0 |
| 01:00 | 0 | 0.0 | 487 ms | 0 |
| 01:15 | 0 | 0.0 | 102 ms | 0 |
| 01:30 | 0 | 0.0 | 46 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 Johns Hopkins Medicine 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 Johns Hopkins Medicine goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Johns Hopkins Medicine alerts to Slack, Discord or a webhook — free.
Johns Hopkins Medicine, at hopkinsmedicine.org, is one of the Health services we monitor. Live checks and user reports.
Johns Hopkins Medicine has no official status feed we can read, so this page relies on our own checks and user reports.
Typical issues 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 2 days of checks. No public incidents logged since monitoring began 2 days ago.
Response time over the last 24 hours: 213 ms average, 9–663 ms range across 98 successful checks.
Checks are succeeding and user reports are near the baseline.
We have not recorded a public Johns Hopkins Medicine incident since monitoring began 2 days ago.
From our own checks: 100% over 2 days of checks.
213 ms on average over the last 24 hours (9–663 ms).
Not one we can read. This page uses independent checks of hopkinsmedicine.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 Johns Hopkins Medicine here at once, the problem is on Johns Hopkins Medicine's side.