Changes / Snowflake / Azure - East US 2 (Virginia): INC0155020
Snowflake: Critical incident: Azure - East US 2 (Virginia): INC0155020
Summary
Snowflake reported a critical outage in Azure - East US 2 (Virginia) from 2026-04-07 18:26 UTC to 2026-04-07 20:56 UTC (2 h 29 min), potentially blocking sign-in, queries and data management. Infrastructure supporting core services was operating below operational thresholds; Snowflake removed it from rotation and rerouted traffic to healthy infrastructure, restoring service.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Azure - East US 2 (Virginia): INC0155020
Before: not present
After: critical
Before: not present
After: postmortem
Before: not present
After: 2026-04-07 18:26 UTC
Before: not present
After: 2026-04-07 20:56 UTC
Before: not present
After: Applications, Azure - East US 2 (Virginia) - Applications, Azure - East US 2 (Virginia) - Databases, Tables, and Views, Azure - East US 2 (Virginia) - Data Loading and Unloading, Azure - East US 2 (Virginia) - Virtual Warehouses, Databases, Tables, and Views, Data Loading and Unloading, Virtual Warehouses
Before: not present
After: <b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes.
<b>Customer experience:</b> Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data.
Before: not present
After: <b>Current status:</b> 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 impact appears to have subsided, we're working to confirm that impact to Snowsight specifically is recovering as well. We'll provide another update within 60 minutes.
<b>Customer experience:</b> Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features, and may experience latency when using Snowsight. Affected users may be unable to sign in, execute queries, or manage data.
<b>ETA:</b> An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures.
<b>Incident start time:</b> 17:47 UTC April 07, 2026
Before: not present
After: <b>Current status:</b> We've confirmed that our service has recovered following the routing of affected traffic to healthy infrastructure, and we're continuing to monitor as the health of Snowsight continues to improve. Other services are fully recovered, but some users who were affected during the period of impact may temporarily experience delayed or incomplete query history.
<b>Customer experience:</b> Customers hosted in the specified regions may have been unable to access or use multiple core Snowflake services and features, and may have experienced latency when using Snowsight. Affected users may have been unable to sign in, execute queries, or manage data.
<b>Incident start time:</b> 17:47 UTC April 07, 2026
<b>Incident end time:</b> 19:45 UTC April 07, 2026
<b>Preliminary root cause:</b> A portion of the infrastructure that supports core Snowflake services was operating below operational thresholds, which resulted in impact.
Before: not present
After: <b>Current status:</b> We've rerouted Snowflake traffic to healthy infrastructure to address this issue, and we've monitored the environment to confirm that service has been restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight.
<b>Customer experience:</b> Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. A subset of affected customers were also unable to use other core Snowflake services and features, such as executing queries or tasks.
<b>Incident start time:</b> 17:47 UTC April 07, 2026
<b>Incident end time:</b> 19:45 UTC April 07, 2026
<b>Preliminary root cause:</b> A subset of our metadata database infrastructure in this region became degraded, which impacted the overall availability of the service for affected customers. Concurrently, Snowsight infrastructure experienced a period of increased latency and failures, which correlated specifically to Snowsight availability issues in the region.
A root cause analysis (RCA) document will be published within five business days.
Before: not present
After: Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC0155020](https://community.snowflake.com/s/article/INC0155020)
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: Azure - East US 2 (Virginia): INC0155020 (this change) Snowflake reported a critical outage in Azure - East US 2 (Virginia) from 2026-04-07 18:26 UTC to 2026-04-07 20:56 UTC (2 h 29 min), potentially blocking sign-in, queries and data management. Infrastructure supporting core services was operating below operational thresholds; Snowflake removed it from rotation and rerouted traffic to healthy infrastructure, restoring service. | Major incident |
All Snowflake changes → · Snowflake profile · Markdown · JSON