Snyk Recurring Tests Degraded

What to do

• Check whether you use Snyk Snyk Code, Snyk Code, Snyk Code, Snyk Code and 16 more. 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 1d 18h it lasted.

  Anything that failed between 2026-04-13 14:58 UTC and 2026-04-15 09:12 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 5

1. investigatingApr 13, 2026, 2: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.

   provider

2. identifiedApr 13, 2026, 5:49 PM UTC

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

   provider

3. monitoringApr 13, 2026, 9: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.

   provider

4. monitoringApr 14, 2026, 9:59 AM UTC

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

   provider

5. resolvedApr 15, 2026, 9: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.

   provider

Corrections

None so far.

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