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 43 min ago. Last stored result reached it in 97 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 331 ms | 0 |
| Mon 14 | 0 | 0.0 | 206 ms | 0 |
| Mon 16 | 0 | 0.0 | 404 ms | 0 |
| Mon 18 | 0 | 0.0 | 142 ms | 0 |
| Mon 21 | 0 | 0.0 | 324 ms | 0 |
| Mon 23 | 0 | 0.0 | 147 ms | 0 |
| Tue 01 | 0 | 0.0 | 177 ms | 0 |
| Tue 03 | 0 | 0.0 | 229 ms | 0 |
| Tue 05 | 0 | 0.0 | 202 ms | 0 |
| Tue 07 | 0 | 0.0 | 424 ms | 0 |
| Tue 09 | 0 | 0.0 | 93 ms | 0 |
| Tue 11 | 0 | 0.0 | 308 ms | 0 |
| Tue 14 | 0 | 0.0 | 420 ms | 0 |
| Tue 16 | 0 | 0.0 | 186 ms | 0 |
| Tue 18 | 0 | 0.0 | 406 ms | 0 |
| Tue 20 | 0 | 0.0 | 218 ms | 0 |
| Tue 23 | 0 | 0.0 | 366 ms | 0 |
| Wed 01 | 0 | 0.0 | 249 ms | 0 |
| Wed 03 | 0 | 0.0 | 145 ms | 0 |
| Wed 05 | 0 | 0.0 | 239 ms | 0 |
| Wed 08 | 0 | 0.0 | 234 ms | 0 |
| Wed 10 | 0 | 0.0 | 370 ms | 0 |
| Wed 12 | 0 | 0.0 | 285 ms | 0 |
| Wed 14 | 0 | 0.0 | 331 ms | 0 |
| Wed 16 | 0 | 0.0 | 184 ms | 0 |
| Wed 18 | 0 | 0.0 | 159 ms | 0 |
| Wed 21 | 0 | 0.0 | 180 ms | 0 |
| Wed 23 | 0 | 0.0 | 206 ms | 0 |
| Thu 01 | 0 | 0.0 | 363 ms | 0 |
| Thu 03 | 0 | 0.0 | 384 ms | 0 |
| Thu 05 | 0 | 0.0 | 349 ms | 0 |
| Thu 07 | 0 | 0.0 | 334 ms | 0 |
| Thu 09 | 0 | 0.0 | 160 ms | 0 |
| Thu 11 | 0 | 0.0 | 387 ms | 0 |
| Thu 13 | 0 | 0.0 | 179 ms | 0 |
| Thu 16 | 0 | 0.0 | 366 ms | 0 |
| Thu 18 | 0 | 0.0 | 203 ms | 0 |
| Thu 20 | 0 | 0.0 | 351 ms | 0 |
| Thu 22 | 0 | 0.0 | 220 ms | 0 |
| Fri 00 | 0 | 0.0 | 242 ms | 0 |
| Fri 02 | 0 | 0.0 | 140 ms | 0 |
| Fri 04 | 0 | 0.0 | 147 ms | 0 |
| Fri 06 | 0 | 0.0 | 354 ms | 0 |
| Fri 08 | 0 | 0.0 | 329 ms | 0 |
| Fri 10 | 0 | 0.0 | 304 ms | 0 |
| Fri 12 | 0 | 0.0 | 248 ms | 0 |
| Fri 14 | 0 | 0.0 | 128 ms | 0 |
| Fri 16 | 0 | 0.0 | 97 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Simucase 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 Simucase goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Simucase alerts to Slack, Discord or a webhook — free.
Simucase is listed in our Health category and checked at simucase.com. Simucase combines the power of simulation-based learning with a comprehensive patient video library. Patented simulation technology allows users to observe, assess, diagnose, and provide intervention for virtual patients.
Simucase publishes an official status page at status.simucase.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 230 ms average, 97–354 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Simucase incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
230 ms on average over the last 24 hours (97–354 ms).
Yes, at https://status.simucase.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 Simucase here at once, the problem is on Simucase'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 Simucase. 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.