SCORM Cloud Outage History

Started Jun 29, 2026, 10:29 PM UTC· resolved Jul 01, 2026, 01:38 PM UTC

1. investigating Jun 29, 2026, 10:29 PM UTC

   We are currently investigating an issue that is causing delayed postbacks across our system. Our engineering team is actively working to identify the root cause and restore normal processing speeds.

2. identified Jun 30, 2026, 01:02 PM UTC

   The issue has been identified and a fix is being implemented. Any postbacks queued over the affected period will be retried once the issue is fully resolved.

3. identified Jun 30, 2026, 08:46 PM UTC

   Our engineering team is actively working on implementing a fix to resolve the issue causing delayed postbacks. We will provide another update as soon as the fix is deployed and system response times begin returning to normal. Thank you for your continued patience.

4. monitoring Jun 30, 2026, 10:24 PM UTC

   We have implemented measures to address the issue causing postback delays, and we are actively monitoring our systems as they process the queued backlog. Thank you for your patience.

5. resolved Jul 01, 2026, 01:38 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 20, 2025, 03:03 PM UTC· resolved Oct 20, 2025, 11:11 PM UTC

1. identified Oct 20, 2025, 03:03 PM UTC

   Due to a large AWS outage early this morning at roughly 7:11AM UTC, SCORM Cloud has been experiencing degraded performance due to it's reliance on AWS. We are monitoring and mitigating issues as we can during these times and thank you for your patience.

2. identified Oct 20, 2025, 08:59 PM UTC

   We are continuing to experience performance degradation due to the ongoing increased error rates and latencies with AWS. Our engineering team remains actively engaged in monitoring AWS status updates and applying necessary mitigations to reduce impact. We understand the critical nature of SCORM Cloud’s availability and are prioritizing restoration of full functionality. Thank you for your continued patience as we work through these challenges.

3. identified Oct 20, 2025, 11:04 PM UTC

   Service has been restored. Thank you for your patience.

4. resolved Oct 20, 2025, 11:11 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 08, 2024, 04:20 PM UTC· resolved Feb 18, 2025, 08:15 PM UTC

1. investigating Nov 08, 2024, 04:20 PM UTC

   We're experiencing performance issues with Reportage that are resulting in slow response times and timeouts and are actively looking into the issue.

2. identified Nov 08, 2024, 04:23 PM UTC

   While getting the Reportage database prepared for an update, an index was removed that causes interactions reports to either take a long time to load or not load altogether. We are attempting to re-add the index but unfortunately, due to the size of the table, this is taking longer than expected.

3. identified Dec 06, 2024, 04:08 AM UTC

   We are continuing to work on a fix to this issue, and greatly appreciate your patience as we do so. After much testing and many failures with other methods, we have decided to segment the data in order to shrink the data set that needs the index re-added, and therefore should speed up the recovery process. When trying to work with the table as a whole, the sheer size of it caused issues with timeouts, out-of-memory errors, and other failures that have prevented us from restoring full functionality. We have also identified ways to add more resiliency to the Reportage application to avoid any future issues like this. We would like to note that this issue appears to only affect some interaction reports. Our testing shows that smaller interaction reports can still be pulled and displayed successfully, but they time out as the size of the report increases. We haven't noticed any similar slowdowns for other types of reports. Again, we thank you for your patience, and we will continue to update this incident as we have more information.

4. monitoring Jan 22, 2025, 03:59 PM UTC

   The database issues affecting interaction reports have been resolved. Reportage is now functioning normally. We are keeping this incident open, as the database must still undergo a major version upgrade. This requires migrating date-time columns to a new format for one more notably large table. We do not expect this process to have a sizable or persistent impact on Reportage performance. However, it is possible there may be intermittent periods during this process where report generation is slower than expected due to database load. We are closely monitoring the upgrade process. Thank you again for your patience.

5. resolved Feb 18, 2025, 08:15 PM UTC

   The database has been fully upgraded and we expect no more issues related to this original incident.

Read the full incident report →