Strigo incident

Slow response times in the classroom for large events

Minor Resolved View vendor source →

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

Started
Apr 16, 2020, 06:04 PM UTC
Resolved
Apr 23, 2020, 06:55 PM UTC
Duration
7d
Detected by Pingoru
Apr 16, 2020, 06:04 PM UTC

Affected components

Strigo service

Update timeline

  1. investigating Apr 16, 2020, 06:04 PM UTC

    We're currently experiencing a performance-related issue when running large events (~60+ attendees). There is a strong correlation between the number of workspaces in the event and the degradation in performance. This means that both instructors and students in the classroom will experience long transition times when switching between tabs or navigating presentation slides, and with other interactions with the user interface. Lab and video performance seem to be working regularly. We're looking into the problem and will update as we gather more insights. We apologize for the inconvenience.

  2. resolved Apr 23, 2020, 06:55 PM UTC

    We've identified several causes for slowness (mainly related to how we dealt with realtime data flows between our client and our server) and resolved them.