Issue with our upstream provider

Our upstream provider, AWS, is currently experiencing an outage affecting multiple services in all the regions, which is causing a broader impact on Docebo's system — specifically on intra-service authentication.

The following areas are primarily affected:

Notifications

Insights

Learning Impact

AI

Community

Our teams are actively working to mitigate the impact and restore full functionality as soon as possible. We are closely monitoring AWS's progress and will provide updates as they become available.

We are continuing to actively troubleshoot the AWS service outage impacting customers and are working to resolve the root cause as quickly as possible.

AWS has applied a potential service mitigation. Continuous monitoring remains in effect to validate full system recovery.

The AWS service mitigation has been successful.
Docebo systems are now restored, and we are maintaining active monitoring as a precautionary measure.

We continue to observe recovery across most of the affected Services.
We continue to work towards full resolution and will provide updates as we have more information to share.

Customers located in US East 1 are experiencing long load times or errors when attempting to access or navigate their sites due to ongoing issues with AWS recovery. We are actively reviewing our possible mitigation paths and will update when additional information is available.

We are closely monitoring the AWS incident. At this time we expect continued intermittent latency and timeout errors for customers hosted in US East 1 until scalability is no longer throttled. We will update as soon as we see signs of recovery.

We are continuing to work with AWS to ensure we address the intermittent latency and timeout errors for customers hosted in US East 1 as soon as recovery is confirmed. We will provide another update when resolution is reached or the situation evolves.

We are now seeing recovery regarding latency and access errors for customers located in US East 1. We are continuing to track intermittent delays or errors in webhook queues as well as delays in processing queued events. We anticipate these to continue until the underlying AWS lambda service is fully operational. We'll provide additional updates available.