On August 27, 2026, Snowflake experienced a ~1.4-hour outage (18:21–19:34 UTC) in which customers using private connectivity solutions such as PrivateLink encountered connection errors and timeouts. The root cause was a misconfiguration introduced by a change intended to improve load balancer health checks, which disrupted how private connectivity traffic was processed. Snowflake resolved the issue by cycling the unhealthy infrastructure, restoring service by 19:34 UTC.
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'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.
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.
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
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.
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