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 1 hr ago. Last stored result reached it in 341 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 365 ms | 0 |
| Mon 18 | 0 | 0.0 | 249 ms | 0 |
| Mon 21 | 0 | 0.0 | 497 ms | 0 |
| Mon 23 | 0 | 0.0 | 394 ms | 0 |
| Tue 01 | 0 | 0.0 | 378 ms | 0 |
| Tue 03 | 0 | 0.0 | 388 ms | 0 |
| Tue 05 | 0 | 0.0 | 370 ms | 0 |
| Tue 07 | 0 | 0.0 | 283 ms | 0 |
| Tue 09 | 0 | 0.0 | 378 ms | 0 |
| Tue 11 | 0 | 0.0 | 303 ms | 0 |
| Tue 14 | 0 | 0.0 | 398 ms | 0 |
| Tue 16 | 0 | 0.0 | 416 ms | 0 |
| Tue 18 | 0 | 0.0 | 202 ms | 0 |
| Tue 20 | 0 | 0.0 | 427 ms | 0 |
| Tue 23 | 0 | 0.0 | 276 ms | 0 |
| Wed 01 | 0 | 0.0 | 307 ms | 0 |
| Wed 03 | 0 | 0.0 | 278 ms | 0 |
| Wed 05 | 0 | 0.0 | 285 ms | 0 |
| Wed 07 | 0 | 0.0 | 372 ms | 0 |
| Wed 10 | 0 | 0.0 | 359 ms | 0 |
| Wed 12 | 0 | 0.0 | 247 ms | 0 |
| Wed 14 | 0 | 0.0 | 332 ms | 0 |
| Wed 16 | 0 | 0.0 | 431 ms | 0 |
| Wed 18 | 0 | 0.0 | 376 ms | 0 |
| Wed 21 | 0 | 0.0 | 437 ms | 0 |
| Wed 23 | 0 | 0.0 | 356 ms | 0 |
| Thu 01 | 0 | 0.0 | 287 ms | 0 |
| Thu 03 | 0 | 0.0 | 247 ms | 0 |
| Thu 05 | 0 | 0.0 | 405 ms | 0 |
| Thu 07 | 0 | 0.0 | 344 ms | 0 |
| Thu 09 | 0 | 0.0 | 273 ms | 0 |
| Thu 11 | 0 | 0.0 | 364 ms | 0 |
| Thu 13 | 0 | 0.0 | 338 ms | 0 |
| Thu 15 | 0 | 0.0 | 244 ms | 0 |
| Thu 17 | 0 | 0.0 | 260 ms | 0 |
| Thu 20 | 0 | 0.0 | 334 ms | 0 |
| Thu 22 | 0 | 0.0 | 243 ms | 0 |
| Fri 00 | 0 | 0.0 | 357 ms | 0 |
| Fri 02 | 0 | 0.0 | 393 ms | 0 |
| Fri 04 | 0 | 0.0 | 376 ms | 0 |
| Fri 06 | 0 | 0.0 | 382 ms | 0 |
| Fri 08 | 0 | 0.0 | 718 ms | 0 |
| Fri 10 | 0 | 0.0 | 453 ms | 0 |
| Fri 12 | 0 | 0.0 | 242 ms | 0 |
| Fri 14 | 0 | 0.0 | 337 ms | 0 |
| Fri 16 | 0 | 0.0 | 335 ms | 0 |
| Fri 18 | 0 | 0.0 | 364 ms | 0 |
| Fri 19 | 0 | 0.0 | 338 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 Medchat 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 Medchat goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Medchat alerts to Slack, Discord or a webhook — free.
Medchat, at medchatapp.com, is one of the Health services we monitor. Medchat·ai's AI agent platform automates healthcare workflows across providers, payers, life sciences & public health. Build intelligent automation for patient communication, operations & support with no-code tools.
Medchat publishes an official status page at status.medchatapp.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: 375 ms average, 242–718 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Medchat incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
375 ms on average over the last 24 hours (242–718 ms).
Yes, at https://status.medchatapp.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 Medchat here at once, the problem is on Medchat'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 Medchat. 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.