Snyk reported this major-impact incident on its official status page on Aug 4, 2026, 13:07 UTC. It was resolved after 1h 22m.
Right now Snyk is operational. Live Snyk status →
Our engineers have deployed a fix and, after a brief monitoring period, have confirmed all services have recovered. The Snyk Incident Response has been stood down.
Our engineering team have identified the root cause and are working on deploying a fix. We will keep you updated on our progress.
We've identified an issue affecting all .NET project workflows, including import, retest, and pull request checks. The Snyk Incident Response has been invoked, and our engineering team are investigating.
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.
Overlapping incidents aren't necessarily related.
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