What visitors reported during this incident
No visitor reports were filed for this incident.
Having problems with Snowflake now? Check the current statusAffected services
Updates (5)
- Apr 15, 2026, 12:21 AMAzure - East US 2 (Virginia): INC0155020
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)
Snowflake ↗ - Apr 7, 2026, 08:56 PMAzure - East US 2 (Virginia): INC0155020
<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 q
Snowflake ↗ - Apr 7, 2026, 08:08 PMAzure - East US 2 (Virginia): INC0155020
<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. Affecte
Snowflake ↗ - Apr 7, 2026, 07:13 PMAzure - East US 2 (Virginia): INC0155020
<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:</
Snowflake ↗ - Apr 7, 2026, 06:26 PMAzure - East US 2 (Virginia): INC0155020
<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.
Snowflake ↗
What to do next
- Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
- Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
- Watch the provider going forward. Follow Snowflake's status feed →
GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.