Articulate incident
Articulate Systems are Intermittently Available
Articulate experienced a minor incident on October 20, 2025 affecting Rise 360 and Review 360 and 1 more component, lasting 1d 3h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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.
- monitoring Oct 20, 2025, 12:22 PM UTC
We are continuing to monitor for any further issues.
- 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.
- 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.
- 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.
- 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].
- 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].
- 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].
- 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].
- 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].
- 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].
- 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].
- 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].
- 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].
- 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].
- 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].
- 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].
- 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].
- 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].
- 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.
- 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.
- 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.