Strigo experienced a major incident on October 20, 2025 affecting Strigo service and AWS EC2 (us-east-1) and 1 more component, lasting 23h 6m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Oct 20, 2025, 01:51 PM UTC
Due to the recent outage in Amazon Web Services, as they recover from their global outage, they are throttling all customers and we’re being impacted in as well. This causes Strigo labs to launch slowly, mainly in the us-east-1 region. We apologize for the inconvenience. One course of action is to wait until AWS stops throttling API calls. An alternative direction - provision your labs in a different region: 1. Make sure you have the AMI from the us-east-1 region copied to another region. 2. Go to any problematic class template with the us-east-1 region. Remove the us-east-1 entry and put another entry with the AMI from the other region. 3. For OD labs that are currently stuck, you will have to find the matching enrollments in the administrative console, un-enroll them, and then re-enroll them. This will result in provisioning the labs in the new region. 4. Live events: either replace the slow-launching labs, or end the live event and re-create it. We are monitoring the API throttling we’re experiencing and will update as soon as anything changes.
- resolved Oct 21, 2025, 06:21 AM UTC
All systems are now back to normal. We’re not expecting any further issues at this time. Please let us know immediately if you encounter anything unusual.