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

As listed on Snyk’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the Snyk status & history page.

Related: Snyk status & history. SquidGrid is not affiliated with Snyk.