Snowflake reported this critical-impact incident on its official status page on Mar 21, 2026, 06:38 UTC. It was resolved after 34 min.
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/INC0154019](https://community.snowflake.com/s/article/INC0154019)
<b>Current status:</b> We've implemented the fix for this issue and monitored the environment to confirm that service was 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. Users would have encountered HTTP 404 or other similar errors. <b>Incident start time:</b> 05:27 UTC March 21, 2026 <b>Incident end time:</b> 06:18 UTC March 21, 2026 <b>Preliminary root cause:</b> The investigation determined that infrastructure responsible for high-level traffic routing and name resolution became degraded, which caused customers to encounter HTTP 404 errors when attempting to access or use certain Snowflake services. A root cause analysis (RCA) document will be pub
<b>Current status:</b> We've implemented the fix for 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. Users would have encountered HTTP 404 or other similar errors. <b>Incident start time:</b> 05:27 UTC March 21, 2026 <b>Incident end time:</b> 06:18 UTC March 21, 2026 <b>Preliminary root cause:</b> The investigation determined that infrastructure responsible for high-level traffic routing and name resolution became degraded, which caused customers to encounter HTTP 404 errors when attempting to access or use certain Snowflake services.
<b>Current status:</b> We've identified the source of the issue, and we're developing and implementing a fix to restore service. We'll provide another update within 30 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. <b>Incident start time:</b> 05:31 UTC March 21, 2026
<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 30 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>Incident start time:</b> 05:31 UTC March 21, 2026
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