Snyk incident

Snyk Recurring Tests Degraded

Minor Resolved View vendor source →

Snyk experienced a minor incident on March 12, 2026 affecting Snyk Code and Snyk Open Source, lasting 3d 21h. The incident has been resolved; the full update timeline is below.

Started
Mar 12, 2026, 02:54 PM UTC
Resolved
Mar 16, 2026, 11:58 AM UTC
Duration
3d 21h
Detected by Pingoru
Mar 12, 2026, 02:54 PM UTC

Affected components

Snyk CodeSnyk Open Source

Update timeline

  1. investigating Mar 12, 2026, 02:54 PM UTC

    Our Engineers are investigating degradation affecting Snyk Recurring Tests. Some Customers may notice that their daily recurring tests have not executed as expected. The Snyk Incident Response has been invoked, and our investigations have commenced.

  2. investigating Mar 12, 2026, 03:27 PM UTC

    During our initial investigations, we identified that only a small portion of daily recurring tests are impacted. The affected tests are experiencing a delay relative to their usual schedule. Our investigations remain ongoing, and we will continue to keep you updated with our progress.

  3. identified Mar 13, 2026, 01:35 PM UTC

    Services are beginning to normalise. However, a small percentage of customers may continue to experience delays affecting their daily Recurring Tests as we work through the backlog. We will continue to update you as we progress.

  4. resolved Mar 16, 2026, 11:58 AM UTC

    We are no longer observing delays affecting our daily recurring tests, and all backlogs have now cleared. The Snyk Incident Response has now been stood down.