SNYK

⚪ Snyk's Gradle testing went full amnesiac for a bit, but engineers performed emergency memory restoration. AU environment is now functional again, and the incident response team can clock out before they become incidents themselves. (Auto-resolved: no updates in 24h)

⏰ May 26, 2026 Fixed (for now) spotted via status_rss

// The official story

Snyk Tests for Gradle projects Degradation

// Status page says

May 26 , 13:20 UTC Resolved - We have observed no further impact on services during our monitoring period. The Snyk Incident Response has now been stood down. May 25 , 23:26 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

🔗 Official status page (for the PR-approved version)

https://status.snyk.io/incidents/z70hrf2cnws2

Snyk's Greatest Hits

🔴 SNYK 4h ago

⚪ Snyk's GitLab integration has stopped cosplaying as a brick. GitLab recovered, Snyk stopped hyperventilating in their war room, and somehow nothing exploded in the last 24 hours. Living the dream.

🟢 SNYK 5d ago

⚪ Snyk's open source and container services went full introspection mode, then remembered how to work. Engineers applied the digital equivalent of turning it off and back on again. All systems now pretending nothing happened. (Auto-resolved: no updates in 24h)

🟢 SNYK 6d ago

⚪ Snyk's Issues API V3 had an existential crisis—timeouts disappeared, response times stopped limping, and the incident response team finally got to leave the war room. Turns out deploying a fix actually works. Who knew?. (Auto-resolved: no updates in 24h)

🟢 SNYK Oct 07, 2026

⚪ Snyk's dependency scanner got too ambitious analyzing test failures and face-planted hard. Engineers threw it in recovery mode, got it back on its feet, and confirmed the patient is breathing normally again. Crisis averted—for now. (Auto-resolved: no updates in 24h)