Snowflake Incident History

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 60 minutes.Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. Customers may observe new trial account creations failing and/or a blank white page/500 error returned upon logging into Snowsight. As an alternative, customers can log in using other methods, such as SnowSQL, connectors, etc.Incident start time: 03:20 UTC April 21, 2025

Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes.Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. Customers may observe new trial account creations failing and/or a blank white page/500 error returned upon logging into Snowsight. As an alternative, customers can log in using other methods, such as SnowSQL, connectors, etc.Incident start time: 15:32 UTC April 20, 2025

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.Customer experience: Customers hosted in the specified regions may have experienced delays while attempting to execute queries. Affected customers may have seen warehouses stuck in a "resuming" status. Additionally, replication to and from the specified region may have appeared stuck or delayed.Incident start time: 18:53 UTC April 16, 2025Incident end time: 19:42 UTC April 16, 2025Preliminary root cause: An infrastructure component that facilitates part of the warehouse provisioning process entered a degraded state.A root cause analysis (RCA) document will be published within seven 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 delays while attempting to execute queries. Affected customers may have seen warehouses stuck in a "resuming" status. Additionally, replication to and from the specified region may have appeared stuck or delayed.Incident start time: 18:53 UTC April 16, 2025Incident end time: 19:42 UTC April 16, 2025Preliminary root cause: An infrastructure component that facilitates part of the warehouse provisioning process entered a degraded state.

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 60 minutes.Customer experience: Customers hosted in the specified regions may experience delays while attempting to execute queries. Affected customers may see warehouses stuck in a "resuming" status.Incident start time: 18:53 UTC April 16, 2025

Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes.Customer experience: Customers hosted in the specified regions may experience delays while attempting to execute queries. Affected customers may see warehouses stuck in a "resuming" status.Incident start time: 18:53 UTC April 16, 2025

Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes.Customer experience: Customers hosted in the specified regions may experience delays while attempting to execute queries. Affected customers may see warehouses stuck in a "resuming" status.Incident start time: 06:53 UTC April 17, 2025

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.Customer experience: Customers hosted in the specified regions may have experienced delays while attempting to access or use Snowflake services and features.Incident start time: 21:00 UTC April 07, 2025Incident end time: 22:40 UTC April 07, 2025Preliminary root cause: A configuration change within the Metadata layer caused a temporary disruption when attempting to access Snowflake services and features.A root cause analysis (RCA) document will be published within seven 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 delays while attempting to access or use Snowflake services and features.Incident start time: 21:00 UTC April 07, 2025Incident end time: 22:40 UTC April 07, 2025Preliminary root cause: A configuration change within the Metadata layer caused a temporary disruption when attempting to access Snowflake services and features.

Current status: We're continuing to develop and implement a fix to restore service. We'll provide another update within 60 minutes.Customer experience: Customers hosted in the specified regions may experience delays while attempting to access or use Snowflake services and features.Incident start time: 21:00 UTC April 07, 2025

Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes.Customer experience: Customers hosted in the specified regions may experience delays or be unable to access or use Snowflake services and features.Incident start time: 21:00 UTC April 07, 2025

Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes.Customer experience: Customers hosted in the specified regions may experience delays while attempting to access or use Snowflake services and features.Incident start time: 21:00 UTC April 07, 2025

Current status: We've finished monitoring the environment and confirmed that all services are functioning properly. If you experience additional issues or have questions, please open a support case via Snowflake Community.Customer experience: Customers hosted in the specified regions may have experienced delays while attempting to execute queries. Affected customers might have encountered query failures.Incident start time: 11:00 UTC April 03, 2025Incident end time: 14:16 UTC April 03, 2025Preliminary root cause: An increase in load to an internal system resulted in elevated CPU utilization on the Cloud Services layer. Specifically, the increase in CPU caused a backlog on the infrastructure responsible for query processing, and as a result, customers may have experienced long-running and/or failed queries.A root cause analysis (RCA) document will be published within seven 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. Please note that our telemetry indicated recovery began at 14:16 UTC; however, this time may have varied as the backlog of requests was processed.Customer experience: Customers hosted in the specified regions may have experienced delays while attempting to execute queries. Affected customers might have encountered query failures.Incident start time: 11:00 UTC April 03, 2025Incident end time: 14:16 UTC April 03, 2025Preliminary root cause: An increase in load to an internal system resulted in elevated CPU utilization on the Cloud Services layer. Specifically, the increase in CPU caused a backlog on the infrastructure responsible for query processing, and as a result, customers may have experienced long-running and/or failed queries.

Current status: The mitigation actions we have taken are showing signs of recovery. We're continuing to monitor the environment while further investigating the source of the issue. We'll provide another update within the next 60 minutes.Customer experience: Customers hosted in the specified regions may experience delays while attempting to execute queries. Affected customers may encounter query failures.Incident start time: 11:00 UTC April 03, 2025

Current status: Our investigation identified that there was a recent increase in utilization on the Cloud service layer. We have taken action to reduce CPU utilization on the affected infrastructure as a potential mitigation strategy. We're continuing to monitor the environment and investigate the source of the issue. We'll provide another update within the next 60 minutes.Customer experience: Customers hosted in the specified regions may experience delays while attempting to execute queries. Affected customers may encounter query failures.Incident start time: 11:00 UTC April 03, 2025

Current status: We've confirmed that this issue impacts service, and we're continuing to investigate to determine the source of the issue. We'll provide another update within 60 minutes.Customer experience: Customers hosted in the specified regions may experience delays while attempting to execute queries. Affected customers may encounter query failures.Incident start time: 11:00 UTC April 03, 2025

Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes.Customer experience: Customers hosted in the specified regions may experience delays while attempting to execute queries. Affected customers may encounter query failures.Incident start time: 11:00 UTC April 03, 2025

Current status: We've confirmed that this issue impacts service, and we're continuing to investigate to determine the source of the issue. We'll provide another update within 60 minutes.Customer experience: Customers hosted in the specified regions may experience delays while attempting to execute queries. Affected customers may encounter query failures.Incident start time: 11:00 UTC April 03, 2025

Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes.Customer experience: Customers hosted in the specified regions may experience delays while attempting to execute queries. Affected customers may encounter query failures.Incident start time: 11:00 UTC April 03, 2025

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.Customer experience: Customers hosted in the specified regions may have observed that Snowpipe file ingestion is stopped or delayed.Incident start time: 11:08 UTC April 01, 2025Incident end time: 12:30 UTC April 01, 2025Preliminary root cause: Investigation discovered a configuration issue in a recent parameter that had been enabled. A root cause analysis (RCA) document will be published within seven 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 observed that Snowpipe file ingestion is stopped or delayed.Incident start time: 11:08 UTC April 01, 2025Incident end time: 12:30 UTC April 01, 2025Preliminary root cause: This issue appeared with the release of Snowflake version 9.8.1. At this time, the full root cause is still under investigation.

Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes.Customer experience: Customers hosted in the specified regions may observe that Snowpipe file ingestion is stopped or delayed.Incident start time: 11:08 UTC April 01, 2025

Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes.Customer experience: Customers hosted in the specified regions may observe that Snowpipe file ingestion is stopped or delayed.Incident start time: 11:08 UTC April 01, 2025

Current status: We've implemented the fix for this issue and monitored the environment to confirm that service was restored. Please note, customer recovery times may vary across the affected infrastructure. If you experience additional issues or have questions, please open a support case via Snowflake Community.Customer experience: Customers hosted in the AWS - US East (N. Virginia) and AWS - US West (Oregon) regions experienced intermittent delays or timeouts while attempting to perform queries or use Snowsight. Starting at approximately 16:00 UTC, customers hosted in the AWS - US East (N. Virginia) region were unable to access or use Snowflake services and features. Incident start time: 12:36 UTC March 19, 2025Incident end time: 19:45 UTC March 19, 2025Preliminary root cause: A code issue affecting an automatic scaling system triggered resource exhaustion and throttling on systems that process customer requests. After implementing an initial mitigation, a secondary, related issue was identified within a subset of the AWS - US East (N. Virginia) region that caused more severe impact to cloud services layer clusters that facilitate the scheduling of requests from virtual warehouses. The root cause of the secondary issue is currently under investigation. A root cause analysis (RCA) document will be published within seven business days.

Current status: All clusters are reporting service health recovery after implementing mitigations for this issue. Please note, customer recovery times may vary across the affected infrastructure. We'll continue to monitor the environment until we're confident all services are functioning properly.Customer experience: Customers hosted in the AWS - US East (N. Virginia) and AWS - US West (Oregon) regions experienced intermittent delays or timeouts while attempting to perform queries or use Snowsight. Starting at approximately 16:00 UTC, customers hosted in the AWS - US East (N. Virginia) region were unable to access or use Snowflake services and features. Incident start time: 12:36 UTC March 19, 2025Incident end time: 19:45 UTC March 19, 2025Preliminary root cause: A code issue affecting an automatic scaling system triggered resource exhaustion and throttling on systems that process customer requests. After implementing an initial mitigation, a secondary, related issue was identified within a subset of the AWS - US East (N. Virginia) region that caused more severe impact to cloud services layer clusters that facilitate the scheduling of requests from virtual warehouses. The root cause of the secondary issue is currently under investigation.

Current status: After our additional mitigation efforts, service health is recovering. We're continuing to implement optimizations and monitor the affected environments while the remaining cloud services layer clusters fully recover. As such, customer recovery times may vary across the affected infrastructure. Since resolution is being observed in the region, failing over is no longer recommended for customers with replication enabled in other regions unless they are continuing to experience impact. We'll provide another update within 60 minutes.Customer experience: Customers hosted in the AWS - US East (N. Virginia) region may be unable to access or use Snowflake services and features. Incident start time: 12:36 UTC March 19, 2025

Current status: Within the AWS - US East (N. Virginia) region, we have identified an additional issue preventing the cloud services layer from processing warehouse requests as expected due to resource contention issues. We're continuing to implement multiple mitigations to help remediate impact including increasing capacity and, in parallel, reverting the most recent software releases in the region. Customer experience: Customers hosted in the AWS - US East (N. Virginia) region may be unable to access or use Snowflake services and features. We recommend customers with replication enabled to other regions consider failing over outside of the AWS - US East (N. Virginia) region.Incident start time: 12:36 UTC March 19, 2025

Current status: We identified an issue affecting an automatic scaling system, triggering resource exhaustion and throttling on systems that process customer requests. After implementing an initial mitigation, we have seen some customer recovery across affected deployments; however, the AWS - US East (N. Virginia) region is continuing to see impact to warehouse operations. We are attempting to implement additional mitigations to reduce resource contention issues within the region, and we'll provide another update within 60 minutes.Customer experience: Customers hosted in the specified regions may experience delays or timeouts while attempting to perform queries or use Snowflake services and features via Snowsight. Queries may appear to be stuck in a running state. Customers hosted in the AWS - US East (N. Virginia) region may be unable to resume warehouses.Incident start time: 12:36 UTC March 19, 2025

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 60 minutes.Customer experience: Customers hosted in the specified regions may experience intermittent delays or timeouts while attempting to perform queries or use Snowflake services and features via Snowsight. Queries may appear to be stuck in a running state. Incident start time: 12:45 UTC March 19, 2025

Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes.Customer experience: Customers hosted in the specified regions may experience intermittent delays or timeouts while attempting to perform queries or use Snowflake services and features.Incident start time: 12:45 UTC March 19, 2025

Current status: We've finished monitoring the environment and confirmed that all services are functioning properly. If you experience additional issues or have questions, please open a support case via Snowflake Community.Customer experience: Customers hosted in the specified regions may have been intermittently unable to execute queries. The issue may have been more apparent when using connectors or when performing longer-running jobs.Incident start time: 22:00 UTC March 19, 2025Incident end time: 17:45 UTC March 20, 2025Preliminary root cause: A network change implemented as part of the mitigation actions for recent incident INC0129024 introduced a configuration issue that generated an elevated number of request redirects for a subset of operations routed through the cloud services layer.A root cause analysis (RCA) document will be published within seven business days.

Current status: We've confirmed that correcting the network configuration has resolved the impact as expected. We'll continue to monitor the environment to ensure all services are functioning properly.Customer experience: Customers hosted in the specified regions may have been intermittently unable to execute queries. The issue may have been more apparent when using connectors or when performing longer-running jobs.Incident start time: 22:00 UTC March 19, 2025Incident end time: 17:45 UTC March 20, 2025Preliminary root cause: A network change implemented as part of the mitigation actions for recent incident INC0129024 introduced a configuration issue that generated an elevated number of request redirects for a subset of operations routed through the cloud services layer.

Current status: After correcting the identified network configuration issue, internal telemetry indicates the increase in request redirects affecting customer operations has subsided. We're monitoring the environment to ensure service is restored.Customer experience: Customers hosted in the specified regions may be intermittently unable to execute queries. The issue may be more apparent when using connectors or when performing longer-running jobs.Incident start time: 22:00 UTC March 19, 2025

Current status: We identified a network configuration issue that may be causing an increase in request redirects for some customer operations. We are currently working to correct the configuration as a potential mitigation. Customer experience: Customers hosted in the specified regions may be intermittently unable to execute queries. The issue may be more apparent when using connectors or when performing longer-running jobs.Incident start time: 22:00 UTC March 19, 2025

Current status: We're investigating an issue with Snowflake Data Cloud intermittently affecting a subset of customers using connectors. We're investigating reported HTTP 307 errors to identify a mitigation, and we'll provide an update within 60 minutes.Customer experience: Customers hosted in the specified regions may be intermittently unable to execute queries when using connectors.Incident start time: 22:00 UTC March 19, 2025