Live / Snyk / Incident
Snyk: PR Checks and Imports Degraded in SNYK-US-01
Snyk · snyk.ioMinor incidentResolved2026-10-15 21:47 UTC
Public — what happened
Summary
Snyk said that pull request checks and project imports were running slowly in its SNYK-US-01 multi-tenant environment, an issue it rated minor. The company reported that it began at 20:39 UTC on 2026-10-15, that it had found the problem and started working on a fix right away. By 21:04 UTC Snyk said a mitigation was in place and PR checks were back to normal while a backlog of imports was worked through, and by 21:09 UTC it said that backlog was cleared. Snyk marked the incident resolved at 21:47 UTC.
Affected
Snyk Code, Snyk Container, Snyk IaC, Snyk Open Source, Snyk API & Web, Snyk Secrets
Timeline
- Started — 2026-10-15 20:39 UTC
- Identified — 2026-10-15 20:39 UTC
- Monitoring — 2026-10-15 21:04 UTC (2 updates)
- Resolved — 2026-10-15 21:47 UTC · 1h 07m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Snyk against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Snyk: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Snyk report →
More from Snyk
Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.