Snyk reported this minor-impact incident on its official status page on Oct 8, 2026, 10:03 UTC. It was resolved after 21h 5m.
Right now Snyk is operational. Live Snyk status →
Services have remained stable throughout our monitoring period, and the Snyk Incident Response has been stood down.
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.
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.
Overlapping incidents aren't necessarily related.
Snyk reported 21 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 14h 35m. See Snyk's uptime and incident history