On October 18, 2026, a third-party cloud platform network issue caused intermittent private connectivity failures for Snowflake customers in the affected region, lasting approximately 45 minutes (23:07–23:37 UTC). Only new connection attempts were impacted, with some failing intermittently while existing connections remained stable. The issue was resolved by 23:37 UTC, with service confirmed restored shortly after.
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 monitored the environment and confirmed that 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 region who connect to Snowflake using private connectivity may have experienced intermittent failures when establishing new connections. Affected users may have seen some connection attempts fail while other attempts succeeded. Customers that are already connected were not impacted.
Incident start time: 23:07 UTC October 18, 2026
Incident end time: 23:37 UTC October 18, 2026
Preliminary root cause: A third-party cloud platform experienced a network connectivity issue, which caused private connectivity connection failures in the affected region.
A root cause analysis (RCA) will be conducted and a summary will be made available within 10 business days.
Current status: We identified an issue with our third-party cloud platform that affected private connectivity in the specified region. The issue has been resolved, and we're working with the provider to confirm the underlying cause. We'll continue to monitor the environment until we're confident all services are functioning properly.
Customer experience: Customers hosted in the specified regions who connect to Snowflake using private connectivity may have experienced intermittent failures when establishing new connections. Affected users may have seen some connection attempts fail while other attempts succeeded. Customers that are already connected were not impacted.
Incident start time: 23:07 UTC October 18, 2026
Incident end time: 23:37 UTC October 18, 2026
Preliminary root cause: A third-party cloud platform experienced a network connectivity issue, which caused private connectivity connection failures in the affected region.
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