- Detected by Pingoru
- Sep 25, 2026, 09:33 AM UTC
- Resolved
- Sep 25, 2026, 11:04 AM UTC
- Duration
- 1h 30m
Affected: Telehealth
Timeline · 3 updates
-
investigating Sep 25, 2026, 09:33 AM UTC
We are investigating a performance issue affecting the following component. 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
-
monitoring Sep 25, 2026, 09:59 AM 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 Sep 25, 2026, 11:04 AM 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
Read the full incident report →
Critical September 16, 2026 - Detected by Pingoru
- Sep 16, 2026, 08:47 AM UTC
- Resolved
- Sep 16, 2026, 12:32 PM UTC
- Duration
- 3h 45m
Affected: Support Doctolib
Timeline · 6 updates
-
investigating Sep 16, 2026, 08:47 AM UTC
We are currently investigating this issue.
-
identified Sep 16, 2026, 09:06 AM UTC
The issue has been identified and a fix is being implemented.
-
identified Sep 16, 2026, 09:17 AM UTC
We are continuing to work on a fix for this issue.
-
identified Sep 16, 2026, 09:53 AM UTC
We are continuing to work on a fix for this issue.
-
monitoring Sep 16, 2026, 11:36 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 16, 2026, 12:32 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 11, 2026, 04:25 PM UTC
- Resolved
- Sep 11, 2026, 04:33 PM UTC
- Duration
- 8m
Affected: Phone assistantClinical software
Timeline · 5 updates
-
investigating Sep 11, 2026, 03:41 PM UTC
We are currently investigating this issue.
-
investigating Sep 11, 2026, 03:46 PM UTC
We are continuing to investigate this issue.
-
investigating Sep 11, 2026, 04:04 PM UTC
We are continuing to investigate this issue.
-
monitoring Sep 13, 2026, 01:32 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 13, 2026, 01:32 AM UTC
This incident has been resolved.
Read the full incident report →
Critical September 8, 2026 - Detected by Pingoru
- Sep 08, 2026, 01:09 PM UTC
- Resolved
- Sep 08, 2026, 02:08 PM UTC
- Duration
- 58m
Affected: CalendarTask managerMy activityPhone assistantPatient ManagementTelehealthPatient messagingDoctolib ConnectClinical softwarePatient billingConnection with medical deviceSupport Doctolib
Timeline · 6 updates
-
investigating Sep 08, 2026, 01:09 PM UTC
We are currently investigating a complete service interruption affecting the following components. We understand how critical uninterrupted access is for delivering care. Our teams are fully mobilized and treating this with the highest priority. We will keep you closely informed. — Your Doctolib Team
-
identified Sep 08, 2026, 01:22 PM UTC
The root cause of the service interruption affecting the following components has been identified. Restoration efforts are actively underway. We know this situation can create significant pressure for healthcare teams, and we are prioritizing safe and rapid recovery. Further updates will follow. — Your Doctolib Team
-
monitoring Sep 08, 2026, 01:24 PM UTC
Service has been restored for the following components. Access is fully operational. We are closely monitoring the system to ensure continued stability. — Your Doctolib Team
-
identified Sep 08, 2026, 01:29 PM UTC
The root cause of the service interruption affecting the following components has been identified. Restoration efforts are actively underway. We know this situation can create significant pressure for healthcare teams, and we are prioritizing safe and rapid recovery. Further updates will follow. — Your Doctolib Team
-
monitoring Sep 08, 2026, 01:58 PM UTC
Service has been restored for the following components. Access is fully operational. We are closely monitoring the system to ensure continued stability. — Your Doctolib Team
-
resolved Sep 08, 2026, 02:08 PM UTC
The performance incident affecting the following components 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
Read the full incident report →
Critical September 1, 2026 - Detected by Pingoru
- Sep 01, 2026, 04:05 PM UTC
- Resolved
- Sep 01, 2026, 05:28 PM UTC
- Duration
- 1h 23m
Affected: Patient billing
Timeline · 4 updates
-
investigating Sep 01, 2026, 04:05 PM UTC
We are currently investigating this issue.
-
identified Sep 01, 2026, 04:05 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Sep 01, 2026, 04:48 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 01, 2026, 05:28 PM UTC
This incident has been resolved.
Read the full incident report →
Critical September 1, 2026 - Detected by Pingoru
- Sep 01, 2026, 09:38 AM UTC
- Resolved
- Sep 01, 2026, 09:52 AM UTC
- Duration
- 14m
Affected: Clinical software
Timeline · 4 updates
-
investigating Sep 01, 2026, 09:38 AM UTC
We are currently investigating this issue.
-
identified Sep 01, 2026, 09:39 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Sep 01, 2026, 09:45 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 01, 2026, 09:52 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 28, 2026, 11:02 AM UTC
- Resolved
- Aug 28, 2026, 12:01 PM UTC
- Duration
- 59m
Affected: Clinical software
Timeline · 6 updates
-
investigating Aug 28, 2026, 11:02 AM UTC
We are currently investigating this issue.
-
identified Aug 28, 2026, 11:02 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Aug 28, 2026, 11:03 AM UTC
A fix has been implemented and we are monitoring the results.
-
identified Aug 28, 2026, 11:04 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Aug 28, 2026, 11:47 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Aug 28, 2026, 12:01 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 18, 2026, 03:24 PM UTC
- Resolved
- Aug 18, 2026, 03:51 PM UTC
- Duration
- 26m
Affected: Clinical software
Timeline · 3 updates
-
identified Aug 18, 2026, 03:24 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Aug 18, 2026, 03:30 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Aug 18, 2026, 03:51 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 04, 2026, 02:44 PM UTC
- Resolved
- Aug 05, 2026, 07:05 AM UTC
- Duration
- 16h 21m
Affected: Calendar
Timeline · 5 updates
-
investigating Aug 04, 2026, 02:44 PM UTC
We are investigating a performance issue affecting the following component. 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
-
investigating Aug 04, 2026, 02:53 PM UTC
We are investigating a performance issue affecting the following component. 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 Aug 04, 2026, 02:56 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Aug 04, 2026, 06:57 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Aug 05, 2026, 07:05 AM 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
Read the full incident report →
- Detected by Pingoru
- Jul 28, 2026, 08:54 AM UTC
- Resolved
- Jul 28, 2026, 11:01 AM UTC
- Duration
- 2h 6m
Affected: Clinical software
Timeline · 6 updates
-
investigating Jul 28, 2026, 08:54 AM UTC
We are currently investigating this issue.
-
identified Jul 28, 2026, 09:02 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jul 28, 2026, 09:12 AM UTC
A fix has been implemented and we are monitoring the results.
-
identified Jul 28, 2026, 09:34 AM UTC
The issue has been identified and a fix is being implemented.
-
identified Jul 28, 2026, 09:50 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
-
resolved Jul 28, 2026, 11:01 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 16, 2026, 07:30 AM UTC
- Resolved
- Jul 16, 2026, 08:17 AM UTC
- Duration
- 46m
Affected: Clinical software
Timeline · 3 updates
-
investigating Jul 16, 2026, 07:30 AM UTC
We're experiencing high errors on Consultation assistant
-
investigating Jul 16, 2026, 07:40 AM UTC
We are continuing to investigate this issue.
-
resolved Jul 16, 2026, 08:17 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 30, 2026, 10:18 AM UTC
- Resolved
- Jun 30, 2026, 10:36 AM UTC
- Duration
- 17m
Affected: CalendarPatient ManagementClinical software
Timeline · 2 updates
-
identified Jun 30, 2026, 10:18 AM UTC
The cause of the performance issue affecting the following components has been identified. Corrective actions are underway to restore full performance. — Your Doctolib Team
-
resolved Jun 30, 2026, 10:36 AM UTC
The performance incident affecting the following components 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
Read the full incident report →
- Detected by Pingoru
- Jun 25, 2026, 01:49 PM UTC
- Resolved
- Jun 25, 2026, 02:38 PM UTC
- Duration
- 48m
Affected: Phone assistant
Timeline · 4 updates
-
identified Jun 25, 2026, 01:49 PM UTC
The issue has been identified and a fix is being implemented.
-
identified Jun 25, 2026, 01:50 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring Jun 25, 2026, 02:32 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 25, 2026, 02:38 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 23, 2026, 12:58 PM UTC
- Resolved
- Jun 23, 2026, 01:07 PM UTC
- Duration
- 8m
Affected: Phone assistant
Timeline · 2 updates
-
monitoring Jun 23, 2026, 12:58 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 23, 2026, 01:07 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
Read the full incident report →
- Detected by Pingoru
- Jun 05, 2026, 02:03 PM UTC
- Resolved
- Jun 05, 2026, 02:26 PM UTC
- Duration
- 22m
Affected: 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
Read the full incident report →
- Detected by Pingoru
- May 29, 2026, 03:11 PM UTC
- Resolved
- May 30, 2026, 01:43 PM UTC
- Duration
- 22h 32m
Affected: 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.
Read the full incident report →
- Detected by Pingoru
- May 29, 2026, 11:42 AM UTC
- Resolved
- May 29, 2026, 12:43 PM UTC
- Duration
- 1h
Affected: 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
Read the full incident report →
- Detected by Pingoru
- May 20, 2026, 03:28 PM UTC
- Resolved
- May 20, 2026, 03:44 PM UTC
- Duration
- 16m
Affected: 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
Read the full incident report →
- Detected by Pingoru
- May 06, 2026, 06:54 AM UTC
- Resolved
- May 06, 2026, 07:33 AM UTC
- Duration
- 39m
Affected: 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.
Read the full incident report →
- Detected by Pingoru
- May 05, 2026, 07:57 AM UTC
- Resolved
- May 05, 2026, 08:59 AM UTC
- Duration
- 1h 1m
Affected: Clinical software
Timeline · 5 updates
-
identified May 05, 2026, 07:57 AM 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 05, 2026, 08:13 AM UTC
We are continuing to work on a fix for this issue.
-
identified May 05, 2026, 08:26 AM UTC
Work continues to improve performance of the following component. Stabilization efforts are ongoing. — Your Doctolib Team
-
identified May 05, 2026, 08:43 AM UTC
Work continues to improve performance of the following component. Stabilization efforts are ongoing. — Your Doctolib Team
-
resolved May 05, 2026, 08:59 AM 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
Read the full incident report →
- Detected by Pingoru
- Apr 10, 2026, 01:21 PM UTC
- Resolved
- Apr 10, 2026, 02:43 PM UTC
- Duration
- 1h 22m
Affected: CalendarTask managerMy activityPhone assistantPatient ManagementTelehealthPatient messagingDoctolib ConnectClinical softwarePatient billingConnection with medical deviceSupport Doctolib
Timeline · 5 updates
-
identified Apr 10, 2026, 01:21 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
-
monitoring Apr 10, 2026, 01:39 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
-
identified Apr 10, 2026, 01:57 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Apr 10, 2026, 02:15 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 10, 2026, 02: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
Read the full incident report →
- Detected by Pingoru
- Apr 07, 2026, 12:09 PM UTC
- Resolved
- Apr 07, 2026, 12:23 PM UTC
- Duration
- 14m
Affected: Clinical softwarePatient billing
Timeline · 3 updates
-
investigating Apr 07, 2026, 12:09 PM UTC
We are investigating a performance issue affecting the following componentss. 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
-
monitoring Apr 07, 2026, 12:14 PM UTC
Performance has returned to normal for the following components. There is no longer any user impact. We are monitoring to ensure continued stability. — Your Doctolib Team
-
resolved Apr 07, 2026, 12:23 PM UTC
The performance incident affecting the following components 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
Read the full incident report →
- Detected by Pingoru
- Dec 05, 2025, 09:51 AM UTC
- Resolved
- Dec 05, 2025, 12:18 PM UTC
- Duration
- 2h 27m
Timeline · 3 updates
-
investigating Dec 05, 2025, 09:51 AM UTC
We're currently experiencing a technical incident that may prevent you from using our Doctolib Connect. We'll share updates on the resolution progress here. We apologize for any inconvenience caused, and appreciate your patience as our teams are working on fixing the issue as soon as possible.
-
identified Dec 05, 2025, 09:54 AM UTC
We have applied a fix and are monitoring the results. We'll be back with an update soon to confirm that Doctolib Siilo is back to normal for everyone.
-
resolved Dec 05, 2025, 12:18 PM UTC
Doctolib fonctionne à nouveau normalement pour tout le monde. --- Doctolib ist wieder für alle Nutzer:innen verfügbar. --- Doctolib funziona per tutti gli utenti.
Read the full incident report →
Critical December 5, 2025 - Detected by Pingoru
- Dec 05, 2025, 09:04 AM UTC
- Resolved
- Dec 05, 2025, 09:55 AM UTC
- Duration
- 51m
Timeline · 3 updates
Read the full incident report →