← Back to the carnage
SNYK

⚪ Snyk spent three hours playing whack-a-mole with its US-01 region, where importing projects kept dying mid-birth with a cryptic 'nope' error. Engineers finally found what was broken, fixed it, and declared victory before grabbing coffee. (Auto-resolved: no updates in 24h)

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

// The official story

Project import on US-01 region intermittently completes with "Project could not be created"

// Status page says

Jan 29 , 09:36 UTC Resolved - Our Engineers have implemented a fix and are confident this incident is now resolved. The Snyk Incident Response has now been stood down. Jan 29 , 08:40 UTC Update - Our investigations into the root cause are continuing. We will keep you updated as we progress. Jan 29 , 06:44 UTC <

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

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

Snyk'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)