Snyk reported this minor-impact incident on its official status page on May 22, 2026, 02:29 UTC. It was resolved after 4d 10h.
Right now Snyk is operational. Live Snyk status →
We have observed no further impact on services during our monitoring period. The Snyk Incident Response has now been stood down.
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.
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.
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.
Our 5-minute checks didn't record a change in Snyk's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
Snyk reported 17 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 6h 27m. See Snyk's uptime and incident history