Snowflake Outage History

Current status: 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. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified region may be unable to access Snowsight or sign in to the Snowflake web interface. Customers using Snowflake Openflow, Snowpark Container Services, or Cortex AI services — including Cortex LLM functions, Agents, Analyst, and Search — may encounter errors or failures when using these services. Workaround: There were no available workarounds for this issue. Incident start time: 23:23 UTC June 10, 2026 Incident end time: 23:58 UTC June 10, 2026 Preliminary root cause: A routine system configuration change intended to unblock a cluster upgrade caused connectivity issues with Snowpark Container Services. Once identified, the configuration was reverted.

Current status: We've monitored the environment and confirmed the rollback restored service. 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 experienced Cortex Code in Snowsight stopping mid-response after completing only one step of a request. The response may have stopped without an error message or may have repeated without progressing. Incident start time: 22:50 UTC May 14, 2026 Incident end time: 04:05 UTC May 15, 2026 Preliminary root cause: A recent update to Cortex Code introduced a code issue that caused Cortex Code in Snowsight to incorrectly halt responses, preventing requests from completing. A root cause analysis (RCA) document will be published within five business days.

Current status: After investigating, we've determined the issue is limited to internal Snowflake systems and did not affect customer replication operations. We've confirmed replication services are functioning normally. If you experience issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight.

Current status: 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. Customer experience: Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. Incident start time: 12:25 UTC April 16, 2026 Incident end time: 13:45 UTC April 16, 2026 Preliminary root cause: Some application instances entered a degraded state and were unable to handle downstream connections. Snowflake mitigated the issue by restarting the affected instances. A root cause analysis (RCA) document will be published within five business days.

Current status: 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. Customer experience: Customers hosted in the specified regions may have been unable to create or alter Snowflake alerts. Incident start time: 14:53 UTC March 14, 2026 Incident end time: 04:39 UTC March 17, 2026 Preliminary root cause: A recent improvement to Snowflake alerts creation and alteration contained a code issue. A root cause analysis (RCA) document will be published within five business days.

Current status: Our observations of service telemetry continue to indicate that our service has recovered following our mitigation. 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 experienced intermittent delays or failures when accessing or using Snowflake services and features. This may have included slower query execution, intermittent availability, or limited feature functionality. Incident start time: 19:26 UTC February 23, 2026 Incident end time: 21:11 UTC February 23, 2026 Preliminary root cause: A networking issue caused a component to be unable to process traffic and resolve DNS requests as expected. A root cause analysis (RCA) document will be published within five business days.