SCORM Cloud incident

Service Disruption

Critical Resolved View vendor source →

SCORM Cloud experienced a critical incident on November 14, 2018 affecting SCORM Cloud Website and SCORM Cloud API, lasting 2h 14m. The incident has been resolved; the full update timeline is below.

Started
Nov 14, 2018, 06:47 PM UTC
Resolved
Nov 14, 2018, 09:02 PM UTC
Duration
2h 14m
Detected by Pingoru
Nov 14, 2018, 06:47 PM UTC

Affected components

SCORM Cloud WebsiteSCORM Cloud API

Update timeline

  1. investigating Nov 14, 2018, 06:47 PM UTC

    SCORM Cloud engineers are aware of a service disruption and are currently investigating.

  2. identified Nov 14, 2018, 07:12 PM UTC

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

  3. monitoring Nov 14, 2018, 07:47 PM UTC

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

  4. resolved Nov 14, 2018, 09:02 PM UTC

    We have identified a source of an unusually large number of requests which resulted in excessive database I/O wait times. We are currently investigating the nature of these requests and have temporarily put in place rudimentary rate limiting to prevent future disruptions. Once we have identified why the sudden increase in traffic occurred, we will implement a long term solution to the problem.