Is Snowflake down?

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 longer than expected warehouse resume and spin-up times for standard warehouses. All other Snowflake features are not impacted. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Workaround: There are currently no available workarounds for this issue. Incident start time: 07:45 UTC July 25, 2026

Current status: We've identified the source of the issue, and we're developing and implementing a fix to restore service. We'll provide another update within 1 hour. Customer experience: Customers hosted in the specified regions may experience intermittent delays or failures when accessing or using Snowflake services and features. This may include slower query execution, intermittent availability, or limited feature functionality. ETA: We're working with a third-party cloud platform to increase capacity limits. An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 07:45 UTC July 25, 2026 Preliminary root cause: Unexpected demand exceeded available capacity in the affected region, causing the third-party cloud platform to throttle provisioning requests.

Current status: We've identified the source of the issue, and we're developing and implementing a fix to restore service. We'll provide another update within 2 hours. Customer experience: Customers hosted in the specified region may be unable to resume warehouses or may experience delays with serverless tasks and other workloads that require compute resources. Queries may queue instead of executing immediately. ETA: We're working with a third-party cloud platform to remove throttling limits. An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 07:45 UTC July 25, 2026 Preliminary root cause: Unexpected demand exceeded available capacity in the affected region, causing the third-party cloud platform to throttle provisioning requests.

Current status: We've identified that IP address exhaustion in the affected region is preventing new compute resources from being provisioned, and we're implementing additional network capacity to restore service. We'll provide another update within 2 hours. Customer experience: Customers hosted in the specified region may be unable to resume warehouses or may experience significant delays with serverless tasks and other workloads that require compute resources. Queries may queue for extended periods instead of executing immediately, with some customers experiencing delays of several hours. ETA: We're implementing additional network capacity to resolve the IP address exhaustion. An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 07:45 UTC July 25, 2026 Preliminary root cause: Unexpected demand from a large-scale workload exceeded available network capacity in the affected region, causing IP address exhaustion that prevents new compute resources from being provisioned.

Current status: We've identified that IP address exhaustion in the affected region is preventing new compute resources from being provisioned, and we're implementing additional network capacity to restore service. We'll provide another update within 2 hours. Customer experience: Customers hosted in the specified region may be unable to resume warehouses or may experience significant delays with serverless tasks and other workloads that require compute resources. Queries may queue for extended periods instead of executing immediately, with some customers experiencing delays of several hours. ETA: We've implemented additional network capacity to resolve the IP address exhaustion. Service restoration is dependent on additional workload adjustments affecting resource consumption. An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 07:45 UTC July 25, 2026 Preliminary root cause: Unexpected demand from a large-scale workload exceeded available network capacity in the affected region, causing IP address exhaustion that prevents new compute resources from being provisioned.

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 resume warehouses or may have experienced significant delays with serverless tasks and other workloads that required compute resources. Queries may have queued for extended periods instead of executing immediately, with some customers experiencing delays of several hours. Workaround: There were no available workarounds for this issue. Incident start time: 07:45 UTC July 25, 2026 Incident end time: 15:05 UTC July 25, 2026 Preliminary root cause: Unexpected demand from a large-scale workload exceeded available network capacity in the affected region, causing resource exhaustion that prevented new compute resources from being provisioned.

Current status: We've confirmed that this issue has been resolved, and we have monitored the environment to confirm that the affected functionality is now working as expected. 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 resume warehouses or may have experienced significant delays with serverless tasks and other workloads that required compute resources. Queries may have queued for extended periods instead of executing immediately, with some customers experiencing delays of several hours. Workaround: There were no available workarounds for this issue. Incident start time: 07:45 UTC July 25, 2026 Incident end time: 15:05 UTC July 25, 2026 Preliminary root cause: Unexpected demand from a large-scale workload exceeded available network capacity in the affected region, causing resource exhaustion that prevented new compute resources from being provisioned. 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'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 delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that are already running may be unaffected. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 16:30 UTC July 11, 2026

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 delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that were already running may have been unaffected. Incident start time: 16:35 UTC July 11, 2026 Incident end time: 18:10 UTC July 11, 2026 Preliminary root cause: Resource exhaustion in the binary download service caused delays when virtual warehouses attempted to download required software components during startup.

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 delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that were already running may have been unaffected. Incident start time: 16:35 UTC July 11, 2026 Incident end time: 18:10 UTC July 11, 2026 Preliminary root cause: Resource exhaustion in the binary download service caused delays when virtual warehouses attempted to download required software components during startup. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

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

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 be unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. Users may encounter connection errors or timeouts. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. This may require DNS configuration changes for PrivateLink functionality.

Current status: Our telemetry indicates the PrivateLink connectivity health has recovered on July 10, 2026, at approximately 14:33 UTC, mitigating the impact for a majority of customers. We're continuing to investigate to isolate and address the source of the issue. Customer experience: Customers hosted in the specified regions may be unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. Users may encounter connection errors or timeouts. ETA: An ETA is not yet available. We'll provide one as soon as possible. Incident start time: 13:26 UTC July 10, 2026

Current status: We've confirmed PrivateLink connectivity health has recovered, 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 been unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. Users may have encountered connection errors or timeouts. Additionally, all customers using public connectivity may have been unable to access Snowsight between July 10, 2026, at 13:26 and 13:40 UTC. Incident start time: 13:26 UTC July 10, 2026 Incident end time: 14:33 UTC July 10, 2026 Preliminary root cause: Our preliminary root cause analysis identified that the load balancing infrastructure responsible for managing connections to Snowsight temporarily entered a degraded state, preventing requests from being processed successfully. We've engaged the associated Cloud Service Provider to investigate and troubleshoot this issue further.

Current status: We've 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 been unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. Users may have encountered connection errors or timeouts. Additionally, all customers using public connectivity may have been unable to access Snowsight between July 10, 2026, at 13:26 and 13:40 UTC. Incident start time: 13:26 UTC July 10, 2026 Incident end time: 14:33 UTC July 10, 2026 Preliminary root cause: Our preliminary root cause analysis identified that the load balancing infrastructure responsible for managing connections to Snowsight temporarily entered a degraded state, preventing requests from being processed successfully. We've engaged the associated Cloud Service Provider to investigate and troubleshoot this issue further. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

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

Current status: We're investigating an issue with Snowsight authentication. We are seeing recovery as of 22:03 UTC and are continuing to monitor. We'll provide an update within 60 minutes. Customer experience: Customers may be unable to access Snowsight or may experience being logged out unexpectedly. All other Snowflake features are not impacted. ETA: We have taken action to address the issue and expect it to be resolved as of 22:03 UTC. Incident start time: 21:47 UTC June 30, 2026

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. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified region may have been unable to access Snowsight or may have experienced being logged out unexpectedly. All other Snowflake features were not impacted. Workaround: While we were focused on remediation, customers who were logged out needed to log back in to Snowsight. Incident start time: 21:47 UTC June 30, 2026 Incident end time: 23:03 UTC June 30, 2026 Preliminary root cause: A routine system configuration change caused authentication issues with Snowsight. Once identified, the configuration was reverted.

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 Snowsight or may have experienced being logged out unexpectedly. All other Snowflake features were not impacted. Workaround: While we were focused on remediation, customers who were logged out needed to log back in to Snowsight. Incident start time: 21:47 UTC June 30, 2026 Incident end time: 23:03 UTC June 30, 2026 Preliminary root cause: A routine system configuration change caused authentication issues with Snowsight. Once identified, the configuration was reverted. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

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

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.

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'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 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.

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