SCORM Cloud Outage History

SCORM Cloud is up right now

SCORM Cloud had 4 outages in the last 2 years totaling 2458h 32m of downtime — averaging 0.2 incidents per month.

There were 4 SCORM Cloud outages since July 29, 2024 totaling 2458h 32m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.cloud.scorm.com

Notice October 20, 2025

SCORM Cloud Degraded Performance

Detected by Pingoru
Oct 20, 2025, 11:04 PM UTC
Resolved
Oct 20, 2025, 11:11 PM UTC
Duration
7m
Affected: SCORM Cloud WebsiteSCORM Cloud API
Timeline · 4 updates
  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 →

Minor August 27, 2024

Slow Response Time

Detected by Pingoru
Aug 27, 2024, 02:47 PM UTC
Resolved
Aug 27, 2024, 03:40 PM UTC
Duration
52m
Affected: SCORM Cloud WebsiteSCORM Cloud API
Timeline · 4 updates
  1. investigating Aug 27, 2024, 02:47 PM UTC

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

  2. identified Aug 27, 2024, 03:03 PM UTC

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

  3. monitoring Aug 27, 2024, 03:23 PM UTC

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

  4. resolved Aug 27, 2024, 03:40 PM UTC

    This incident has been resolved.

Read the full incident report →