🟠 Snowflake yanked a chunk of Azure East US 2 infrastructure offline after it started phoning in its performance like a disengaged employee. Queries are getting rerouted to the competent servers, but query history is running on geological time. The good news: at least they caught it before the whole thing went full archaeological dig. (Auto-resolved: no updates in 24h)

// The official story

Azure - East US 2 (Virginia): INC0155020

// Status page says

Apr 7 , 19:13 UTC Identified - Current status: We've identified the source of the issue as a portion of the infrastructure which supports core Snowflake services operating below operational thresholds. We've taken the affected portion of infrastructure out of active rotation and confirmed that Snowflake traffic is being routed to healthy infrastructure. Affected users may experience delayed query history. While the majority of