Docebo Outage History
6 incidents recorded over the last 365 days, 6 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Docebo Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 28, 2026 | Service disruption on login via SSO (Single-Sign-On)Mitigation for the Single-Sign-On service disruption has been applied across all the production environments and we're observing general improvements. We will continue to monitor the situation to ensure a total recovery. | 51 min | Resolved |
| Oct 21, 2026 | Learning Evaluation - Zoom and Webex integration Service DisruptionZoom and Webex integration services are now active. Our team is still actively working through mitigation steps for Learning Evaluation. We will send additional updates as available. | 9h 22m | Resolved |
| Oct 21, 2026 | Docebo Service DisruptionMitigation has been applied. We will continue to monitor the situation to ensure recovery. | 8h 45m | Resolved |
| Oct 6, 2026 | Docebo Service DisruptionWe are currently experiencing an intermittent service disruption impacting US East based customers. Our Cloud Operations team has identified the root cause and is implement a solution. We will send an additional update… | 1h 0m | Resolved |
| Sep 11, 2026 | Snowflake Service Outage in EU Central (eu-central-1)Region: eu-central-1 The third-party Snowflake incident has been resolved. The complete data refresh is going to be fully restored in a few hours. We will continue to monitor the situation to ensure recovery. | 3h 33m | Resolved |
| Sep 4, 2026 | Snowflake Service Outage in EU Central (eu-central-1)Region: eu-central-1 Snowflake has determined the root cause and mitigation efforts are underway. The mitigation has been applied. We will continue to monitor the situation to ensure recovery. | 2h 7m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Docebo incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Docebo Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Docebo acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Docebo outage in this window ran 9h 22m, against a mean recovery of 4h 16m. If you depend on Docebo in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.