Strigo Outage History
Strigo is up right nowPingoru has recorded 39 incidents for Strigo: 3 in the last 12 months and 0 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 7 of 720 (1%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 517 (0%) |
Incidents, newest first
Major April 21, 2026 Labs with Office licenses are not launching 6h 58m Strigo service
Started Apr 21, 2026, 04:00 PM UTC· resolved Apr 21, 2026, 10:58 PM UTC
- investigating Apr 21, 2026, 04:00 PM UTC
Lab AWS instances fail to register with the AWS license manager and therefore don't launch. The root cause is unknown, and we are still investigating.
- investigating Apr 21, 2026, 07:01 PM UTC
There seems to be an internal problem with the AWS license manager service. We are working with AWS to solve it.
- resolved Apr 21, 2026, 10:58 PM UTC
The incident is resolved, and Office-based labs are now launching properly across all regions. The issue was a new setting in the license manager, set by AWS, that interrupted the process of registering lab instances with the license manager. That setting has been turned off.
Major April 1, 2026 No RDP to remote desktop labs 21m Strigo service, AWS EC2 (eu-west-1)
Started Apr 01, 2026, 04:47 PM UTC· resolved Apr 01, 2026, 05:08 PM UTC
- investigating Apr 01, 2026, 04:47 PM UTC
Labs based on remote desktops and RDP connections are not accessible right now.
- investigating Apr 01, 2026, 05:05 PM UTC
We are continuing to investigate this issue.
- resolved Apr 01, 2026, 05:44 PM UTC
We found a resource access problem in our eu-west based RDP relay servers and restarted them.
Major November 24, 2025 Recording feature unavailable 9d 1h Strigo service
Started Nov 24, 2025, 12:29 PM UTC· resolved Dec 03, 2025, 02:02 PM UTC
- investigating Nov 24, 2025, 12:29 PM UTC
Our recording infrastructure is currently unavailable. As a result, no new recordings can be started for live events, and affected sessions will not generate recording video archives.
- monitoring Dec 03, 2025, 01:28 PM UTC
A fix has been implemented and we're monitoring
- identified Dec 03, 2025, 01:37 PM UTC
We identified an issue with current implementation and we are working on the fix
- monitoring Dec 03, 2025, 01:50 PM UTC
Another fix has been implemented and we're monitoring
- resolved Dec 03, 2025, 02:02 PM UTC
This incident has been resolved.
Major October 20, 2025 AWS Throttling Impacting Lab Deployments 23h 6m Strigo service, AWS EC2 (us-east-1), AWS EC2 (us-west-2)
Started Oct 20, 2025, 07:15 AM UTC· resolved Oct 21, 2025, 06:21 AM UTC
- 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.
Notice October 20, 2025 AWS global outage impacting Strigo labs 3h 46m
Started Oct 20, 2025, 07:00 AM UTC· resolved Oct 20, 2025, 10:46 AM UTC
- resolved Oct 20, 2025, 12:43 PM UTC
Start time: ~07:11 UTC End time: ~10:46 UTC At ~07:11 UTC a widespread outage at Amazon Web Services (us-east-1 region) caused significant failures in provisioning and accessing virtual infrastructure. As a result, Strigo lab workspaces across the affected region became inaccessible until ~10:46 UTC when services returned to normal. If you continue to experience issues, please contact us.
Minor August 25, 2025 Chat is down 39m Strigo service
Started Aug 25, 2025, 06:12 PM UTC· resolved Aug 25, 2025, 06:52 PM UTC
- identified Aug 25, 2025, 06:12 PM UTC
The chat is down. We identified the issue and the fix is being deployed.
- monitoring Aug 25, 2025, 06:41 PM UTC
The fix was deployed. The chat is back to normal. We're monitoring.
- resolved Aug 25, 2025, 06:52 PM UTC
This incident has been resolved.
Major June 30, 2025 Webview returns 404 errors for some users 2h 3m Strigo service
Started Jun 30, 2025, 02:11 PM UTC· resolved Jun 30, 2025, 04:14 PM UTC
- investigating Jun 30, 2025, 02:11 PM UTC
We’re currently investigating an issue causing the webview to return 404 errors for some users. Our team is working to identify the root cause and restore full functionality as soon as possible.
- investigating Jun 30, 2025, 02:11 PM UTC
We deployed a fix to the rate limiter in an attempt to resolve the webview 404 errors. Unfortunately, this change did not resolve the issue. Our team continues to investigate.
- investigating Jun 30, 2025, 02:12 PM UTC
We applied an additional fix to the webview reverse proxy logic. However, this also did not resolve the issue. We’re still actively investigating and will provide further updates as soon as possible.
- investigating Jun 30, 2025, 02:41 PM UTC
We’re currently deploying another fix that targets the webview routing behavior. We’ll monitor its impact closely and continue investigating in parallel.
- monitoring Jun 30, 2025, 03:14 PM UTC
We’ve deployed a fix that appears to have resolved the webview 404 issue. The affected functionality is now working as expected for impacted users. We’re continuing to monitor closely to ensure stability.
- resolved Jun 30, 2025, 04:14 PM UTC
Monitoring is complete and all systems are operating normally. The issue has been fully resolved.
Notice June 25, 2025 Labs outage 1h 9m Strigo service
Started Jun 25, 2025, 01:30 PM UTC· resolved Jun 25, 2025, 02:40 PM UTC
- investigating Jun 25, 2025, 02:35 PM UTC
We’ve identified an issue with our labs and are currently investigating it.
- investigating Jun 25, 2025, 02:36 PM UTC
We are continuing to investigate this issue.
- investigating Jun 25, 2025, 02:38 PM UTC
The issue has been resolved.
- resolved Jun 25, 2025, 02:40 PM UTC
This incident has been resolved.
- postmortem Jun 25, 2025, 03:06 PM UTC
**Incident Update: Labs Startup and Launch Issue** **We identified an issue with one of our internal servers responsible for handling both labs startup and launch processes. This caused a disruption in initiating new labs.** **The root cause has been fixed, and the server is now fully operational. All lab types are back online and functioning as expected.** **We are monitoring the system to ensure continued stability. Thank you for your patience.**
Major May 27, 2025 Webviews outage 24m Strigo service
Started May 27, 2025, 11:56 AM UTC· resolved May 27, 2025, 12:20 PM UTC
- identified May 27, 2025, 11:56 AM UTC
A recent version deployment to our reverse-proxy layer (responsible for routing web interfaces into the lab) introduced an upstream resolution error, causing lookup failures (Unable to find upstream … Upstream lookup returned 500).
- identified May 27, 2025, 11:57 AM UTC
Rollback of the bad deployment initiated; estimated recovery within 15 minutes
- monitoring May 27, 2025, 12:11 PM UTC
The rollback has completed successfully and all webviews seem to be restored. Error rates have returned to normal and users can access the labs as expected. We’re continuing to monitor system health and will update if anything changes.
- resolved May 27, 2025, 12:20 PM UTC
All webviews have been fully restored and are operating normally. No further errors detected. Thank you for your patience.
Minor March 11, 2025 Recording Service Down 19h 7m Strigo service
Started Mar 11, 2025, 03:29 PM UTC· resolved Mar 12, 2025, 10:37 AM UTC
- investigating Mar 11, 2025, 03:29 PM UTC
We are currently experiencing an issue where the recording service is down for all Strigo users. This is due to an error in the infrastructure, and our team is actively investigating the root cause. We will provide updates as soon as we have more information. We apologize for the disruption and appreciate your patience.
- monitoring Mar 12, 2025, 10:15 AM UTC
We identified an issue where DNS resolution between our API server and the recording service failed, preventing all users from recording in Strigo. The issue has now been resolved, and recordings should be functioning as expected. We are currently monitoring to ensure stability, but everything appears to be back to normal. Thank you for your patience, and we apologize for the disruption!
- resolved Mar 12, 2025, 10:37 AM UTC
Monitoring has been completed, and everything is operating normally. The issue is fully resolved, and recording services are stable. Thank you for your patience!
Minor January 22, 2025 GitHub fetching functionality is limited 3d 16h Strigo service
Started Jan 22, 2025, 06:57 PM UTC· resolved Jan 26, 2025, 11:46 AM UTC
- investigating Jan 22, 2025, 06:57 PM UTC
Fetching lab configs and exercises from private repositories is currently unavailable for both manual and automatic methods. Public repositories remain unaffected. We are actively investigating the issue.
- resolved Jan 26, 2025, 11:46 AM UTC
We experienced a temporary disruption due to high activity levels causing GitHub to throttle our access. After implementing optimizations, the issue has been fully resolved. All functionality for private and public repositories is now restored. Thank you for your understanding.
Critical November 20, 2024 Strigo classroom application is down 28m Strigo service
Started Nov 20, 2024, 04:00 PM UTC· resolved Nov 20, 2024, 04:29 PM UTC
- identified Nov 20, 2024, 04:00 PM UTC
We’re currently experiencing an infrastructure issue causing all users to encounter a 404 error. Our team is actively working on resolving this as quickly as possible. We deeply apologize for the inconvenience and appreciate your patience.
- identified Nov 20, 2024, 04:07 PM UTC
We’ve identified the root cause of the issue and are now working to address its downstream effects.
- monitoring Nov 20, 2024, 04:13 PM UTC
All Strigo applications are now back up and running. We are actively monitoring the systems to ensure everything remains stable.
- monitoring Nov 20, 2024, 04:18 PM UTC
Monitoring is complete, and everything is back to normal. We’re deeply sorry for the disruption and appreciate your patience and support during this time!
- resolved Nov 20, 2024, 04:29 PM UTC
The issue has been fully resolved, and all systems are operating normally.