Snowflake reported this critical-impact incident on its official status page on Jan 22, 2026, 19:18 UTC. It was resolved after 4h 6m.
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/INC0150359-and-INC0150440](https://community.snowflake.com/s/article/INC0150359-and-INC0150440)
<b>Current status:</b> Our observations of service telemetry continue to indicate that our service has recovered following the restart of the systems related to the Snowsight application-hosting layer. 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 Snowflake services and features using Snowsight or may have experienced delays. A subset of customers may have encountered errors while executing queries and other related operations. <b>Incident start time:</b> 19:02 UTC January 22, 2026 <b>Incident end time:</b> 19:30 UTC January 22, 2026 <b>Preliminary root cause:</b> While we're continuing to investigate to determine the underlying root cause of this issue, we suspect that a recent change made to our internal monitoring systems may have resulted in the problem with the Snowsight application-hosting layer. A root cause anal
<b>Current status:</b> Our observations of service telemetry indicate that our service has recovered following the restart of the systems related to the Snowsight application-hosting layer. 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 Snowflake services and features using Snowsight or may have experienced delays. <b>Incident start time:</b> 19:02 UTC January 22, 2026 <b>Incident end time:</b> 19:30 UTC January 22, 2026 <b>Preliminary root cause:</b> While we're continuing to investigate to determine the underlying root cause of this issue, we suspect that a recent change made to our internal monitoring systems may have resulted in the problem with the Snowsight application-hosting layer.
<b>Current status:</b> Our investigation has led us to focus on a potential issue with the Snowsight application-hosting layer. We're restarting the systems related to the Snowsight application-hosting layer, and our initial observation of telemetry indicates that this is providing relief. We're continuing to monitor as this trend continues to ensure the service returns to normal health. 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 Snowflake services and features using Snowsight or may experience delays.
<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 Snowflake services and features using Snowsight or may experience delays.
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