← Back to the carnage
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)
// 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/z70hrf2cnws2Snyk's Greatest Hits
🟢 SNYK
1d ago
🟡 Snyk's app management features went into hibernation while existing apps just sit there, perfectly fine, watching the chaos. Engineers are currently having a staring contest with their monitors trying to figure out what happened. (Auto-resolved: no updates in 24h)
🟢 SNYK
6d ago
⚪ Snyk's Go-based PR checks went full existential crisis, then got therapy. Engineers applied the digital equivalent of duct tape, success rates stabilized, and everyone pretended this never happened. Crisis averted, dignity remains questionable. (Auto-resolved: no updates in 24h)
🟢 SNYK
Nov 03, 2026
⚪ Snyk spent 8+ hours denying users access to their own code before engineers deployed a fix. The incident response team has stood down, which is fancy HR speak for 'we're pretending this never happened.' Services are now behaving like they're supposed to. (Auto-resolved: no updates in 24h)
🟢 SNYK
Oct 29, 2026
⚪ Snyk's Bitbucket integrations went radio silent, then mysteriously decided to start working again after engineers threw the classic 'have you tried turning it off and on' solution at it. Crisis averted, relationship status: complicated. (Auto-resolved: no updates in 24h)