Articulate Outage History

Started Nov 20, 2025, 07:13 PM UTC· resolved Nov 21, 2025, 12:23 AM UTC

1. investigating Nov 20, 2025, 07:13 PM UTC

   We're actively investigating an issue where some users are unable to log in to Reach 360. Our engineering team is currently working to resolve this authentication issue. While we investigate, affected users can contact our support team for assistance.

2. investigating Nov 20, 2025, 08:23 PM UTC

   We are continuing to investigate this Reach 360 login issue.

3. investigating Nov 20, 2025, 10:02 PM UTC

   Our engineering team is continuing their work in resolving this authentication issue and is close to implementing a fix.

4. monitoring Nov 20, 2025, 11:21 PM UTC

   We’ve fixed the issue that impacted Reach 360, and all systems are now stable. We’re continuing to monitor performance to ensure everything runs smoothly. Thanks for your patience while we worked on this.

5. resolved Nov 21, 2025, 12:23 AM UTC

   This incident has been resolved, and Reach 360 is fully operational. Thanks for your patience while we worked on this.

6. postmortem Dec 03, 2025, 10:33 PM UTC

   A recent software update in Reach 360 caused a problem that affected how some user accounts were set up. When a user updated their profile—or when a new account was created—an important piece of information that connects their profile to our login system was accidentally removed. When this happened, the affected users could no longer sign in to Reach 360. Only a small number of users across our data centers were impacted. **November 19** * **3:17 PM ET** - A code change was shipped which caused a misconfiguration for a subset of users, preventing login for impacted users in Reach. **November 20** * **11:30 AM ET** - **1:29 PM ET** - Users reported login issues which prompted our triage team to investigate, where the underlying code change was identified. * **2:08 PM ET** - A fix was implemented, which prevented additional users from being impacted, but did not resolve the issues with users who had already been affected. * **2:10 PM ET** - The triage team worked to understand the scope of impact to users. * **5:55 PM ET** - The impacted users were repaired and could now log in, systems were stable. Some permission changes made during this outage may have been lost, which could be corrected manually by admins, but did not affect overall system stability. **November 21** * **11:33 AM ET** - A script was run to clean up any lingering issues with permissions, fully resolving the incident. ### What We’re Improving * We’re improving internal tools in the affected areas to make updates more quickly and reliably going forwards. * We found two systems were connected in a way that let this issue occur. We’re improving that integration and adding protections to strengthen reliability going forward. * Refining our internal alerting and dashboards to surface these patterns earlier.

Read the full incident report →

Started Nov 19, 2025, 02:01 PM UTC· resolved Nov 19, 2025, 07:01 PM UTC

1. investigating Nov 19, 2025, 02:01 PM UTC

   We are continuing to investigate an issue affecting Articulate Localization in Rise 360 and Storyline 360. Currently, content isn’t translating as expected when selecting certain languages. Creators may notice that the following languages fail to translate: Khmer Luxembourgish Lao Maori Nepali Nyanja Samoan Tetum Tigrinya We’ll share more updates as soon as we learn more!

2. investigating Nov 19, 2025, 02:23 PM UTC

   We are continuing to investigate this issue.

3. investigating Nov 19, 2025, 04:18 PM UTC

   We are continuing to investigate this issue.

4. monitoring Nov 19, 2025, 05:40 PM UTC

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

5. resolved Nov 19, 2025, 07:01 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 14, 2025, 05:42 PM UTC· resolved Nov 14, 2025, 06:11 PM UTC

1. investigating Nov 14, 2025, 05:42 PM UTC

   We’re investigating an issue that prevents authors from publishing Rise 360 courses to LMS, Web, PDF, and Review 360. Thanks for your patience while we dig in. We’ll keep this page updated as we learn more.

2. identified Nov 14, 2025, 05:47 PM UTC

   We’ve identified the issue and released a fix. Publishing is starting to work again for creators, and we’re keeping a close eye as the fix rolls out. We’ll confirm once everything’s fully stable.

3. monitoring Nov 14, 2025, 05:55 PM UTC

   We've confirmed publishing is stable for all Creators, and we're continuing to monitor the situation. Thanks for your patience!

4. resolved Nov 14, 2025, 06:11 PM UTC

   Publishing in Rise 360 is working normally again. If you still have questions or run into any trouble, our Support team is here to help at articulatecase.com. Thanks again for your patience while we sorted this out.

Read the full incident report →

Started Nov 12, 2025, 04:11 PM UTC· resolved Nov 12, 2025, 07:50 PM UTC

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.

Read the full incident report →

Started Nov 04, 2025, 06:04 PM UTC· resolved Nov 04, 2025, 06:04 PM UTC

1. resolved Nov 04, 2025, 06:04 PM UTC

   This incident has been resolved. We identified and fixed an issue where text edits in Rise 360 Custom Blocks weren't saving properly. The issue occurred between 11:13 AM and 5:06 PM Eastern on Monday, November 3. Users should refresh their browsers to ensure they're working with the latest version. We're sorry for the trouble and appreciate your patience.

Read the full incident report →

Started Nov 03, 2025, 09:17 PM UTC· resolved Nov 04, 2025, 07:21 PM UTC

1. monitoring Nov 03, 2025, 09:17 PM UTC

   We’re investigating intermittent issues that may prevent users from accessing Reach 360. Some may be unable to log in or use the product reliably. We’ve made a change and are currently monitoring performance to confirm stability.

2. resolved Nov 04, 2025, 07:21 PM UTC

   This incident has been resolved. Reach 360 is fully operational.

Read the full incident report →

Started Oct 28, 2025, 04:36 PM UTC· resolved Oct 28, 2025, 05:48 PM UTC

1. investigating Oct 28, 2025, 04:36 PM UTC

   We’re investigating an issue that’s blocking access to Reach 360. Users may be unable to log in or load reports right now. We’ll share more details as soon as we have them.

2. monitoring Oct 28, 2025, 05:08 PM UTC

   We implemented a fix for the issue that was blocking access to Reach 360. Users can now log in and load reports. All systems are operational, and we're actively monitoring performance to ensure continued stability.

3. monitoring Oct 28, 2025, 05:18 PM UTC

   We implemented a fix for the issue blocking access to Reach 360. Users couldn't access Reach 360. All systems are operational, and we're actively monitoring performance to ensure continued stability.

4. resolved Oct 28, 2025, 05:48 PM UTC

   This incident has been resolved. Reach 360 is fully operational.

Read the full incident report →

Started Oct 24, 2025, 02:59 PM UTC· resolved Oct 24, 2025, 03:50 PM UTC

1. investigating Oct 24, 2025, 02:59 PM UTC

   Articulate support chat is currently not available. This includes access to our chatbot and all links to chat on our website. In the meantime, you can still reach us via [email protected], [email protected], or through our E-Learning Heroes Community at https://community.articulate.com/ We'll let you know as soon as we're back up and running!

2. resolved Oct 24, 2025, 03:50 PM UTC

   This is resolved. Our support chat is back online.

Read the full incident report →

Started Oct 20, 2025, 04:07 PM UTC· resolved Oct 20, 2025, 09:42 PM UTC

1. investigating Oct 20, 2025, 04:07 PM UTC

   We’ve paused ordering to prevent processing errors caused by issues with our cloud service provider. This helps us avoid failed transactions and ensure accuracy once services stabilize. We’re actively investigating and will share updates as we learn more. Thanks for your patience while we work through this.

2. resolved Oct 20, 2025, 09:42 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 20, 2025, 09:59 AM UTC· resolved Oct 21, 2025, 01:03 PM UTC

1. monitoring Oct 20, 2025, 09:59 AM UTC

   We encountered an issue with our cloud service provider that affected many of our products. Everything is more stable now. We'll continue to monitor closely and update you when we have more info. We’re so sorry for the trouble.

2. monitoring Oct 20, 2025, 12:22 PM UTC

   We are continuing to monitor for any further issues.

3. monitoring Oct 20, 2025, 01:07 PM UTC

   Services remain stable, although given the wide-spread impact on our systems, we're continuing to monitor them until we receive a confirmation from our cloud service provider.

4. monitoring Oct 20, 2025, 01:22 PM UTC

   We’re continuing to monitor our systems and have observed delays affecting our AI features and Articulate 360 email notifications. We’ll share another update once we receive confirmation that everything has fully recovered.

5. monitoring Oct 20, 2025, 01:54 PM UTC

   We’re continuing to monitor our systems and have no new information to share at this time.

6. monitoring Oct 20, 2025, 02:40 PM UTC

   We’re continuing to monitor our systems and have no new information to share at this time. If you're experiencing any issues, please contact our Support team by visiting articulatecase.com or emailing [email protected].

7. monitoring Oct 20, 2025, 03:19 PM UTC

   We’re continuing to monitor our systems and have no new information to share at this time. If you're experiencing any issues, please contact our Support team by visiting articulatecase.com or emailing [email protected].

8. monitoring Oct 20, 2025, 03:54 PM UTC

   We are still seeing degraded performance across our systems and are waiting on updates from our cloud service provider. Things may be inconsistent. If you’re running into issues, please reach out to our Support team by visiting articulatecase.com or emailing [email protected].

9. monitoring Oct 20, 2025, 04:24 PM UTC

   We are still seeing degraded performance across our systems and are waiting on updates from our cloud service provider. Things may be inconsistent. If you’re running into issues, please reach out to our Support team by visiting articulatecase.com or emailing [email protected].

10. monitoring Oct 20, 2025, 04:53 PM UTC

    We are still seeing degraded performance across our systems and are waiting on updates from our cloud service provider. Things may be inconsistent. If you’re running into issues, please reach out to our Support team by visiting articulatecase.com or emailing [email protected].

11. monitoring Oct 20, 2025, 05:22 PM UTC

    We are still seeing degraded performance across our systems and are waiting on updates from our cloud service provider. Things may be inconsistent. If you’re running into issues, please reach out to our Support team by visiting articulatecase.com or emailing [email protected].

12. monitoring Oct 20, 2025, 05:51 PM UTC

    We are still seeing degraded performance across our systems and are waiting on updates from our cloud service provider. Things may be inconsistent. If you’re running into issues, please reach out to our Support team by visiting articulatecase.com or emailing [email protected].

13. monitoring Oct 20, 2025, 06:21 PM UTC

    We are still seeing degraded performance across our systems and are waiting on updates from our cloud service provider. Things may be inconsistent. If you’re running into issues, please reach out to our Support team by visiting articulatecase.com or emailing [email protected].

14. monitoring Oct 20, 2025, 06:53 PM UTC

    We are still seeing degraded performance across our systems and are waiting on updates from our cloud service provider. Things may be inconsistent. If you’re running into issues, please reach out to our Support team by visiting articulatecase.com or emailing [email protected].

15. monitoring Oct 20, 2025, 07:23 PM UTC

    We are still seeing degraded performance across our systems and are waiting on updates from our cloud service provider. Things may be inconsistent. If you’re running into issues, please reach out to our Support team by visiting articulatecase.com or emailing [email protected].

16. monitoring Oct 20, 2025, 07:56 PM UTC

    We are still seeing degraded performance across our systems and are waiting on updates from our cloud service provider. Things may be inconsistent. If you’re running into issues, please reach out to our Support team by visiting articulatecase.com or emailing [email protected].

17. monitoring Oct 20, 2025, 08:30 PM UTC

    We are still seeing degraded performance across our systems and are waiting on updates from our cloud service provider. Things may be inconsistent. If you’re running into issues, please reach out to our Support team by visiting articulatecase.com or emailing [email protected].

18. monitoring Oct 20, 2025, 09:14 PM UTC

    We’re still experiencing degraded performance across our systems and are currently awaiting updates from our cloud service provider. Publishing to Review 360 may continue to fail due to the earlier incident, and performance may remain inconsistent for now. If you’re running into issues, please reach out to our Support team by visiting articulatecase.com or emailing [email protected].

19. monitoring Oct 20, 2025, 11:25 PM UTC

    Our cloud provider has resolved most of the incident on their end. We’re currently processing a backlog of events and messages, which may still cause some delays. However, one of our critical third-party providers continues to experience issues affecting Rise and publishing to Review 360. Once those issues are fully resolved, our services should return to normal operations. If you’re running into issues, please reach out to our Support team at articulatecase.com or by emailing [email protected].

20. monitoring Oct 21, 2025, 03:19 AM UTC

    Our cloud provider has resolved the issue and we have made some temporary changes to ensure all components are working normally again. We’ll continue to monitor the situation.

21. resolved Oct 21, 2025, 01:03 PM UTC

    We monitored our systems overnight, and they’ve remained stable. This issue is resolved. Thanks so much for your patience.

22. postmortem Oct 24, 2025, 03:52 PM UTC

    ### **Overview** Between 7:33 UTC on October 20 and 13:00 UTC on October 21, Articulate 360 experienced a widespread service disruption caused by an outage within our third-party cloud hosting provider, Amazon Web Services. This event caused intermittent failures, slow loading, and degraded performance across multiple Articulate 360 services. ### **Incident Details and Timeline of Events** Impact: * Many customers reported an inability to sign into Articulate tools * Access to Articulate services was inconsistent throughout the incident * The widespread outage impacted the platforms Articulate uses to communicate and mitigate issues, further delaying our ability to update customers and reduce the impact. Timeline: * **07:33–07:43 UTC \(October 20\)** Monitoring detected degraded performance. Customers reported login issues. We confirmed a broad impact and activated our incident response team. * **08:00–09:30 UTC** We identified a widespread outage with our cloud provider. While they worked on recovery, we stabilized services, rerouted traffic, and attempted to post updates—though our status page provider was also affected. * **09:44–10:14 UTC** Connectivity improved. We restarted services and adjusted configurations. Our first public update was posted, and we continued monitoring. * **10:30–22:30 UTC** Most systems recovered, but instability lingered. We cleared backlogs and made additional config changes while our provider’s services improved. Some media processing remained delayed. * **23:00 UTC \(October 20\)—03:30 UTC \(October 21\):** A related issue with our feature-flag provider disrupted publishing and caused slow loading for a small group of customers. We deployed fallbacks to restore stability. * **03:30–13:00 UTC \(October 21\)** All systems stabilized. We monitored closely and confirmed full recovery after final checks. ### **What We’re Improving** While we’re proud of how quickly our teams mobilized and the mitigations we implemented during this incident, we also identified areas where we can do better: * Faster public communication – We’re working on backup options and updating our playbooks to enable us to share timely updates, even when our usual tools are down. * Stronger protections and reducing dependency on third-party providers – We’re building better safeguards and backup systems to keep those tools from affecting your experience again. We’re using what we’ve learned to strengthen our systems, improve our communication, and better support you during future incidents.

Read the full incident report →

Started Oct 09, 2025, 09:54 PM UTC· resolved Oct 09, 2025, 11:26 PM UTC

1. investigating Oct 09, 2025, 09:54 PM UTC

   We're currently investigating an issue where Reach 360 users are experiencing discrepancies in their Course Analytics reporting. Some data may appear to be missing or incomplete when viewing reports. We’re working to identify the cause and will provide updates as soon as more information is available. We'll provide another update within the hour.

2. resolved Oct 09, 2025, 11:26 PM UTC

   This incident has been resolved.

Read the full incident report →