Snowflake reported this major-impact incident on its official status page on Mar 7, 2026, 20:05 UTC. It was resolved after 2h 14m.
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/INC0153183](https://community.snowflake.com/s/article/INC0153183)
<b>Current status:</b> We've coordinated with our third-party cloud platform to confirm that the fix for this issue was successfully implemented, and we've monitored the environment to confirm that service has been fully 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 multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data. <b>Incident start time:</b> 19:30 UTC March 07, 2026 <b>Incident end time:</b> 21:10 UTC March 07, 2026 <b>Preliminary root cause:</b> A third-party cloud platform experienced an issue with part of their storage service, which temporarily prevented some Snowflake services and features from working for a subset of customers in this region. A root cause analysis (RCA) document will be pub
<b>Current status:</b> We've coordinated with our third-party cloud platform to remediate this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data. <b>Incident start time:</b> 19:30 UTC March 07, 2026 <b>Incident end time:</b> 21:10 UTC March 07, 2026 <b>Preliminary root cause:</b> A third-party cloud platform experienced an issue with part of their storage service, which temporarily prevented some Snowflake services and features from working for a subset of customers in this region.
<b>Current status:</b> We've identified an issue with a third-party cloud platform, and we're coordinating with the provider to restore service. We're beginning to see some relief as mitigation actions take effect. We're continuing to monitor, and 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. 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> 19:30 UTC March 07, 2026
<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