โ Back to the carnage
SNOWFLAKE
๐ด Snowflake in US West decided to play hide-and-seek with customer data. Engineers are investigating why 'processing efficiency' is code for 'we broke it.' Meanwhile, your queries are getting real acquainted with timeout errors. (Auto-resolved: no updates in 24h)
// The official story
AWS - US West (Oregon): INC0159680
// Status page says
Jun 22 , 21:48 UTC Update - Current status: We are continuing to investigate the underlying source of the issue. In parallel, we are working to improve processing efficiency in a portion of our service infrastructure as a potential mitigation for the increased downstream load affecting related services. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core
๐ Official status page (for the PR-approved version)
https://status.snowflake.com/incidents/zn8xxp2qzpr1Snowflake's Greatest Hits
๐ข SNOWFLAKE
Oct 29, 2026
๐ Snowflake discovered their virtual warehouses were stored in someone else's cloud locker, and that locker caught fire. Third-party provider is slowly fixing it while Snowflake watches and updates their status page like they're not directly responsible. (Auto-resolved: no updates in 24h)
๐ข SNOWFLAKE
Oct 20, 2026
๐ Snowflake's monitoring team discovered a magical definition of 'healthy service' that apparently includes an entire availability zone ghosting them. They've put the region in timeout and are now playing phone tag with their cloud provider while pretending everything's fine. Narrator voice: it was not fine. (Auto-resolved: no updates in 24h)
๐ข SNOWFLAKE
Oct 14, 2026
๐ก Snowflake's regional infrastructure threw a tantrum and had to restart. The good news: most tasks are limping back to life. The bad news: they're still fishing task history out of the digital trash. Think of it as your database's awkward teenage phaseโembarrassing, temporary, hopefully. (Auto-resolved: no updates in 24h)
๐ข SNOWFLAKE
Sep 01, 2026
๐ Snowflake found the bug hiding in plain sight and is slowly letting customers back in like a bouncer checking IDs. Most folks can login again, but they're taking their sweet time rolling out the fix to everyone else. ETA: another hour of watching the status page like it's a reality show. (Auto-resolved: no updates in 24h)