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 2 hr ago. Last stored result reached it in 884 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 884 ms | 0 |
| Mon 23 | 0 | 0.0 | 727 ms | 0 |
| Tue 01 | 0 | 0.0 | 781 ms | 0 |
| Tue 03 | 0 | 0.0 | 760 ms | 0 |
| Tue 05 | 0 | 0.0 | 800 ms | 0 |
| Tue 07 | 0 | 0.0 | 714 ms | 0 |
| Tue 09 | 0 | 0.0 | 963 ms | 0 |
| Tue 11 | 0 | 0.0 | 893 ms | 0 |
| Tue 14 | 0 | 0.0 | 725 ms | 0 |
| Tue 16 | 0 | 0.0 | 914 ms | 0 |
| Tue 18 | 0 | 0.0 | 740 ms | 0 |
| Tue 20 | 0 | 0.0 | 815 ms | 0 |
| Tue 23 | 0 | 0.0 | 866 ms | 0 |
| Wed 01 | 0 | 0.0 | 1056 ms | 0 |
| Wed 03 | 0 | 0.0 | 820 ms | 0 |
| Wed 05 | 0 | 0.0 | 450 ms | 0 |
| Wed 08 | 0 | 0.0 | 799 ms | 0 |
| Wed 10 | 0 | 0.0 | 913 ms | 0 |
| Wed 12 | 0 | 0.0 | 880 ms | 0 |
| Wed 14 | 0 | 0.0 | 781 ms | 0 |
| Wed 16 | 0 | 0.0 | 725 ms | 0 |
| Wed 18 | 0 | 0.0 | 869 ms | 0 |
| Wed 21 | 0 | 0.0 | 782 ms | 0 |
| Wed 23 | 0 | 0.0 | 776 ms | 0 |
| Thu 01 | 0 | 0.0 | 745 ms | 0 |
| Thu 02 | 0 | 0.0 | 834 ms | 0 |
| Thu 04 | 0 | 0.0 | 939 ms | 0 |
| Thu 06 | 0 | 0.0 | 792 ms | 0 |
| Thu 08 | 0 | 0.0 | 878 ms | 0 |
| Thu 10 | 0 | 0.0 | 797 ms | 0 |
| Thu 12 | 0 | 0.0 | 747 ms | 0 |
| Thu 14 | 0 | 0.0 | 799 ms | 0 |
| Thu 16 | 0 | 0.0 | 953 ms | 0 |
| Thu 19 | 0 | 0.0 | 841 ms | 0 |
| Thu 21 | 0 | 0.0 | 699 ms | 0 |
| Thu 23 | 0 | 0.0 | 882 ms | 0 |
| Fri 01 | 0 | 0.0 | 1089 ms | 0 |
| Fri 03 | 0 | 0.0 | 817 ms | 0 |
| Fri 05 | 0 | 0.0 | 803 ms | 0 |
| Fri 07 | 0 | 0.0 | 891 ms | 0 |
| Fri 09 | 0 | 0.0 | 914 ms | 0 |
| Fri 11 | 0 | 0.0 | 708 ms | 0 |
| Fri 12 | 0 | 0.0 | 742 ms | 0 |
| Fri 14 | 0 | 0.0 | 667 ms | 0 |
| Fri 16 | 0 | 0.0 | 803 ms | 0 |
| Fri 18 | 0 | 0.0 | 807 ms | 0 |
| Fri 20 | 0 | 0.0 | 749 ms | 0 |
| Fri 22 | 0 | 0.0 | 884 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 SeriousMD 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 SeriousMD goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send SeriousMD alerts to Slack, Discord or a webhook — free.
SeriousMD, at seriousmd.com, is one of the Health services we monitor. Electronic Medical Records Software trusted by thousands of doctors in the Philippines. SeriousMD Doctors EMR helps you save time and manage your practice.
SeriousMD publishes an official status page at status.seriousmd.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: 823 ms average, 667–1089 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public SeriousMD incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
823 ms on average over the last 24 hours (667–1089 ms).
Yes, at https://status.seriousmd.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 SeriousMD here at once, the problem is on SeriousMD'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 SeriousMD. 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.