Is Doctolib down?
Last checked 2m agoNo incidents right now.
Doctolib is operational right now. Last checked 2m ago; the most recent incident resolved 8d ago.
Real-time Doctolib status, recent outages, and incident history — pulled directly from Doctolib's official status page at https://status.doctolib.com every 5 minutes. Pingoru tracks 12 Doctolib services and has captured 9 incidents in the last 90 days (97.69% uptime). Get email, Slack, Discord, or webhook alerts the moment Doctolib reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Calendar
Timeline · 4 updates
- identified · Jun 05, 2026, 02:03 PM UTC
The cause of the performance issue affecting the following component has been identified. Corrective actions are underway to restore full performance. — Your Doctolib Team
- identified · Jun 05, 2026, 02:18 PM UTC
The cause of the performance issue affecting the following component has been identified. Corrective actions are underway to restore full performance. — Your Doctolib Team
- monitoring · Jun 05, 2026, 02:22 PM UTC
Performance has returned to normal for the following component. There is no longer any user impact. We are monitoring to ensure continued stability. — Your Doctolib Team
- resolved · Jun 05, 2026, 02:26 PM UTC
The performance incident affecting the following component has been fully resolved: All services are stable and operating normally. We apologize for the inconvenience and thank you for your patience. — Your Doctolib Team
Latest: The performance incident affecting the following component has been fully resolved: All services are stable and operating normally. We apologize for the inconvenience and thank you…
-
- Phone assistantClinical software
Timeline · 4 updates
- identified · May 29, 2026, 03:11 PM UTC
We are investigating a performance issue affecting the following components. Some users may experience slower response times or intermittent instability. We understand how important reliability is in your daily practice and are working with high priority. — Your Doctolib Team
- identified · May 29, 2026, 03:23 PM UTC
We are continuing to work on a fix for this issue.
- monitoring · May 29, 2026, 03:49 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved · May 30, 2026, 01:43 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Phone assistant
Timeline · 5 updates
- identified · May 29, 2026, 11:42 AM UTC
The cause of the performance issue affecting the following component has been identified. Corrective actions are underway to restore full performance. — Your Doctolib Team
- identified · May 29, 2026, 12:02 PM UTC
The cause of the performance issue affecting the following component has been identified. Corrective actions are underway to restore full performance. — Your Doctolib Team
- identified · May 29, 2026, 12:12 PM UTC
The cause of the performance issue affecting the following component has been identified. Corrective actions are underway to restore full performance. — Your Doctolib Team
- monitoring · May 29, 2026, 12:38 PM UTC
Performance has returned to normal for the following component. There is no longer any user impact. We are monitoring to ensure continued stability. — Your Doctolib Team
- resolved · May 29, 2026, 12:43 PM UTC
The performance incident affecting the following component has been fully resolved: All services are stable and operating normally. We apologize for the inconvenience and thank you for your patience. — Your Doctolib Team
Latest: The performance incident affecting the following component has been fully resolved: All services are stable and operating normally. We apologize for the inconvenience and thank you…
-
- Clinical software
Timeline · 3 updates
- identified · May 20, 2026, 03:28 PM UTC
The cause of the performance issue affecting the following component has been identified. Corrective actions are underway to restore full performance. — Your Doctolib Team
- monitoring · May 20, 2026, 03:38 PM UTC
Performance has returned to normal for the following component. There is no longer any user impact. We are monitoring to ensure continued stability. — Your Doctolib Team
- resolved · May 20, 2026, 03:44 PM UTC
The performance incident affecting the following component has been fully resolved: All services are stable and operating normally. We apologize for the inconvenience and thank you for your patience. — Your Doctolib Team
Latest: The performance incident affecting the following component has been fully resolved: All services are stable and operating normally. We apologize for the inconvenience and thank you…
-
- Calendar
Timeline · 4 updates
- identified · May 06, 2026, 06:54 AM UTC
The issue has been identified and a fix is being implemented.
- identified · May 06, 2026, 07:01 AM UTC
We are continuing to work on a fix for this issue.
- monitoring · May 06, 2026, 07:28 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved · May 06, 2026, 07:33 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
See the full Doctolib outage history
4 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Doctolib outage history →Or sign up free to get alerts when Doctolib breaks · 10 free monitors · No credit card
- Started Jun 05, 2026, 02:03 PM UTC · Resolved Jun 05, 2026, 02:26 PM UTC · 22m
- Components impacted: Phone Assistant ResolvedStarted May 29, 2026, 03:11 PM UTC · Resolved May 30, 2026, 01:43 PM UTC · 22h 32m
- Started May 29, 2026, 11:42 AM UTC · Resolved May 29, 2026, 12:43 PM UTC · 1h
- Started May 20, 2026, 03:28 PM UTC · Resolved May 20, 2026, 03:44 PM UTC · 16m
- Started May 06, 2026, 06:54 AM UTC · Resolved May 06, 2026, 07:33 AM UTC · 39m
- Started May 05, 2026, 07:57 AM UTC · Resolved May 05, 2026, 08:59 AM UTC · 1h 1m
- Components impacted: Phone Assistant ResolvedStarted Apr 22, 2026, 08:45 AM UTC · Resolved Apr 22, 2026, 09:45 AM UTC · 1h
- Components impacted: All ResolvedStarted Apr 10, 2026, 01:21 PM UTC · Resolved Apr 10, 2026, 02:43 PM UTC · 1h 22m