Snyk reported this major-impact incident on its official status page on Jun 22, 2026, 22:21 UTC. It was resolved after 1d 23h.
Right now Snyk is operational. Live Snyk status →
This incident has been resolved.
We are continuing our monitoring throughout today to ensure services remain stable.
Mitigation steps have been completed and are showing immediate improvements in success rate and latency, and are burning down the backlog. We will maintain a period of monitoring for continued stability.
Snyk Engineering is continuing to investigate the issue. Mitigation steps are progressing but will take some time to be fully effective. Current scope of effect: * Customers may notice increased latency across the Snyk UI platform, as well as API, CLI, SCM based projects and PR Checks. * Due to the increased latency, some tests may be observed to timeout and fail. * There is currently no known observed impact to analytics and reporting. This issue is not affecting other environments. We will continue to work on mitigation efforts and provide updates as the issue progresses.
Snyk engineers are continuing their investigation. We have applied initial mitigation steps and are seeing signs of recovery, though some performance degradation persists. Our teams remain focused on a full resolution, and we will share another update shortly.
Our engineering team is currently investigating reports of degraded performance in the SNYK-US-01 US Multi-tenant environment (app.snyk.io). We are actively working to isolate the cause and will provide updates as we the investigation progresses.
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