SNYK

🟡 Snyk Code scans are playing dead in IDE plugins. Engineers are debugging why the 'scan' button now means 'don't scan.' Downgrade to last week's version if you miss your vulnerabilities actually being found. (Auto-resolved: no updates in 24h)

⏰ Mar 03, 2026 Fixed (for now) spotted via status_rss

// The official story

IDE Plugin Scans not triggering

// Status page says

Mar 3 , 16:54 UTC Identified - Snyk engineers are currently investigating performance issues affecting IDE plugins. Customers may encounter scan not triggering when Snyk Code is enabled in their IDE settings. The Snyk team is working on a fix, which is expected to be released on March 4th as part of the regularly scheduled CLI update. As a workaround, customers can downgrade the IDE plugin to a previous version.

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

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

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)