Snyk incident

Snyk Recurring Tests Degraded

Minor Resolved View vendor source →

Snyk experienced a minor incident on April 13, 2026 affecting Snyk Code and Snyk Code and 1 more component, lasting 1d 18h. The incident has been resolved; the full update timeline is below.

Started
Apr 13, 2026, 02:58 PM UTC
Resolved
Apr 15, 2026, 09:12 AM UTC
Duration
1d 18h
Detected by Pingoru
Apr 13, 2026, 02:58 PM UTC

Affected components

Snyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk ContainerSnyk ContainerSnyk ContainerSnyk ContainerSnyk Container

Update timeline

  1. investigating Apr 13, 2026, 02:58 PM UTC

    We're currently investigating degradation affecting Recurring Tests. Since April 11th, customers may have been experiencing delays for some Recurring Tests. The Snyk Incident Response has been invoked. We will keep you updated with our progress.

  2. identified Apr 13, 2026, 05:49 PM UTC

    Snyk Engineering has identified a mitigation and is currently implementing it.

  3. monitoring Apr 13, 2026, 09:55 PM UTC

    Snyk engineers have successfully deployed a mitigation. Recurring tests have now resumed, and we are closely monitoring the environment to ensure continued stability.

  4. monitoring Apr 14, 2026, 09:59 AM UTC

    We will continue to monitor services throughout today to ensure all Recurring Tests run as scheduled.

  5. resolved Apr 15, 2026, 09:12 AM UTC

    There have been no further issues observed throughout the monitoring period, and we're confident the issue has now been resolved. The Snyk Incident Response has been stood down.