← Back to the carnage
SNYK
⚪ Snyk's container scanner had beef with JAR files and went on a 3-day strike before someone deployed a fix. The service is now back to pretending it never happened, which is definitely how software engineering works. (Auto-resolved: no updates in 24h)
// The official story
Container scans are degraded for images containing JAR files
// Status page says
Jan 19 , 09:10 UTC Resolved - No further impact has been observed throughout the monitoring period. The Snyk Incident Response has been stood down. Jan 16 , 14:57 UTC Monitoring - A fix has been deployed, and error rates are normalising. We are monitoring to ensure service stability. Jan 16 , 14:00 UTC <s
🔗 Official status page (for the PR-approved version)
https://status.snyk.io/incidents/qg9zp3yzc84wSnyk'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)