Strigo incident

GitHub fetching functionality is limited

Minor Resolved View vendor source →

Strigo experienced a minor incident on January 22, 2025 affecting Strigo service, lasting 3d 16h. The incident has been resolved; the full update timeline is below.

Started
Jan 22, 2025, 06:57 PM UTC
Resolved
Jan 26, 2025, 11:46 AM UTC
Duration
3d 16h
Detected by Pingoru
Jan 22, 2025, 06:57 PM UTC

Affected components

Strigo service

Update timeline

  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.