Snowflake experienced a major service incident in the Azure UK South (London) region lasting 1.4 hours, caused by an unhealthy DNS processing component. Customers were unable to access Snowflake Openflow runtimes and experienced connectivity issues with Snowpark Container Services, including failed data pulls and pushes through Openflow Connectors. The issue was resolved by restarting the affected infrastructure and monitoring the environment to confirm service restoration.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
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: An internal component responsible for processing 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 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 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: An internal component responsible for processing DNS requests in the affected region became unhealthy, which caused service connectivity failures for Snowpark Container Services and Openflow.
Current status: We're continuing to investigate the issue with Snowflake Data Cloud. We'll provide another update within 30 minutes.
Customer experience: Customers hosted in the specified regions may experience errors or connectivity issues when using Snowflake Openflow.
Incident start time: 02:05 UTC April 29, 2026
Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 30 minutes.
Customer experience: Customers hosted in the specified regions may experience errors or connectivity issues when using Snowflake Openflow.
Incident start time: 02:05 UTC April 29, 2026
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with