Snowflake incident

INC20000237

Critical Resolved View vendor source →

Snowflake experienced a critical incident on September 25, 2026 affecting Databases, Tables, and Views and Virtual Warehouses and 1 more component, lasting 1h 20m. The incident has been resolved; the full update timeline is below.

Started
Sep 25, 2026, 11:00 PM UTC
Resolved
Sep 26, 2026, 12:20 AM UTC
Duration
1h 20m
Detected by Pingoru
Sep 25, 2026, 11:00 PM UTC

Affected components

Databases, Tables, and ViewsVirtual WarehousesData Loading and UnloadingApplicationsSecurity and Privacy Features

Update timeline

  1. investigating Sep 25, 2026, 11:00 PM 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 be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data, and may be unable to connect to Snowflake via private connectivity, such as AWS PrivateLink. Additionally, they may be unable to continuously stream data into Snowflake using Snowpipe Streaming.

  2. monitoring Sep 25, 2026, 11:26 PM 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 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, and may have been unable to connect to Snowflake via private connectivity, such as AWS PrivateLink. Additionally, they may have been unable to continuously stream data into Snowflake using Snowpipe Streaming. Incident start time: 22:35 UTC September 25, 2026 Incident end time: 22:59 UTC September 25, 2026 Preliminary root cause: Our internal metadata database infrastructure in the affected region became unavailable, resulting in connectivity failures across multiple Snowflake services.

  3. resolved Sep 26, 2026, 12:20 AM UTC

    Current status: We've implemented the fix for this issue and monitored the environment to confirm that service was restored. Most impact was resolved by 22:59 UTC, with the remaining backlog for scheduled and serverless task execution fully clearing by 23:43 UTC. 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, and may have been unable to connect to Snowflake via private connectivity, such as AWS PrivateLink. Additionally, they may have been unable to continuously stream data into Snowflake using Snowpipe Streaming, and customers using scheduled or serverless tasks may have experienced delayed task execution. Incident start time: 22:35 UTC September 25, 2026 Incident end time: 23:43 UTC September 25, 2026 Preliminary root cause: Our internal metadata database infrastructure in the affected region became unavailable, resulting in connectivity failures across multiple Snowflake services. A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.

  4. postmortem Oct 02, 2026, 11:36 PM 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/INC20000237](https://community.snowflake.com/s/article/INC20000237)