Strigo incident

Labs with Office licenses are not launching

Major Resolved View vendor source →

Strigo experienced a major incident on April 21, 2026 affecting Strigo service, lasting 6h 58m. The incident has been resolved; the full update timeline is below.

Started
Apr 21, 2026, 04:00 PM UTC
Resolved
Apr 21, 2026, 10:58 PM UTC
Duration
6h 58m
Detected by Pingoru
Apr 21, 2026, 04:00 PM UTC

Affected components

Strigo service

Update timeline

  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.