PR Check Degradation

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 5d it lasted.

  Anything that failed between 2026-03-12 14:04 UTC and 2026-03-17 14:43 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. identifiedMar 12, 2026, 2:04 PM UTC

   Our Engineers are aware of the degradation affecting PR Checks. Customers may observe that there are processing delays impacting their PR Checks, resulting in PR Checks getting stuck in a processing state. The Snyk Incident Response has been invoked, and our investigations are underway.

   provider

2. monitoringMar 13, 2026, 7:33 AM UTC

   A fix has been deployed, and initial signs suggest this has been successful. We are currently monitoring to ensure services remain stable.

   provider

3. monitoringMar 17, 2026, 10:12 AM UTC

   We are continuing with monitoring throughout today to make sure our services continue to remain stable.

   provider

4. resolvedMar 17, 2026, 2:43 PM UTC

   No further impact has been observed during our monitoring period. 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.