Snyk: Temporary Degradation of Open Source and Container

What to do

Check whether you use Snyk Snyk Container, 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 21h 28m it lasted.
Anything that failed between 2026-07-22 09:41 UTC and 2026-07-23 07:09 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.

monitoringJul 22, 2026, 9:41 AM UTC
From 09:08 to 09:30 UTC customers may have experienced errors when executing imports for Snyk Open Source or Snyk Container. Additionally, some customers may have experienced issues when attempting to view Project details for these project types. The Snyk Incident response was activated and corrective actions have returned operations to normal. The team is continuing to monitor the situation.
provider
resolvedJul 23, 2026, 7:09 AM UTC
No further impact was observed during our monitoring period. Customers should re-import any imports that errored or failed during the outage window. 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-07-23 07:09 UTC. For Snyk's live state, see https://down.guide/snyk.

How long did it last?

21h 28m, from 2026-07-22 09:41 UTC to 2026-07-23 07:09 UTC, by the times Snyk posted.

What was affected?

Snyk named Snyk Container, Snyk Open Source.

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.