User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
doctolib.com · Money
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
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 3340 ms · 6 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 180 ms | 0 |
| 03:15 | 0 | 0.0 | 1316 ms | 0 |
| 03:30 | 0 | 0.0 | 1407 ms | 0 |
| 03:45 | 0 | 0.0 | 2174 ms | 0 |
| 04:00 | 0 | 0.0 | 1365 ms | 0 |
| 04:15 | 0 | 0.0 | 1751 ms | 0 |
| 04:30 | 0 | 0.0 | 1310 ms | 0 |
| 04:45 | 0 | 0.0 | 1177 ms | 0 |
| 05:00 | 0 | 0.0 | 236 ms | 0 |
| 05:15 | 0 | 0.0 | 1026 ms | 0 |
| 05:30 | 0 | 0.0 | 1866 ms | 0 |
| 05:45 | 0 | 0.0 | 1113 ms | 0 |
| 06:00 | 0 | 0.0 | 1070 ms | 0 |
| 06:15 | 0 | 0.0 | 509 ms | 0 |
| 06:30 | 0 | 0.0 | 1376 ms | 0 |
| 06:45 | 0 | 0.0 | 1224 ms | 0 |
| 07:00 | 0 | 0.0 | 2321 ms | 0 |
| 07:15 | 0 | 0.0 | 373 ms | 0 |
| 07:30 | 0 | 0.0 | 1546 ms | 0 |
| 07:45 | 0 | 0.0 | 310 ms | 0 |
| 08:00 | 0 | 0.0 | 519 ms | 0 |
| 08:15 | 0 | 0.0 | 1730 ms | 0 |
| 08:30 | 0 | 0.0 | 386 ms | 0 |
| 08:45 | 0 | 0.0 | 287 ms | 0 |
| 09:00 | 0 | 0.0 | 538 ms | 0 |
| 09:15 | 0 | 0.0 | 1807 ms | 0 |
| 09:30 | 0 | 0.0 | 432 ms | 0 |
| 09:45 | 0 | 0.0 | 444 ms | 0 |
| 10:00 | 0 | 0.0 | 1395 ms | 0 |
| 10:15 | 0 | 0.0 | 1075 ms | 0 |
| 10:30 | 0 | 0.0 | 1331 ms | 0 |
| 10:45 | 0 | 0.0 | 1155 ms | 0 |
| 11:00 | 0 | 0.0 | 1602 ms | 0 |
| 11:15 | 0 | 0.0 | 1417 ms | 0 |
| 11:30 | 0 | 0.0 | 1075 ms | 0 |
| 11:45 | 0 | 0.0 | 3130 ms | 0 |
| 12:00 | 0 | 0.0 | 1130 ms | 0 |
| 12:15 | 0 | 0.0 | 1863 ms | 0 |
| 12:30 | 0 | 0.0 | 234 ms | 0 |
| 12:45 | 0 | 0.0 | 1173 ms | 0 |
| 13:00 | 0 | 0.0 | 1344 ms | 0 |
| 13:15 | 0 | 0.0 | 1192 ms | 0 |
| 13:30 | 0 | 0.0 | 2161 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.
No outages on record for Doctolib 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 Doctolib goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Doctolib alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Doctolib is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Doctolib's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.