Snowflake

Mar 7, 22:20 UTC
Resolved - Current status: We've coordinated with our third-party cloud platform to confirm that the fix for this issue was successfully implemented, and we've monitored the environment to confirm that service has been fully 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 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.

Incident start time: 19:30 UTC March …

Mar 5, 04:39 UTC
Update - Current status: We continue to actively monitor the situation, and our cloud service provider affirms that meaningful progress is being made toward recovery, with several distinct services showing sustained improvement. While focused efforts continue toward full-service restoration for the region, the cloud service providers' initial advice to migrate your workloads and traffic to alternate Region(s) remains in place. We are in continuous contact with the provider and will post our next update once they confirm significant progress in restoring the site's physical environment, or when other material updates become available.

Customer experience: Customers hosted in the …

Feb 23, 22:07 UTC
Resolved - Current status: Our observations of service telemetry continue to indicate that our service has recovered following our mitigation. 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 intermittent delays or failures when accessing or using Snowflake services and features. This may have included slower query execution, intermittent availability, or limited feature functionality.

Incident start time: 19:26 UTC February 23, 2026
Incident end time: 21:11 UTC February 23, 2026

Preliminary root cause: A networking issue caused …