Articulate ID: Users can’t log in or create Articulate 360 Trials

Update timeline

1. investigating Nov 12, 2025, 04:11 PM UTC

   We’re currently investigating an issue that’s preventing users from logging in, staying logged in, and creating Articulate 360 trials. This affects access to all Articulate 360 apps. We know this is disruptive, and we’re working to restore access as quickly as we can. We’ll share more as soon as we know more!

2. monitoring Nov 12, 2025, 04:56 PM UTC

   We aren’t seeing new login errors with Articulate ID. Access to Articulate 360 apps is working as expected right now. We’re monitoring closely in case the issue returns. If we see more trouble, we’ll update this status right away. Thanks for hanging in there!

3. monitoring Nov 12, 2025, 06:05 PM UTC

   Everything continues to run smoothly. Users can log in and access Articulate 360 apps without trouble. We’re still investigating the root cause. We’ll keep monitoring and share another update once we wrap up that work.

4. resolved Nov 12, 2025, 07:50 PM UTC

   We've resolved the issue affecting Articulate ID that prevented users from logging in and creating Articulate 360 trials. All systems are now working normally.

5. postmortem Nov 19, 2025, 11:02 PM UTC

   ### **Overview** On November 12 between 15:34 UTC and 16:20 UTC, we experienced trouble connecting to our authentication provider. This caused intermittent login and signup errors for some users. The disruption was traced back to a brief networking problem within one zone of a third-party cloud hosting provider, which affected outbound connections from a subset of our systems. ### Incident Details and Timeline of Events **Impact:** * Some users experienced intermittent errors when logging in. * Some users experienced issues staying logged into our application. * New account signups and trial activations occasionally failed or had to be retried. **Timeline:** * **November 12 15:43 - 15:50 UTC** — Monitoring detected degraded performance for authentication errors and activated our incident response team. * **November 12 15:50 - 16:11 UTC** — We identified the issue causing a subset of requests to our authentication provider to fail and attempted to restart those services. Our first public update was posted. * **November 12 16:20 - 16:56 UTC** — Connectivity improved. Most systems recovered. We continued to closely monitoring. * **November 12 19:30 - 19:50 UTC** — Third-party cloud hosting provider confirmed a regional networking issue was the cause and we confirmed full recovery after final checks. ### What We’re Improving We provided a quick response and swift mitigation measures during this incident, but also identified areas for improvement: * Refinements to our internal alerting and dashboards to surface these patterns earlier and cut down investigation time. * Clearer escalation paths with cloud hosting providers so we can confirm external incidents sooner.