Strigo experienced a major incident on May 27, 2025 affecting Strigo service, lasting 24m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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.