Strigo Outage History

Strigo is up right now

Strigo had 12 outages in the last 2 years totaling 360h 41m of downtime — averaging 0.5 incidents per month.

There were 12 Strigo outages since November 20, 2024 totaling 360h 41m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.strigo.io

Major April 21, 2026

Labs with Office licenses are not launching

Detected by Pingoru
Apr 21, 2026, 04:00 PM UTC
Resolved
Apr 21, 2026, 10:58 PM UTC
Duration
6h 58m
Affected: Strigo service
Timeline · 3 updates
  1. 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.

  2. 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.

  3. 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.

Read the full incident report →

Major April 1, 2026

No RDP to remote desktop labs

Detected by Pingoru
Apr 01, 2026, 04:47 PM UTC
Resolved
Apr 01, 2026, 05:08 PM UTC
Duration
21m
Affected: Strigo serviceAWS EC2 (eu-west-1)
Timeline · 3 updates
  1. investigating Apr 01, 2026, 04:47 PM UTC

    Labs based on remote desktops and RDP connections are not accessible right now.

  2. investigating Apr 01, 2026, 05:05 PM UTC

    We are continuing to investigate this issue.

  3. 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.

Read the full incident report →

Major November 24, 2025

Recording feature unavailable

Detected by Pingoru
Nov 24, 2025, 12:29 PM UTC
Resolved
Dec 03, 2025, 02:02 PM UTC
Duration
9d 1h
Affected: Strigo service
Timeline · 5 updates
  1. 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.

  2. monitoring Dec 03, 2025, 01:28 PM UTC

    A fix has been implemented and we're monitoring

  3. identified Dec 03, 2025, 01:37 PM UTC

    We identified an issue with current implementation and we are working on the fix

  4. monitoring Dec 03, 2025, 01:50 PM UTC

    Another fix has been implemented and we're monitoring

  5. resolved Dec 03, 2025, 02:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 20, 2025

AWS global outage impacting Strigo labs

Detected by Pingoru
Oct 20, 2025, 12:43 PM UTC
Resolved
Oct 20, 2025, 07:00 AM UTC
Duration
—
Timeline · 1 update
  1. 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.

Read the full incident report →

Minor August 25, 2025

Chat is down

Detected by Pingoru
Aug 25, 2025, 06:12 PM UTC
Resolved
Aug 25, 2025, 06:52 PM UTC
Duration
39m
Affected: Strigo service
Timeline · 3 updates
  1. identified Aug 25, 2025, 06:12 PM UTC

    The chat is down. We identified the issue and the fix is being deployed.

  2. monitoring Aug 25, 2025, 06:41 PM UTC

    The fix was deployed. The chat is back to normal. We're monitoring.

  3. resolved Aug 25, 2025, 06:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 30, 2025

Webview returns 404 errors for some users

Detected by Pingoru
Jun 30, 2025, 02:11 PM UTC
Resolved
Jun 30, 2025, 04:14 PM UTC
Duration
2h 3m
Affected: Strigo service
Timeline · 6 updates
  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. resolved Jun 30, 2025, 04:14 PM UTC

    Monitoring is complete and all systems are operating normally. The issue has been fully resolved.

Read the full incident report →

Notice June 25, 2025

Labs outage

Detected by Pingoru
Jun 25, 2025, 01:30 PM UTC
Resolved
Jun 25, 2025, 02:40 PM UTC
Duration
1h 9m
Affected: Strigo service
Timeline · 5 updates
  1. investigating Jun 25, 2025, 02:35 PM UTC

    We’ve identified an issue with our labs and are currently investigating it.

  2. investigating Jun 25, 2025, 02:36 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jun 25, 2025, 02:38 PM UTC

    The issue has been resolved.

  4. resolved Jun 25, 2025, 02:40 PM UTC

    This incident has been resolved.

  5. 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.**

Read the full incident report →

Major May 27, 2025

Webviews outage

Detected by Pingoru
May 27, 2025, 11:56 AM UTC
Resolved
May 27, 2025, 12:20 PM UTC
Duration
24m
Affected: Strigo service
Timeline · 4 updates
  1. 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).

  2. identified May 27, 2025, 11:57 AM UTC

    Rollback of the bad deployment initiated; estimated recovery within 15 minutes

  3. 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.

  4. 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.

Read the full incident report →

Minor March 11, 2025

Recording Service Down

Detected by Pingoru
Mar 11, 2025, 03:29 PM UTC
Resolved
Mar 12, 2025, 10:37 AM UTC
Duration
19h 7m
Affected: Strigo service
Timeline · 3 updates
  1. 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.

  2. 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!

  3. 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!

Read the full incident report →

Minor January 22, 2025

GitHub fetching functionality is limited

Detected by Pingoru
Jan 22, 2025, 06:57 PM UTC
Resolved
Jan 26, 2025, 11:46 AM UTC
Duration
3d 16h
Affected: Strigo service
Timeline · 2 updates
  1. 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.

  2. 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.

Read the full incident report →

Critical November 20, 2024

Strigo classroom application is down

Detected by Pingoru
Nov 20, 2024, 04:00 PM UTC
Resolved
Nov 20, 2024, 04:29 PM UTC
Duration
28m
Affected: Strigo service
Timeline · 5 updates
  1. 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.

  2. 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.

  3. 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.

  4. 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!

  5. resolved Nov 20, 2024, 04:29 PM UTC

    The issue has been fully resolved, and all systems are operating normally.

Read the full incident report →