Snowflake Outage History

Current status: We identified a subset of infrastructure that was unhealthy. We restarted that infrastructure and monitored the environment to confirm that the 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. Customer experience: Customers hosted in the specified regions may experience errors or connectivity issues when using Snowpark Container Services. Openflow users may be unable to access their runtimes, and Openflow Connectors may fail to pull data from sources or push data to Snowflake. Incident start time: 02:05 UTC April 29, 2026 Incident end time: 04:11 UTC April 29, 2026 Preliminary root cause: A subset of infrastructure that processes DNS requests in the affected region became unhealthy, which caused service connectivity failures for Snowpark Container Services and Openflow. 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 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 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. Customer experience: 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. Incident start time: 17:47 UTC April 07, 2026 Incident end time: 19:45 UTC April 07, 2026 Preliminary root cause: 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 failures, which correlated specifically to Snowsight availability issues in the region. A root cause analysis (RCA) document will be published within five business days.

Current status: We've confirmed that the infrastructure issue delaying deployment of the fix to the GCP - US East 4 (N. Virginia) region was resolved, and we have monitored the environment to confirm that the affected functionality is now working as expected. 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 may have been unable to see or manage their Native Apps within the "Apps" page of the Snowsight UI. App execution and all other Snowflake features were not impacted. SQL commands (e.g., SHOW APPLICATIONS) or searching for apps using the Catalog > Database Explorer page could still be used to view and manage Native Apps. Incident start time: 00:00 UTC March 27, 2026 Incident end time: 05:55 UTC March 29, 2026 Preliminary root cause: A recent Snowsight release introduced a code issue that caused an error to occur when attempting to load application metadata within the Apps page. This prevented the page from rendering the list of installed applications as expected. 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 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. Incident start time: 05:27 UTC March 21, 2026 Incident end time: 06:18 UTC March 21, 2026 Preliminary root cause: 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 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: We've confirmed that the rollback of the impacting Snowflake Intelligence update has completed, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified regions may have been unable to use Snowflake Intelligence services and features. Additionally, users may have experienced issues with expired sessions attempting to access Snowflake Intelligence. Existing sessions should have been unaffected. Workaround: While we were focused on remediation, users may have been able to work around the issue by accessing the service directly via the non-account-specific URL, AI.Snowflake.com, in a private browser tab. Incident start time: 16:30 UTC March 12, 2026 Incident end time: 20:39 UTC March 12, 2026 Preliminary root cause: An update intended to optimize Snowflake Intelligence introduced a code issue that caused problems with expired sessions attempting to access Snowflake Intelligence.

Current status: 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. Customer experience: 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. Incident start time: 19:30 UTC March 07, 2026 Incident end time: 21:10 UTC March 07, 2026 Preliminary root cause: 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 published within ten 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.