SCORM Cloud Outage History

SCORM Cloud is up right now

SCORM Cloud had 2 outages in the last 2 years totaling 39h 16m of downtime — averaging 0.1 incidents per month.

There were 2 SCORM Cloud outages since October 20, 2025 totaling 39h 16m of downtime. Each is summarised below — incident details, duration, and resolution information.

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

Minor June 29, 2026

Registration Postback Service Interruption

Detected by Pingoru
Jun 29, 2026, 10:29 PM UTC
Resolved
Jul 01, 2026, 01:38 PM UTC
Duration
1d 15h
Affected: SCORM Cloud API
Timeline · 5 updates
  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 →

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 →