Outage in Strigo

AWS Throttling Impacting Lab Deployments

Resolved Major
October 20, 2025 - Started 13 days ago - Lasted about 17 hours
Official incident page

Incident Report

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.

Need to monitor Strigo outages?

One place to monitor all your cloud vendors. Get instant alerts when an outage is detected.

Latest Updates ( sorted recent to last )
RESOLVED 12 days ago - at 10/21/2025 06:21AM

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.

IDENTIFIED 13 days ago - at 10/20/2025 01:51PM

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.

Latest Strigo outages

Chat is down - 2 months ago
Labs outage - 4 months ago
Webviews outage - 5 months ago
Recording Service Down - 8 months ago

The Status Page Aggregator Built for IT Teams

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 4522 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook