Current answer
Snyk experienced a minor incident: Snyk Open Source and Container Degradation. ServiceAlert observed recovery on Oct 9, 2026.
Looking for an update now? Check the current status, or follow Snyk for future changes.
Incident Lifecycle
Affected Components
Snyk Container
Snyk Open Source
Incident Timeline
Monitoring
Our engineers have applied a fix, and services have recovered across our <a href="https://app.au.snyk.io/">app.au.snyk.io</a> environment.
If any project imports, tests or monitor runs failed or were blocked earlier, they should now complete as normal when re-run.
We are continuing to monitor performance closely and will post here if anything changes.
If any project imports, tests or monitor runs failed or were blocked earlier, they should now complete as normal when re-run.
We are continuing to monitor performance closely and will post here if anything changes.
Oct 8, 2026 at 11:24 AM UTC
Investigating
Our engineers are investigating degraded performance affecting Snyk Open Source and Snyk Container for customers within our <a href="https://app.au.snyk.io/">app.au.snyk.io</a> environment.
Customers may experience longer response times when importing projects, running tests, and monitoring projects through both SCM integrations and the Snyk CLI. Retrying the operation may succeed.
The Snyk Incident Response has been invoked. We will keep you updated with our progress.
Customers may experience longer response times when importing projects, running tests, and monitoring projects through both SCM integrations and the Snyk CLI. Retrying the operation may succeed.
The Snyk Incident Response has been invoked. We will keep you updated with our progress.
Oct 8, 2026 at 10:03 AM UTC
Was your business affected by this Snyk outage?
Follow Snyk and route available status alerts to email or a team channel.