SCORM Cloud incident

Registration Postback Service Interruption

Minor Resolved View vendor source →

SCORM Cloud experienced a minor incident on June 29, 2026 affecting SCORM Cloud API, lasting 1d 15h. The incident has been resolved; the full update timeline is below.

Started
Jun 29, 2026, 10:29 PM UTC
Resolved
Jul 01, 2026, 01:38 PM UTC
Duration
1d 15h
Detected by Pingoru
Jun 29, 2026, 10:29 PM UTC

Affected components

SCORM Cloud API

Update timeline

  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.