Strigo incident

Slower than usual response times within the application

Minor Resolved View vendor source →

Strigo experienced a minor incident on April 2, 2020 affecting Strigo service, lasting 6d 12h. The incident has been resolved; the full update timeline is below.

Started
Apr 02, 2020, 08:50 PM UTC
Resolved
Apr 09, 2020, 08:57 AM UTC
Duration
6d 12h
Detected by Pingoru
Apr 02, 2020, 08:50 PM UTC

Affected components

Strigo service

Update timeline

  1. investigating Apr 02, 2020, 08:50 PM UTC

    Some customers have experienced slower than usual response times within our application. Core functionality, such as lab work, has not been impacted. We are working to resolve this issue and will continue to provide updates as necessary. In the meantime, if you are experiencing this issue, please reach out to us via the support chat. Thank you for your patience and understanding.

  2. investigating Apr 06, 2020, 10:46 AM UTC

    We have identified a few issues that were affecting the performance of the user interface in a live event and in an on-demand environment. We are finalizing some fixes and should introduce them soon. We will keep updating.

  3. resolved Apr 09, 2020, 08:57 AM UTC

    3 days ago we have issued several fixes to the performance of the user interface in the live classroom and the on-demand environments. Another fix is scheduled to be issued soon. These fixes have to do with the way the user interface handles the real-time data arriving during the live activity in the classroom or on-demand environment. By this, we resolve the issue.