Major impactResolvedDevOps

Snyk outage: Temporary Degradation of Open Source and Container

Snyk reported this major-impact incident on its official status page on Jul 22, 2026, 09:41 UTC. It was resolved after 21h 28m.

Right now Snyk is operational. Live Snyk status →

🔔 Get alerted when Snyk has issuesFree · email alerts · no credit card
Jul 22, 2026, 09:41 UTC
started
Jul 23, 2026, 07:09 UTC
resolved
21h 28m
duration
Major
impact

Affected components

  • Snyk Container
  • Snyk Open Source
  1. resolvedJul 23, 2026, 07:09 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.

  2. monitoringJul 22, 2026, 09:41 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Snyk's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Snyk have incidents?

Snyk reported 17 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 6h 27m. See Snyk's uptime and incident history

Snyk outage on Jul 22, 2026: Temporary Degradation of Open Source and Container · APIStatus.watch