Strigo incident

Lab provisioning degredation

Critical Resolved View vendor source →

Strigo experienced a critical incident on March 25, 2020, lasting —. The incident has been resolved; the full update timeline is below.

Started
Mar 25, 2020, 04:00 AM UTC
Resolved
Mar 25, 2020, 04:00 AM UTC
Duration
Detected by Pingoru
Mar 25, 2020, 04:00 AM UTC

Update timeline

  1. resolved Mar 26, 2020, 05:17 AM UTC

    We've experienced degradation in provisoning lab instances. Things should be fine for now, but anyone who's still experiencing labs not loading from the previous ~24h, please replace your labs. We're sorry for the inconvenience.

  2. postmortem Mar 26, 2020, 05:18 AM UTC

    The issue happened due to a lack of capacity in the `eu-central-1` AWS region \(Frankfurt\), which we aren’t compensating for. We've addressed the issue specifically, and intend to implement a fallback for these types of situations.