SNYK

⚪ Snyk's web portal took an unscheduled nap affecting imports, retests, and PR checks. Engineers poked it with a stick, it woke up, and pretended nothing happened. Incident response stood down at 10:59 UTC. (Auto-resolved: no updates in 24h)

⏰ Jun 18, 2026 Fixed (for now) spotted via status_rss

// The official story

Degredation affecting app.snyk.io

// Status page says

Jun 18 , 10:59 UTC Resolved - No further issues have been observed during our monitoring period. The Snyk Incident Response has been stood down. Jun 17 , 23:31 UTC Monitoring - Our engineers are investigating degradation affecting app.snyk.io. This impacts user-initiated events such as imports, manual retests, PR checks, CLI, API endpoints on th

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

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

Snyk's Greatest Hits

🔴 SNYK 1h 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 5d 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)