Articulate incident

Articulate 360 Desktop App: Creators can’t sign in

Critical Resolved View vendor source →

Articulate experienced a critical incident on April 21, 2026 affecting Articulate ID and Articulate 360 Desktop App Updates, lasting 1h 55m. The incident has been resolved; the full update timeline is below.

Started
Apr 21, 2026, 06:31 PM UTC
Resolved
Apr 21, 2026, 08:26 PM UTC
Duration
1h 55m
Detected by Pingoru
Apr 21, 2026, 06:31 PM UTC

Affected components

Articulate IDArticulate 360 Desktop App Updates

Update timeline

  1. investigating Apr 21, 2026, 06:31 PM UTC

    We’re seeing an issue where Creators can’t sign in to the Articulate 360 desktop app. You may see sign-in failures or get stuck during login. This impacts launching and updating apps from the desktop app. Our team is investigating now. We’ll share updates as we learn more.

  2. identified Apr 21, 2026, 07:00 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Apr 21, 2026, 07:22 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Apr 21, 2026, 08:26 PM UTC

    This incident has been resolved.

  5. postmortem May 01, 2026, 05:47 PM UTC

    #### Overview On 2026-04-21 between approximately 01:45–03:15 ET \(05:45–07:15 UTC\), Articulate 360 Desktop app users experienced authentication failures preventing access to the Articulate 360 Desktop application. The issue was caused by an infrastructure-level change that corrupted a signing key used in the authentication flow. The problem was identified and resolved within approximately 90 minutes. Web-based users were not affected. #### Incident Details and Timeline of Events **Impact:** * Articulate 360 Desktop app users were unable to complete authentication checks, blocking access to the desktop application * Web-based users were not impacted * Duration: approximately 90 minutes **Timeline:** * **2026-04-21 ~01:45 ET \(05:45 UTC\)** — Articulate 360 Desktop app users begin experiencing authentication failures. * **2026-04-21 ~02:00 ET \(06:00 UTC\)** — Issue identified by our engineering team and investigation underway. * **2026-04-21 ~03:15 ET \(07:15 UTC\)** — Fix applied and service fully restored for all affected users. #### What We're Improving * Adding safeguards so that misconfigured authentication credentials are detected at startup and prevent a service from going live, rather than causing silent failures for users * Strengthening our review process for changes to shared infrastructure components to ensure their impact across all services is evaluated before merging