User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Health
amwell.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 826 ms · 3 min ago.
No status feed
Amwell does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 12:30 | 0 | 0.0 | 554 ms | 0 |
| 12:45 | 0 | 0.0 | 921 ms | 0 |
| 13:00 | 0 | 0.0 | 569 ms | 1 |
| 13:15 | 0 | 0.0 | 504 ms | 0 |
| 13:30 | 0 | 0.0 | 548 ms | 0 |
| 13:45 | 0 | 0.0 | 620 ms | 0 |
| 14:00 | 0 | 0.0 | 655 ms | 1 |
| 14:15 | 0 | 0.0 | — | 2 |
| 14:30 | 0 | 0.0 | 716 ms | 0 |
| 14:45 | 0 | 0.0 | 347 ms | 1 |
| 15:00 | 0 | 0.0 | 744 ms | 0 |
| 15:15 | 0 | 0.0 | 806 ms | 0 |
| 15:30 | 0 | 0.0 | 902 ms | 0 |
| 15:45 | 0 | 0.0 | — | 1 |
| 16:00 | 0 | 0.0 | 720 ms | 1 |
| 16:15 | 0 | 0.0 | — | 2 |
| 16:30 | 0 | 0.0 | — | 2 |
| 16:45 | 0 | 0.0 | — | 2 |
| 17:00 | 0 | 0.0 | — | 2 |
| 17:15 | 0 | 0.0 | 706 ms | 1 |
| 17:30 | 0 | 0.0 | — | 2 |
| 17:45 | 0 | 0.0 | 655 ms | 0 |
| 18:00 | 0 | 0.0 | 368 ms | 1 |
| 18:15 | 0 | 0.0 | 788 ms | 1 |
| 18:30 | 0 | 0.0 | 656 ms | 0 |
| 18:45 | 0 | 0.0 | 343 ms | 1 |
| 19:00 | 0 | 0.0 | 775 ms | 1 |
| 19:15 | 0 | 0.0 | 688 ms | 0 |
| 19:30 | 0 | 0.0 | 530 ms | 1 |
| 19:45 | 0 | 0.0 | 834 ms | 0 |
| 20:00 | 0 | 0.0 | 1454 ms | 1 |
| 20:15 | 0 | 0.0 | 682 ms | 1 |
| 20:30 | 0 | 0.0 | 866 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.
| Started | Peak | Duration | Status | Details |
|---|---|---|---|---|
| 2026-11-04 16:24 UTC | outage | 1 h 4 min | Resolved | Details → |
One report per service every 10 minutes from this network. No account.
Get an email when Amwell goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Amwell alerts to Slack, Discord or a webhook — free.
Amwell is listed in our Health category and checked at amwell.com. Live checks and user reports.
Amwell 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: 56.90% over 1 day of checks. We logged 1 public incident since monitoring began 1 day ago.
Response time over the last 24 hours: 703 ms average, 343–1454 ms range across 36 successful checks.
Checks are succeeding and user reports are near the baseline.
The most recent public incident we recorded started 2026-11-04 and lasted 1 h 4 min. 1 incident since monitoring began 1 day ago.
From our own checks: 56.90% over 1 day of checks.
703 ms on average over the last 24 hours (343–1454 ms).
Not one we can read. This page uses independent checks of amwell.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 Amwell here at once, the problem is on Amwell's side.