INC0148543

Final update

Current status: We've implemented the fix for this issue and monitored the environment to confirm that the service was restored. Some customers may experience delays in ingestion as the backlog of requests is cleared. If you experience additional issues or have questions, please open a support case via Snowflake Community. Customer experience: Customers hosted in the specified regions may have been unable to execute queries and may have experienced query performance degradation. Additionally, data clustering may have appeared to be in an unhealthy state. Users may have experienced delays or failures when using Snowpipe or Snowpipe Streaming to ingest files, and users may have seen a "SQL execution internal error" message or similar error messages. Workaround: There were no available workarounds for this issue except for customers with replication failing over to non-impacted regions. Incident start time: 02:55 UTC December 16, 2025 Incident end time: 15:59 UTC December 16, 2025 Preliminary root cause: Our initial investigation has identified that our most recent release introduced a backwards-incompatible database schema update. As a result, previous release packages incorrectly r

1. Resolved · Dec 16, 17:25 UTC
   Current status: We've implemented the fix for this issue and monitored the environment to confirm that the service was restored. Some customers may experience delays in ingestion as the backlog of requests is cleared. If you experience additional issues or have questions, please open a support case via Snowflake Community. Customer experience: Customers hosted in the specified regions may have been unable to execute queries and may have experienced query performance degradation. Additionally, data clustering may have appeared to be in an unhealthy state. Users may have experienced delays or failures when using Snowpipe or Snowpipe Streaming to ingest files, and users may have seen a "SQL execution internal error" message or similar error messages. Workaround: There were no available workarounds for this issue except for customers with replication failing over to non-impacted regions. Incident start time: 02:55 UTC December 16, 2025 Incident end time: 15:59 UTC December 16, 2025 Preliminary root cause: Our initial investigation has identified that our most recent release introduced a backwards-incompatible database schema update. As a result, previous release packages incorrectly referenced the updated fields, resulting in version mismatch errors and causing operations to fail or take an extended amount of time to complete. A root cause analysis (RCA) document will be published within five business days.