Snyk Recurring Tests Degraded

What to do

• Check whether you use Snyk Snyk Code, Snyk Open Source. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 3d 21h it lasted.

  Anything that failed between 2026-03-12 14:54 UTC and 2026-03-16 11:58 UTC may need a replay.

• Subscribe to Snyk's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=snyk works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Snyk 4

1. investigatingMar 12, 2026, 2: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.

   provider

2. investigatingMar 12, 2026, 3: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.

   provider

3. identifiedMar 13, 2026, 1: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.

   provider

4. resolvedMar 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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.