Snyk: PR Checks Degraded

What to do

Check whether you use Snyk Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source and 1 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 1h 48m it lasted.
Anything that failed between 2026-05-22 17:26 UTC and 2026-05-22 19:14 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.

identifiedMay 22, 2026, 5:26 PM UTC
Snyk engineers have identified the root cause of degraded performance affecting Open Source across all environments, leading to PR Checks and recurring test failures. A fix is currently being rolled out globally. We will provide further updates as the deployment progresses.
provider
resolvedMay 22, 2026, 7:14 PM UTC
Snyk engineers have rolled out a fix across all environments. Our engineers will continue to monitor the situation. The Snyk Incident Response has been stood down.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

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

Is Snyk still down?

No, this incident was resolved 2026-05-22 19:14 UTC. For Snyk's live state, see https://down.guide/snyk.

How long did it last?

1h 48m, from 2026-05-22 17:26 UTC to 2026-05-22 19:14 UTC, by the times Snyk posted.

What was affected?

Snyk named Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source and 1 more.

What caused it?

Snyk hasn't published a root cause. If it does, it shows here.

Where does this come from?

Snyk's official status page, https://status.snyk.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.