Snowflake reported this critical-impact incident on its official status page on Apr 7, 2026, 18:26 UTC. It was resolved after 2h 30m.
Right now Snowflake is degraded. Live Snowflake status →
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)
<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 f
<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.
<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 i
<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.
Our 5-minute checks didn't record a change in Snowflake's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
Snowflake reported 23 incidents in the last 90 days, 18 of them major or critical. A typical incident lasted 1h 56m. See Snowflake's uptime and incident history