SCORM Cloud incident

Service Interruption

Critical Resolved View vendor source →

SCORM Cloud experienced a critical incident on May 1, 2020 affecting SCORM Cloud Website and SCORM Cloud API, lasting 1h 18m. The incident has been resolved; the full update timeline is below.

Started
May 01, 2020, 03:49 PM UTC
Resolved
May 01, 2020, 05:08 PM UTC
Duration
1h 18m
Detected by Pingoru
May 01, 2020, 03:49 PM UTC

Affected components

SCORM Cloud WebsiteSCORM Cloud API

Update timeline

  1. investigating May 01, 2020, 03:49 PM UTC

    Engineers are currently investigating an unexpected service interruption

  2. investigating May 01, 2020, 04:05 PM UTC

    We are continuing to investigate this issue.

  3. monitoring May 01, 2020, 04:41 PM UTC

    We observed service latency that has resolved and are monitoring the recovery.

  4. resolved May 01, 2020, 05:08 PM UTC

    This incident has been resolved. A specific update to a database table was identified as the source of the problem. We have identified a more performant implementation of the query. Additionally, we have identified improvements to our change control procedures that will reduce the likelihood of non-performant data updates being run in the future.