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 8 min ago. Last stored result reached it in 69 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 05 | 0 | 0.0 | 111 ms | 0 |
| Tue 07 | 0 | 0.0 | 383 ms | 0 |
| Tue 09 | 0 | 0.0 | 153 ms | 0 |
| Tue 11 | 0 | 0.0 | 100 ms | 0 |
| Tue 14 | 0 | 0.0 | 118 ms | 0 |
| Tue 16 | 0 | 0.0 | 160 ms | 0 |
| Tue 18 | 0 | 0.0 | 386 ms | 0 |
| Tue 20 | 0 | 0.0 | 245 ms | 0 |
| Tue 23 | 0 | 0.0 | 126 ms | 0 |
| Wed 01 | 0 | 0.0 | 190 ms | 0 |
| Wed 03 | 0 | 0.0 | 237 ms | 0 |
| Wed 05 | 0 | 0.0 | 137 ms | 0 |
| Wed 07 | 0 | 0.0 | 120 ms | 0 |
| Wed 08 | 0 | 0.0 | 33 ms | 0 |
| Wed 10 | 0 | 0.0 | 111 ms | 0 |
| Wed 12 | 0 | 0.0 | 119 ms | 0 |
| Wed 14 | 0 | 0.0 | 79 ms | 0 |
| Wed 16 | 0 | 0.0 | 432 ms | 0 |
| Wed 18 | 0 | 0.0 | 332 ms | 0 |
| Wed 20 | 0 | 0.0 | 332 ms | 0 |
| Wed 22 | 0 | 0.0 | 115 ms | 0 |
| Thu 00 | 0 | 0.0 | 93 ms | 0 |
| Thu 02 | 0 | 0.0 | 151 ms | 0 |
| Thu 04 | 0 | 0.0 | 254 ms | 0 |
| Thu 06 | 0 | 0.0 | 77 ms | 0 |
| Thu 08 | 0 | 0.0 | 214 ms | 0 |
| Thu 10 | 0 | 0.0 | 141 ms | 0 |
| Thu 13 | 0 | 0.0 | 487 ms | 0 |
| Thu 15 | 0 | 0.0 | 97 ms | 0 |
| Thu 17 | 0 | 0.0 | 237 ms | 0 |
| Thu 19 | 0 | 0.0 | 102 ms | 0 |
| Thu 21 | 0 | 0.0 | 130 ms | 0 |
| Thu 23 | 0 | 0.0 | 87 ms | 0 |
| Fri 01 | 0 | 0.0 | 100 ms | 0 |
| Fri 03 | 0 | 0.0 | 129 ms | 0 |
| Fri 05 | 0 | 0.0 | 315 ms | 0 |
| Fri 06 | 0 | 0.0 | 199 ms | 0 |
| Fri 08 | 0 | 0.0 | 154 ms | 0 |
| Fri 10 | 0 | 0.0 | 462 ms | 0 |
| Fri 12 | 0 | 0.0 | 115 ms | 0 |
| Fri 14 | 0 | 0.0 | 110 ms | 0 |
| Fri 16 | 0 | 0.0 | 157 ms | 0 |
| Fri 18 | 0 | 0.0 | 122 ms | 0 |
| Fri 20 | 0 | 0.0 | 291 ms | 0 |
| Fri 22 | 0 | 0.0 | 333 ms | 0 |
| Sat 00 | 0 | 0.0 | 357 ms | 0 |
| Sat 02 | 0 | 0.0 | 85 ms | 0 |
| Sat 03 | 0 | 0.0 | 110 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 MediPulse 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 MediPulse goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send MediPulse alerts to Slack, Discord or a webhook — free.
MediPulse is listed in our Health category and checked at medipulse.de. Die Software für Praxisfinanzen und MVZ-Management: Echtzeitdaten, automatisiertes Praxiscontrolling und klare Handlungsempfehlungen für Arztpraxen und MVZs.
MediPulse publishes an official status page at status.medipulse.de; when we can read it, its incident level is folded into the status shown here.
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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 212 ms average, 69–504 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public MediPulse incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
212 ms on average over the last 24 hours (69–504 ms).
Yes, at https://status.medipulse.de.
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 MediPulse here at once, the problem is on MediPulse'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 MediPulse. 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.