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)

⏰ Jan 19, 2026 Fixed (for now) spotted via status_rss

// 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/qg9zp3yzc84w

Snyk's Greatest Hits

🔴 SNYK 12h 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)