Skip to content
Snowflake · Data and observabilityApr 7, 2026, 18:26 UTC

Azure - East US 2 (Virginia): INC0155020

CriticalDatabaseUpdated 20h ago
Apr 7, 18:26 UTCApr 7, 20:56 UTC
Duration
2h 30m
Impact
Critical
Root cause
Database
Snowflake, 90 days
22 incidents
Affected
Databases, Tables, and ViewsVirtual WarehousesData Loading and UnloadingApplicationsAzure - East US 2 (Virginia) - Databases, Tables, and ViewsAzure - East US 2 (Virginia) - Virtual WarehousesAzure - East US 2 (Virginia) - Data Loading and UnloadingAzure - East US 2 (Virginia) - Applications
Status page

Final update

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)

Timeline

  1. Postmortem · Apr 15, 00:21 UTC
    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)
  2. Resolved · Apr 7, 20:56 UTC
    Current status: 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. Customer experience: 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. Incident start time: 17:47 UTC April 07, 2026 Incident end time: 19:45 UTC April 07, 2026 Preliminary root cause: 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.
  3. Monitoring · Apr 7, 20:08 UTC
    Current status: 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. Customer experience: 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. Incident start time: 17:47 UTC April 07, 2026 Incident end time: 19:45 UTC April 07, 2026 Preliminary root cause: A portion of the infrastructure that supports core Snowflake services was operating below operational thresholds, which resulted in impact.
  4. Identified · Apr 7, 19:13 UTC
    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 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. Customer experience: 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. ETA: 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. Incident start time: 17:47 UTC April 07, 2026
  5. Investigating · Apr 7, 18:26 UTC
    Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. Customer experience: 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.

More from Snowflake

Full history
StartedIncidentDuration
Sep 1404:48 UTCINC200002171h 21m
Sep 1107:18 UTCINC200002136h 1m
Sep 921:53 UTCINC200002111h 58m
Sep 407:34 UTCINC200001992h 36m
Sep 109:58 UTCINC200001903h 52m
Aug 3117:20 UTCINC200001882h 24m

Also caused by database

All
StartedIncidentDuration
Sep 1309:16 UTCIncident with several GitHub ServicesGitHub1h 29m
Aug 2616:17 UTCIssues performance is degraded in the USSentry4h 19m
Aug 1216:16 UTCIncident with Pull Requests and IssuesGitHub25m
Aug 818:57 UTCAccount Registration, Droplets, and Related ServicesDigitalOcean6h 3m
Jul 2817:41 UTCEvent ingestion and retrieval delays for some North America customersHubSpot2h
Jul 2419:37 UTCIncident with Pull RequestsGitHub46m

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.