Strigo experienced a major incident on May 4, 2023 affecting Strigo service, lasting 8m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 04, 2023, 01:17 PM UTC
New labs that were created between UTC 10:50 and 13:15 had limited accessibility and lags
- identified May 04, 2023, 01:18 PM UTC
The root cause was identified and a patch was deployed. We're validating that the issues is fixed before unrolling the fix to all labs.
- monitoring May 04, 2023, 01:21 PM UTC
The fix seems to solve the issue. Deployed to affect all labs. Monitoring.
- resolved May 04, 2023, 01:25 PM UTC
The issue is now resolved
- postmortem May 04, 2023, 01:25 PM UTC
Today \(the 4th of May \(may the 4th be with you\), at UTC 13:15\), some users experienced downtime in our labs provisioning that lasted 3h and 5m. We noticed that the service responsible for preparing lab connectivity for newly created labs could not run for several lab instances. After a rather deep investigation, we conclude that this was related to an unsuccessful deploy of the service around the start time of the issue. We’ve been monitoring the system since then and all seems to be operational. We apologize for the inconvenience.