Live / Snyk / Incident
Snyk: Snyk Open Source and Container Degradation
Snyk · snyk.ioMinor incidentResolved2026-10-09 07:08 UTC
Public — what happened
Summary
Snyk reported slower performance in its Open Source and Container products starting at 10:03 UTC on 2026-10-08, affecting customers using its Australian environment at app.au.snyk.io. The company said importing, testing and monitoring projects, whether through source code integrations or the command-line tool, could take longer than usual, and that trying again might work. By 11:24 UTC Snyk said a fix was in place and service had recovered, adding that anything that failed earlier should work if run again; it did not state a cause. The incident was marked resolved on 2026-10-09 at 07:08.
Affected
Snyk Container, Snyk Open Source
Timeline
- Started — 2026-10-08 10:03 UTC
- Investigating — 2026-10-08 10:03 UTC
- Monitoring — 2026-10-08 11:24 UTC
- Resolved — 2026-10-09 07:08 UTC · 21h 05m 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 42, 2026, our weekly internet health report.