INC20000182

Final update

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

1. Postmortem · Sep 3, 21:03 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/INC20000182](https://community.snowflake.com/s/article/INC20000182)
2. Resolved · Aug 27, 20:26 UTC
   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 experienced connectivity issues when attempting to connect to Snowflake via private connectivity solutions, such as PrivateLink. Affected users may have encountered connection errors or timeouts. Incident start time: 18:21 UTC August 27, 2026 Incident end time: 19:34 UTC August 27, 2026 Preliminary root cause: A recent change intended to improve load balancer infrastructure health checks inadvertently introduced a configuration issue, which affected how private connectivity traffic was processed and resulted in connection failures. Once identified, we cycled the unhealthy infrastructure, restoring service. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.
3. Monitoring · Aug 27, 19:54 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 experienced connectivity issues when attempting to connect to Snowflake via private connectivity solutions, such as PrivateLink. Affected users may have encountered connection errors or timeouts. Incident start time: 18:21 UTC August 27, 2026 Incident end time: 19:34 UTC August 27, 2026 Preliminary root cause: A recent change intended to improve load balancer infrastructure health checks inadvertently introduced a configuration issue, which affected how private connectivity traffic was processed and resulted in connection failures. Once identified, we cycled the unhealthy infrastructure, restoring service.
4. Identified · Aug 27, 19:22 UTC
   Current status: We've identified the source of the issue, and we're implementing a fix to restore service. We'll provide another update within 1 hour. Customer experience: Customers hosted in the specified regions may experience connectivity issues when attempting to connect to Snowflake via private connectivity solutions, such as PrivateLink. Users may encounter connection errors or timeouts. ETA: Our current estimate is that service will be fully restored within 1 hour. Incident start time: 18:21 UTC August 27, 2026
5. Investigating · Aug 27, 19:05 UTC
   Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 1 hour. Customer experience: Customers hosted in the specified regions may experience connectivity issues when attempting to connect to Snowflake via private connectivity solutions, such as PrivateLink. Users may encounter connection errors or timeouts.