Snowflake incident

Azure - UK South (London): INC0156355

Resolved after 1 hour 21 minutes, affecting Snowpark Container Services, on April 29, 2026.

postmortem May 07, 2026, 02:26 AM UTC

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/INC0156355](https://community.snowflake.com/s/article/INC0156355)

Started
Apr 29, 2026, 03:23 AM UTC
Resolved
Apr 29, 2026, 04:44 AM UTC
Duration
1h 21m
Detected by Pingoru
Apr 29, 2026, 03:23 AM UTC

Affected components

Snowpark Container Services

Update timeline

  1. investigating Apr 29, 2026, 03:23 AM UTC

    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

  2. investigating Apr 29, 2026, 03:53 AM UTC

    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

  3. monitoring Apr 29, 2026, 04:27 AM UTC

    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.

  4. resolved Apr 29, 2026, 04:44 AM UTC

    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.

  5. postmortem May 07, 2026, 02:26 AM UTC

    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/INC0156355](https://community.snowflake.com/s/article/INC0156355)

Your product runs on more than Snowflake

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →