Articulate incident

Articulate 360: Delayed provisioning for users signing in to Articulate 360 with SSO

Minor Resolved View vendor source →

Articulate experienced a minor incident on May 5, 2026 affecting Account Management, lasting 5h 32m. The incident has been resolved; the full update timeline is below.

Started
May 05, 2026, 08:08 PM UTC
Resolved
May 06, 2026, 01:40 AM UTC
Duration
5h 32m
Detected by Pingoru
May 05, 2026, 08:08 PM UTC

Affected components

Account Management

Update timeline

  1. investigating May 05, 2026, 08:08 PM UTC

    We’re investigating an issue that delays provisioning for some users signing into Articulate 360 with SSO. Impacted users may not see the expected access right away. We’ll share an update as soon as we know more.

  2. monitoring May 05, 2026, 08:52 PM UTC

    We’ve fixed the issue that caused delays when provisioning users through SSO in Articulate 360. Provisioning is now working as expected. Some users may still notice short delays as systems fully catch up. We’re continuing to monitor the performance to ensure everything remains stable.

  3. resolved May 06, 2026, 01:40 AM UTC

    This incident has been resolved.

  4. postmortem May 22, 2026, 11:19 PM UTC

    ### **Overview** On May 5th, 2026, between 6:00 PM and May 6th, 2026, 1:30 AM UTC, some customers experienced delays with identity provider \(IDP\) profile updates. During this time, updates to user profile information through SAML-based sign-ins may have taken longer than expected to appear across Articulate services. An internal system processing activity with a heavy load was identified as the cause of this incident. ### Incident Details and Timeline of Events | Time \(UTC\) | Event | | --- | --- | | May 5 6:05pm | Our monitoring detected degraded performance in processing user updates | | May 5 7:33pm | An incident response team was assembled | | May 5 8:37pm | The cause was identified as a large import of data by our sales team. After canceling the import, we opted to increase our processing capacity to handle the existing event logs | | May 6 1:28am | Services returned back to normal operation | ### What We’re Improving We’ve already completed several improvements, including: * Increasing processing capacity for high-volume events * Updating internal workflows for increased communication around large imports