Monitoring - We have re-enabled the email-to-case feature, allowing customers to create and reply to cases via email.
Monitoring is now underway to ensure the services remains stable.
Jun 09, 2026 - 14:13 UTC
Identified - Please note that the ability to create or reply to cases via email has been temporarily turned off. If you need to log a new issue or update an existing case, please do so directly through the ticketing portal. We will let you know as soon as email functionality is restored. Thank you for your patience!
Jun 08, 2026 - 15:47 UTC
Resolved -
Between 12:03 and 12:04 UTC today (1st June 2026), Snyk experienced a brief period of degradation affecting Snyk Code scans and custom Rule Extension tests. This impacted scans run via the CLI, IDE plugins, CLI uploads, as well as PR Checks.
Services have now fully recovered. Please retry any scans or tests that failed during this window.
Jun 1, 14:17 UTC
Resolved -
We have observed no further impact on services during our monitoring period.
The Snyk Incident Response has now been stood down.
May 26, 13:20 UTC
Monitoring -
Our Engineers have implemented a fix, and we're no longer observing the degradation on the AU-01 (app.au.snyk.io) environment. We will continue to monitor for ongoing stability.
May 25, 23:26 UTC
Update -
Our Engineers have confirmed that the US-01 (app.snyk.io) environment has shown no further degradation following re-deployment and appears to be stable.
Investigation into the AU-01 (app.au.snyk.io) environment is still ongoing, and we will provide a further update as we progress.
May 22, 14:52 UTC
Identified -
Snyk Engineers have identified degraded Open Source scanning performance for Gradle projects in the US-01 (app.snyk.io) and AU-01 (app.au.snyk.io) environments. The affect services include Repo Imports, Recurring tests, Manual Retests, and PR Checks. The investigation is ongoing under the Snyk Incident Response process.
May 22, 02:29 UTC