A configuration issue overloaded Snowflake's metadata database layer, causing cascading failures across Snowsight, Snowpipe, and core data warehouse operations from 15:10–15:50 UTC on June 24, 2026. Affected users were unable to sign in, execute queries, or manage data, with some experiencing elevated latency during recovery. Snowflake implemented a fix by 15:50 UTC and confirmed full service restoration by 17:22 UTC, with a formal RCA to follow within 5 business days.
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 region may have been unable to access or use Snowflake services and features using Snowsight. A subset of affected users in the region may also have been unable to execute queries, manage data, or may have experienced increased latency or performance issues with database operations.
Incident start time: 15:10 UTC June 24, 2026
Incident end time: 15:50 UTC June 24, 2026
Preliminary root cause: A configuration issue caused an unexpected increase in load on our metadata database layer, resulting in cascading impact to dependent services like Snowsight and database operations.
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 region may have been unable to access or use Snowflake services and features using Snowsight. A subset of affected users in the region may also have been unable to execute queries, manage data, or may have experienced increased latency or performance issues with database operations.
Incident start time: 15:10 UTC June 24, 2026
Incident end time: 15:50 UTC June 24, 2026
Preliminary root cause: A configuration issue caused an unexpected increase in load on our metadata database layer, resulting in cascading impact to dependent services like Snowsight and database operations.
Current status: We've identified the source of the issue, and we've implemented a fix to restore service. We're assessing the recovery of affected components and we'll provide another update within 30 minutes.
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. Following initial recovery actions, sign in functionality has been restored, but customers may observe some increased latency or performance issues until service has fully recovered.
ETA: Our current estimate is that service is recovering and will be fully restored within the next 30 minutes.
Incident start time: 15:10 UTC June 24, 2026
Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 30 minutes.
Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data.
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