Is Snowflake Down Right Now? Check if there is a current outage ongoing.

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight.

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to access or use Snowflake services and features. <b>Incident start time:</b> 02:22 UTC June 12, 2025

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. <b>Incident start time:</b> 01:31 UTC June 11, 2025

<b>Current status:</b> We've identified a recent configuration update that impacted a system service that facilitates replication of account metadata across U.S. regions supporting public sector workloads. We're developing and implementing a fix to restore service. We'll provide another update within 2 hours. <b>Customer experience:</b> A subset of customers hosted in the specified regions are unable to access Snowflake services and features, or are experiencing replication failures related to missing account organization metadata. This can result in HTTP 404 errors or failures when attempting to use Snowflake services and features that rely on organization name metadata or the <orgname>-<account_name> URL format. Additionally, affected customers may experience failures when attempting to manage failover groups. <b>Workaround:</b> For some impact scenarios, such as access via Snowsight or connectors, you may be able to workaround this issue by switching the account format you are using from an account name format (e.g. <orgname>-<account_name>) to a regioned account locator format, such as <account_locator>.<cloud_region_id>. Please see https://docs.snowflake.com/en/user-guide/admin-account-identifier#using-an-account-locator-as-an-identifier for more information on account identifier formats. ETA: An ETA is not yet available. <b>Incident start time:</b> 00:10 UTC June 10, 2025

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

<b>Current status:</b> 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. <b>Customer experience:</b> Customers in the affected deployments may have faced delays in resuming, or been unable to resume, virtual warehouses. Customers may also have faced delays in using Snowpark Container Services. <b>Incident start time:</b> 11:00 UTC May 20, 2025 <b>Incident end time:</b> 13:20 UTC May 20, 2025 <b>Preliminary root cause:</b> An internal change intended to optimize system efficiency had an unintended consequence that resulted in a temporary inability to provision service infrastructure. This resulted in performance degradation when attempting to use virtual warehouses and Snowpark Container Services. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers in the affected deployments may have faced delays in resuming, or been unable to resume, virtual warehouses. Customers may also have faced delays in using Snowpark Container Services. <b>Incident start time:</b> 11:00 UTC May 20, 2025 <b>Incident end time:</b> 13:20 UTC May 20, 2025 <b>Preliminary root cause:</b> An internal change intended to optimize system efficiency had an unintended consequence that resulted in a temporary inability to provision service infrastructure. This resulted in performance degradation when attempting to use virtual warehouses and Snowpark Container Services.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers in the affected deployments might face delays in resuming, or be unable to resume, virtual warehouses. Customers may also face delays in using Snowpark Container Services. <b>Incident start time:</b> 11:00 UTC May 20, 2025

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers in the affected deployments might face delays in resuming, or be unable to resume, virtual warehouses. Customers may also face delays in using Snowpark Container Services. <b>Incident start time:</b> 11:00 UTC May 20, 2025

Current status: This is a test of status.snowflake.com.Customer experience: There is no customer impact associated with this message, and no action is required.

Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes.Customer experience: Customers in the affected deployments might face delays in resuming, or be unable to resume, virtual warehouses. Customers may also face delays in using Snowpark Container Services.Incident start time: 11:00 UTC May 20, 2025

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

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. Customers may have observed new trial account creations failing and/or a blank white page/500 error being returned upon logging into Snowsight. As an alternative, customers were able to log in using other methods, such as SnowSQL, connectors, etc. <b>Incident start time:</b> 03:20 UTC April 21, 2025 <b>Incident end time:</b> 04:09 UTC April 21, 2025 <b>Preliminary root cause:</b> A third-party service provider experienced an issue upon completing a scheduled maintenance window, which affected the caching service used for logins to the Snowflake UI. Snowflake engineers were engaged and reverted to a secondary data system to mitigate impacts. A root cause analysis (RCA) document will be published within ten business days.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. Customers may have observed new trial account creations failing and/or a blank white page/500 error being returned upon logging into Snowsight. As an alternative, customers were able to log in using other methods, such as SnowSQL, connectors, etc. <b>Incident start time:</b> 03:20 UTC April 21, 2025 <b>Incident end time:</b> 04:09 UTC April 21, 2025 <b>Preliminary root cause:</b> A third-party service provider experienced an issue upon completing a scheduled maintenance window, which affected the caching service used for logins to the Snowflake UI. Snowflake engineers were engaged and reverted to a secondary data system to mitigate impacts.

<b>Current status:</b> 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. <b>Customer experience:</b> 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. <b>Incident start time:</b> 03:20 UTC April 21, 2025

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

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. Customers may have observed new trial account creations failing and/or a blank white page/500 error returned upon logging into Snowsight. As an alternative, customers were able to log in using other methods, such as SnowSQL, connectors, etc. <b>Incident start time:</b> 15:32 UTC April 20, 2025 <b>Incident end time:</b> 19:52 UTC April 20, 2025 <b>Preliminary root cause:</b> A third-party service provider experienced an issue upon completing a scheduled maintenance window, which affected the caching service used for logins to the Snowflake UI. Snowflake engineers were engaged and reverted to a secondary data system. A root cause analysis (RCA) document will be published within ten business days.

<b>Current status:</b> 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. <b>Customer experience:</b> 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. <b>Incident start time:</b> 15:32 UTC April 20, 2025 <b>Incident end time:</b> 19:52 UTC April 20, 2025 <b>Preliminary root cause:</b> A third-party service provider experienced an issue upon completing a scheduled maintenance window, which affected the caching service used for logins to the Snowflake UI. Snowflake engineers were engaged and reverted to a secondary data system.

<b>Current status:</b> 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. <b>Customer experience:</b> 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. <b>Incident start time:</b> 15:32 UTC April 20, 2025

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> 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. <b>Incident start time:</b> 15:32 UTC April 20, 2025

Python Connector UpdateAs of April 29, we have released a new version (3.15.0) of the Snowflake Python connector: https://pypi.org/project/snowflake-connector-python/3.15.0/.This update includes improved OCSP handling logic and permanently resolves the compatibility issue that previous versions of the Snowflake Python connector had after the recent certifi library change.To ensure proper functionality, we recommend upgrading to the latest version of the Snowflake Python connector in order to resolve the issue. Additional details will be provided in a customer-facing RCA, which will be made available within seven business days.

We've revised the message below to reflect the most recent details of the issue.

We've received reports that some customers hosted in AWS regions are experiencing certificate errors when using the Snowflake Python or Spark connectors to interact with AWS S3 external stages, and you may need to apply a temporary solution to work around the issue.What happened?Our findings indicate that the Python certifi library, which is used in specific Snowflake connectors, has recently been updated to remove trust for a legacy certificate previously used in the validation chain for S3 endpoints. The new version of the certifi certificate library (2025.4.26) exposed a latent code issue in the way that the Snowflake connector handles chain validation. Additional details will be provided in the customer-facing RCA, which will be shared following the release of an updated version of the connector.How will this affect my service?Customers hosted in AWS regions may encounter the error "The certificate is revoked or could not be validated" and are unable to use the Python and Spark connectors to perform specific operations that require an external AWS S3 stage with certificate check enabled. This issue primarily affects users who have recently upgraded the certifi library to version 2025.4.26.What action do I need to take?Potential temporary workarounds for customers with AWS EMR jobs may include the following:Reverting to the previous certifi library version (2025.1.31) to restore the recently removed certificate trust. Customers can revert to the previous version using “pip install certifi==2025.1.31”Configuring your Snowflake connector (Python/Spark) to operate in insecure_mode. This bypasses the certificate validation check (OCSP). Please be aware of the security implications before enabling this mode. Consult the connector documentation for instructions on enabling insecure_mode: https://community.snowflake.com/s/article/How-to-turn-off-OCSP-checking-in-Snowflake-client-driversFor customers running AWS Glue jobs, a possible workaround involves applying a Python environment change within your Glue job script or configuration, such as attempting to downgrade the certifi library manually.As the permanent solution to this issue with the Snowflake connector, we’re planning to release an updated version by April 30. We’ll update this post should alternative solutions be identified or further relevant details emerge. For more information about the certifi library update, please see the change history: https://pypi.org/project/certifi/2025.4.26/. For more information about the certificate authority update, please see the related AWS blog post: https://aws.amazon.com/blogs/security/acm-will-no-longer-cross-sign-certificates-with-starfield-class-2-starting-august-2024/

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

<b>Current status:</b> 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. <b>Customer experience:</b> 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. <b>Incident start time:</b> 18:53 UTC April 16, 2025 <b>Incident end time:</b> 19:42 UTC April 16, 2025 <b>Preliminary root cause:</b> 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.

<b>Current status:</b> 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. <b>Customer experience:</b> 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. <b>Incident start time:</b> 18:53 UTC April 16, 2025 <b>Incident end time:</b> 19:42 UTC April 16, 2025 <b>Preliminary root cause:</b> An infrastructure component that facilitates part of the warehouse provisioning process entered a degraded state.

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

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may experience delays while attempting to execute queries. Affected customers may see warehouses stuck in a "resuming" status. <b>Incident start time:</b> 18:53 UTC April 16, 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 been unable to access or use Snowflake services and features using Snowsight. Customers may have observed new trial account creations failing and/or a blank white page/500 error being returned upon logging into Snowsight. As an alternative, customers were able to log in using other methods, such as SnowSQL, connectors, etc.Incident start time: 03:20 UTC April 21, 2025Incident end time: 04:09 UTC April 21, 2025Preliminary root cause: A third-party service provider experienced an issue upon completing a scheduled maintenance window, which affected the caching service used for logins to the Snowflake UI. Snowflake engineers were engaged and reverted to a secondary data system to mitigate impacts.A root cause analysis (RCA) document will be published within ten 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 been unable to access or use Snowflake services and features using Snowsight. Customers may have observed new trial account creations failing and/or a blank white page/500 error being returned upon logging into Snowsight. As an alternative, customers were able to log in using other methods, such as SnowSQL, connectors, etc.Incident start time: 03:20 UTC April 21, 2025Incident end time: 04:09 UTC April 21, 2025Preliminary root cause: A third-party service provider experienced an issue upon completing a scheduled maintenance window, which affected the caching service used for logins to the Snowflake UI. Snowflake engineers were engaged and reverted to a secondary data system to mitigate impacts.

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'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'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 been unable to access or use Snowflake services and features using Snowsight. Customers may have observed new trial account creations failing and/or a blank white page/500 error returned upon logging into Snowsight. As an alternative, customers were able to log in using other methods, such as SnowSQL, connectors, etc.Incident start time: 15:32 UTC April 20, 2025Incident end time: 19:52 UTC April 20, 2025Preliminary root cause: A third-party service provider experienced an issue upon completing a scheduled maintenance window, which affected the caching service used for logins to the Snowflake UI. Snowflake engineers were engaged and reverted to a secondary data system. A root cause analysis (RCA) document will be published within ten 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 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, 2025Incident end time: 19:52 UTC April 20, 2025Preliminary root cause: A third-party service provider experienced an issue upon completing a scheduled maintenance window, which affected the caching service used for logins to the Snowflake UI. Snowflake engineers were engaged and reverted to a secondary data system.

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: 15:32 UTC April 20, 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'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

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

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have experienced delays while attempting to access or use Snowflake services and features. <b>Incident start time:</b> 21:00 UTC April 07, 2025 <b>Incident end time:</b> 22:40 UTC April 07, 2025 <b>Preliminary root cause:</b> 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.

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

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

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

A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC0130416](https://community.snowflake.com/s/article/INC0130416)

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have experienced delays while attempting to execute queries. Affected customers might have encountered query failures. <b>Incident start time:</b> 11:00 UTC April 03, 2025 <b>Incident end time:</b> 14:16 UTC April 03, 2025 <b>Preliminary root cause:</b> 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.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have experienced delays while attempting to execute queries. Affected customers might have encountered query failures. <b>Incident start time:</b> 11:00 UTC April 03, 2025 <b>Incident end time:</b> 14:16 UTC April 03, 2025 <b>Preliminary root cause:</b> 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.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may experience delays while attempting to execute queries. Affected customers may encounter query failures. <b>Incident start time:</b> 11:00 UTC April 03, 2025

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may experience delays while attempting to execute queries. Affected customers may encounter query failures. <b>Incident start time:</b> 11:00 UTC April 03, 2025

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may experience delays while attempting to execute queries. Affected customers may encounter query failures. <b>Incident start time:</b> 11:00 UTC April 03, 2025

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

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

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have observed that Snowpipe file ingestion is stopped or delayed. <b>Incident start time:</b> 11:08 UTC April 01, 2025 <b>Incident end time:</b> 12:30 UTC April 01, 2025 <b>Preliminary root cause:</b> 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.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have observed that Snowpipe file ingestion is stopped or delayed. <b>Incident start time:</b> 11:08 UTC April 01, 2025 <b>Incident end time:</b> 12:30 UTC April 01, 2025 <b>Preliminary root cause:</b> This issue appeared with the release of Snowflake version 9.8.1. At this time, the full root cause is still under investigation.

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may observe that Snowpipe file ingestion is stopped or delayed. <b>Incident start time:</b> 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. 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

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

<b>Current status:</b> 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. <b>Customer experience:</b> 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. <b>Incident start time:</b> 22:00 UTC March 19, 2025 <b>Incident end time:</b> 17:45 UTC March 20, 2025 <b>Preliminary root cause:</b> 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.

<b>Current status:</b> 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. <b>Customer experience:</b> 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. <b>Incident start time:</b> 22:00 UTC March 19, 2025 <b>Incident end time:</b> 17:45 UTC March 20, 2025 <b>Preliminary root cause:</b> 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.

<b>Current status:</b> 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. <b>Customer experience:</b> 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. <b>Incident start time:</b> 22:00 UTC March 19, 2025

<b>Current status:</b> 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. <b>Customer experience:</b> 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. <b>Incident start time:</b> 22:00 UTC March 19, 2025

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may be intermittently unable to execute queries when using connectors. <b>Incident start time:</b> 22:00 UTC March 19, 2025

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

<b>Current status:</b> 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. <b>Customer experience:</b> 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. <b>Incident start time:</b> 12:36 UTC March 19, 2025 <b>Incident end time:</b> 19:45 UTC March 19, 2025 <b>Preliminary root cause:</b> 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.

<b>Current status:</b> 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. <b>Customer experience:</b> 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. <b>Incident start time:</b> 12:36 UTC March 19, 2025 <b>Incident end time:</b> 19:45 UTC March 19, 2025 <b>Preliminary root cause:</b> 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.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the AWS - US East (N. Virginia) region may be unable to access or use Snowflake services and features. <b>Incident start time:</b> 12:36 UTC March 19, 2025

<b>Current status:</b> 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. <b>Customer experience:</b> 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. <b>Incident start time:</b> 12:36 UTC March 19, 2025

<b>Current status:</b> 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. <b>Customer experience:</b> 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. <b>Incident start time:</b> 12:36 UTC March 19, 2025

<b>Current status:</b> 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. <b>Customer experience:</b> 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. <b>Incident start time:</b> 12:45 UTC March 19, 2025

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

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

<b>Current status:</b> We've coordinated with our third-party service provider to implement the fix for this issue, and 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. <b>Customer experience:</b> Customers hosted in the specified regions may have experienced delays while attempting to execute queries. Affected customers might have encountered query failures. <b>Incident start time:</b> 21:30 UTC March 14, 2025 <b>Incident end time:</b> 22:40 UTC March 14, 2025 <b>Preliminary root cause:</b> A third-party service provider experienced a connectivity issue, which caused a delay with warehouse resume. A root cause analysis (RCA) document will be published within ten business days.

<b>Current status:</b> We've coordinated with our third-party service provider to implement the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. <b>Customer experience:</b> Customers hosted in the specified regions may have experienced delays while attempting to execute queries. Affected customers might have encountered query failures. <b>Incident start time:</b> 21:30 UTC March 14, 2025 <b>Incident end time:</b> 22:40 UTC March 14, 2025 <b>Preliminary root cause:</b> A third-party service provider experienced a connectivity issue, which caused a delay with warehouse resume.

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may experience delays while attempting to execute queries. Affected customers may encounter query failures. <b>Incident start time:</b> 21:30 UTC March 14, 2025

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

<b>Current status:</b> We've coordinated with our third-party service provider to implement the fix for this issue, and 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. <b>Customer experience:</b> Customers hosted in the specified regions may have been intermittently unable to execute queries. <b>Incident start time:</b> 23:11 UTC February 13, 2025 <b>Incident end time:</b> 00:21 UTC February 14, 2025 <b>Preliminary root cause:</b> A third-party service provider experienced a network issue, which caused connectivity issues when trying to use Snowflake services. A root cause analysis (RCA) document will be published within ten business days.

<b>Current status:</b> We've coordinated with our third-party service provider to implement the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. <b>Customer experience:</b> Customers hosted in the specified regions may have been intermittently unable to execute queries. <b>Incident start time:</b> 23:11 UTC February 13, 2025 <b>Incident end time:</b> 00:21 UTC February 14, 2025 <b>Preliminary root cause:</b> A third-party service provider experienced a network issue, which caused connectivity issues when trying to use Snowflake services.

<b>Current status:</b> We're continuing to coordinate with our third-party service provider to develop and implement a fix to restore service. We'll provide another update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may be intermittently unable to execute queries. <b>Incident start time:</b> 23:11 UTC February 13, 2025

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may be intermittently unable to execute queries. <b>Incident start time:</b> 23:11 UTC February 13, 2025

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

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to access or use Snowflake services and features via Snowpark Container Services. <b>Incident start time:</b> 18:49 UTC February 06, 2025 <b>Incident end time:</b> 02:51 UTC February 07, 2025 <b>Preliminary root cause:</b> An update intended to fix an unrelated issue unexpectedly caused a subset of Snowpark Container Services to fail. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to access or use Snowflake services and features via Snowpark Container Services. <b>Incident start time:</b> 18:49 UTC February 06, 2025 <b>Incident end time:</b> 02:51 UTC February 07, 2025 <b>Preliminary root cause:</b> An update intended to fix an unrelated issue unexpectedly caused a subset of Snowpark Container Services to fail.

<b>Current status:</b> A subset of customers should now see improvements as we continue making steady progress in reverting Snowflake software to its previous release to provide continued service. We'll provide another update within 2 hours. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to access or use Snowflake services and features via Snowpark Container Services. <b>Incident start time:</b> 18:49 UTC February 06, 2025

<b>Current status:</b> We're temporarily reverting Snowflake software to its previous release to provide continued service pending remediation of the current version. We'll provide another update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to access or use Snowflake services and features via Snowpark Container Services. <b>Incident start time:</b> 23:01 UTC February 06, 2025

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to access or use Snowflake services and features via Snowpark Container Services. <b>Incident start time:</b> 23:01 UTC February 06, 2025

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

<b>Current status:</b> 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. <b>Customer experience:</b> Customers may have observed that replication to and from the specified region is stopped or delayed and/or that Snowpipe file ingestion is stopped or delayed. <b>Incident start time:</b> 03:07 UTC February 12, 2025 <b>Incident end time:</b> 08:20 UTC February 12, 2025 <b>Preliminary root cause:</b> A configuration in the latest release caused Replication and Snowpipe file ingestion to be stopped or delayed. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> We've implemented the fix for this issue and will continue to monitor the environment until we're confident all services are functioning properly. Customers might still experience some delays as the backlog is being processed. <b>Customer experience:</b> Customers may have observed that replication to and from the specified region is stopped or delayed and/or that Snowpipe file ingestion is stopped or delayed. <b>Incident start time:</b> 03:07 UTC February 12, 2025 <b>Incident end time:</b> 08:20 UTC February 12, 2025 <b>Preliminary root cause:</b> A configuration in the latest release caused Replication and Snowpipe file ingestion to be stopped or delayed.

<b>Current status:</b> We've identified the source of the issue, and we continue developing and implementing a fix to restore service. We'll provide another update within 60 minutes. <b>Customer experience:</b> Customers may observe that replication to and from the specified region is stopped or delayed and/or that Snowpipe file ingestion is stopped or delayed. <b>Incident start time:</b> 03:07 UTC February 12, 2025

<b>Current status:</b> 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. <b>Customer experience:</b> Customers may observe that replication to and from the specified region is stopped or delayed and/or that Snowpipe file ingestion is stopped or delayed. <b>Incident start time:</b> 03:07 UTC February 12, 2025

<b>Current status:</b> We're continuing to investigate the issue with Snowflake Data Cloud. We'll provide another update within 60 minutes. <b>Customer experience:</b> Customers may observe that replication to and from the specified region is stopped or delayed and/or that Snowpipe file ingestion is stopped or delayed. <b>Incident start time:</b> 03:07 UTC February 12, 2025

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers may observe that replication to and from the specified region is stopped or delayed. <b>Incident start time:</b> 03:07 UTC February 12, 2025

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

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions experienced elevated warehouse resume delays while attempting to access or use Snowflake services and features. <b>Incident start time:</b> 01:03 UTC January 28, 2025 <b>Incident end time:</b> 04:56 UTC January 28, 2025 <b>Preliminary root cause:</b> A subset of Snowflake systems encountered performance degradation, which caused elevated virtual warehouse resume delays. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may experience elevated warehouse resume delays while attempting to access or use Snowflake services and features. <b>Incident start time:</b> 01:03 UTC January 28, 2025 <b>Incident end time:</b> 04:56 UTC January 28, 2025 <b>Preliminary root cause:</b> A subset of Snowflake systems encountered performance degradation, which caused elevated virtual warehouse resume delays.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may experience elevated warehouse resume delays while attempting to access or use Snowflake services and features. <b>Incident start time:</b> 01:00 UTC January 28, 2025

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 2 hours. <b>Customer experience:</b> Customers hosted in the specified regions may experience elevated warehouse resume delays while attempting to access or use Snowflake services and features. <b>Incident start time:</b> 01:00 UTC January 28, 2025

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

<b>Current status:</b> 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. <b>Customer experience:</b> Customers may have experienced delays or been unable to resume Virtual Warehouses. <b>Incident start time:</b> 12:00 UTC January 28, 2025 <b>Incident end time:</b> 17:43 UTC January 28, 2025 <b>Preliminary root cause:</b> A system responsible for infrastructure management entered a degraded state, causing a queue of requests to form related to warehouse provisioning. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> We've implemented an additional mitigation to speed up processing the backlog of requests, and warehouse resume latency has returned to normal as of 17:45 UTC. We'll continue to monitor the environment until we're confident all services are functioning properly. <b>Customer experience:</b> Customers may have experienced delays or been unable to resume Virtual Warehouses. <b>Incident start time:</b> 12:00 UTC January 28, 2025 <b>Incident end time:</b> 17:45 UTC January 28, 2025 <b>Preliminary root cause:</b> A system responsible for infrastructure management entered a degraded state, causing a queue of requests to form related to warehouse provisioning.

<b>Current status:</b> We have observed an improvement after scaling up associated infrastructure provisioning systems; however, we still expect an extended period of time required to process the backlog of requests. We are attempting to implement additional mitigation options to help speed up the processing of requests. We'll provide another update within 90 minutes. <b>Customer experience:</b> Customers may not be able to resume Virtual Warehouses. <b>Incident start time:</b> 12:00 UTC January 28, 2025

<b>Current status:</b> We've identified a system responsible for infrastructure management entered a degraded state, causing a queue of requests to form related to warehouse provisioning. We have scaled up associated provisioning systems to help process the backlog of requests while we continue to investigate the source of the issue. We'll provide another update within 60 minutes. <b>Customer experience:</b> Customers may not be able to resume Virtual Warehouses. <b>Incident start time:</b> 12:00 UTC January 28, 2025

<b>Current status:</b> We have an indication of the source of the issue, and we're developing a fix to restore service. We'll provide another update within 60 minutes. <b>Customer experience:</b> Customers might not be able to resume Virtual Warehouses. <b>Incident start time:</b> 12:00 UTC January 28, 2025

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers might not be able to resume Virtual Warehouses. <b>Incident start time:</b> 12:00 UTC January 28, 2025

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

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. <b>Incident start time:</b> 09:24 UTC January 29, 2025 <b>Incident end time:</b> 10:00 UTC January 29, 2025 <b>Preliminary root cause:</b> A transient networking issue caused Snowsight unavailability in several regions. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. <b>Incident start time:</b> 09:25 UTC January 29, 2025 <b>Incident end time:</b> 10:00 UTC January 29, 2025 <b>Preliminary root cause:</b> A transient networking issue caused Snowsight unavailability in several regions.

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. Incident start time: 09:25 UTC January 29, 2025

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. <b>Incident start time:</b> 09:25 UTC January 29, 2025

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

<b>Current status:</b> We've coordinated with our third-party service provider to implement the fix for this issue, and 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. <b>Customer experience:</b> Customers hosted in the specified region may experience delays while attempting to access or use Snowflake services and features. Virtual warehouses may be delayed in a resuming state. <b>Incident start time:</b> 00:01 UTC January 09, 2025 <b>Incident end time:</b> 15:10 UTC January 10, 2025 <b>Preliminary root cause:</b> A third-party service provider experienced a network configuration issue, which caused a subset of storage partitions to become unhealthy. This resulted in intermittent virtual machine connectivity issues and failures in allocating or communicating with resources in the region. The nature of this incident prevented standard workarounds, such as bypassing the affected availability zones, which prolonged recovery time. A root cause analysis (RCA) document will be published within ten business days.

<b>Current status:</b> We continue to work with our third-party service provider as they address the underlying cause of this incident, previously identified as INC0123659, which resulted in prolonged warehouse resume times and delays when accessing or utilizing Snowflake services and features. The third-party provider's recovery plan has been completed and they continue to see signs of recovery. They are monitoring telemetry to confirm the issue is fully resolved. Our internal telemetry indicates the majority of the impact to Snowflake services and features recovered at 21:20 UTC on January 9, 2025; the remaining impact recovered at 15:10 UTC on January 10, 2025. Due to the nature of the issue, we're conducting an extended period of monitoring to ensure the impact doesn't return. We'll continue monitoring over the weekend and through peak traffic hours, and we'll provide another update within 72 hours. <b>Customer experience:</b> Customers hosted in the specified region may experience delays while attempting to access or use Snowflake services and features. Virtual warehouses may be delayed in a resuming state. <b>Incident start time:</b> 00:01 UTC January 09, 2025 <b>Incident end time:</b> 15:10 UTC January 10, 2025 <b>Preliminary root cause:</b> A third-party service provider experienced a network configuration issue, which caused a subset of storage partitions to become unhealthy. This resulted in intermittent virtual machine connectivity issues and failures in allocating or communicating with resources in the region. The nature of this incident prevented standard workarounds, such as bypassing affected availability zones, which prolonged recovery time.

<b>Current status:</b> We continue to work with our third-party service provider as they address the underlying cause of this incident, previously identified as INC0123659, which resulted in prolonged warehouse resume times and delays when accessing or utilizing Snowflake services and features. The third-party provider's recovery plan has been completed and they are seeing signs of recovery; however, they continue to validate that the issue has been fully resolved. We remain committed to monitoring the situation closely and implementing measures wherever possible to maintain service continuity. Our next update will be shared within three hours or sooner if we receive significant developments from the third-party provider. <b>Customer experience:</b> Customers hosted in the specified region may experience delays while attempting to access or use Snowflake services and features. Virtual warehouses may be delayed in a resuming state. <b>Incident start time:</b> 00:01 UTC January 09, 2025

<b>Current status:</b> We continue to work with our third-party service provider as they address the underlying cause of this incident, previously identified as INC0123659, which resulted in prolonged warehouse resume times and delays when accessing or utilizing Snowflake services and features. The third-party provider's recovery plan remains underway, however, full resolution continues to require an extended timeline. Snowflake's previously implemented mitigation strategies - such as reallocating resources and increasing capacity in high-demand areas - are unchanged, minimizing the impact for many of our customers. We remain committed to monitoring the situation closely and implementing measures wherever possible to maintain service continuity. The third-party provider has confirmed the issue stemmed from a configuration change within their regional networking service, which resulted in an inconsistent service state across a subset of storage partitions. This caused intermittent virtual machine connectivity issues, failures in allocating or communicating with resources in the region. The nature of this incident prevented standard workarounds, such as bypassing the impacted availability zones, which prolonged recovery time. Our next update will be shared within three hours or sooner if we receive significant developments from the third-party provider. <b>Customer experience:</b> Customers hosted in the specified region may experience delays while attempting to access or use Snowflake services and features. Virtual warehouses may be delayed in a resuming state. <b>Incident start time:</b> 00:01 UTC January 09, 2025

<b>Current status:</b> We continue to collaborate with our third-party service provider to address this incident, previously identified as INC0123659, which resulted in prolonged warehouse resume times and delays when accessing or utilizing Snowflake services and features. The third-party provider's recovery plan is ongoing, however, they continue to indicate full resolution will require an extended timeline. Snowflake's previously implemented mitigation strategies - such as reallocating resources and increasing capacity in high-demand areas - are holding in place, reducing the impact for many of our customers. We remain committed to monitoring the situation closely and implementing measures wherever possible to maintain service continuity. The third-party provider has confirmed the issue stemmed from a configuration change within their regional networking service, which resulted in an inconsistent service state across a subset of storage partitions. This caused intermittent virtual machine connectivity issues, failures in allocating or communicating with resources in the region. The nature of this incident prevented standard workarounds, such as bypassing the impacted availability zones, which prolonged recovery time. Our next update will be shared within three hours or sooner if we receive significant developments from the third-party provider. <b>Customer experience:</b> Customers hosted in the specified region may experience delays while attempting to access or use Snowflake services and features. Virtual warehouses may be delayed in a resuming state. <b>Incident start time:</b> 00:01 UTC January 09, 2025

<b>Current status:</b> We remain in close collaboration with our third-party service provider to address the ongoing incident, previously identified as INC0123659, which contributed to prolonged warehouse resume times and delays when accessing or utilizing Snowflake services and features. The third-party provider is making progress on their recovery plan but continue to indicate an extended timeline for full resolution. Snowflake's previously implemented mitigation strategies - such as reallocating resources and increasing capacity in high-demand areas - remain effective in reducing the impact for many of our customers. We remain committed to monitoring the situation closely and implementing measures wherever possible to maintain service continuity. The third-party provider shares that the issue stemmed from a configuration change within their regional networking service, which resulted in an inconsistent service state. This caused intermittent virtual machine connectivity issues, failures in allocating or communicating with resources in the region. The nature of this incident prevented standard workarounds, such as bypassing the impacted availability zones, which prolonged recovery time. Our next update will be shared within three hours or sooner if we receive significant developments from the third-party provider. <b>Customer experience:</b> Customers hosted in the specified region may experience delays while attempting to access or use Snowflake services and features. Virtual warehouses may be delayed in a resuming state. <b>Incident start time:</b> 00:01 UTC January 09, 2025

<b>Current status:</b> We remain in close collaboration with our third-party service provider to address the ongoing incident, previously identified as INC0123659, which has been contributing to prolonged warehouse resume times and delays when accessing or utilizing Snowflake services and features. The third-party provider continues to meticulously advance toward recovery but consistently indicates that resolution requires extended recovery time. Snowflake remains committed to monitoring the situation closely and is ready to apply the necessary mitigation strategies, such as reallocating resources and increasing capacity in high-demand areas, if required. The third-party provider shares that the issue stemmed from a configuration change within their regional networking service, which resulted in an inconsistent service state. This caused intermittent virtual machine connectivity issues or failures in allocating resources or communicating with resources in the region. The nature of this incident prevented standard workarounds, such as bypassing the impacted availability zones, which prolongs recovery time. Our next update will be shared within three hours or sooner if we receive significant developments from the third-party provider. <b>Customer experience:</b> Customers hosted in the specified region may experience delays while attempting to access or use Snowflake services and features. Virtual warehouses may be delayed in a resuming state. <b>Incident start time:</b> 00:01 UTC January 09, 2025

<b>Current status:</b> We remain in close collaboration with our third-party service provider to address the ongoing incident, previously identified as INC0123659, which has been contributing to prolonged warehouse resume times and delays when accessing or utilizing Snowflake services and features. As per the previous update from the third-party provider, a configuration change in a regional networking service resulted in an inconsistent service state, resulting in intermittent virtual machine connectivity issues or failures in allocating resources or communicating with resources in the region. The nature of this incident prevented standard workarounds, such as bypassing the impacted availability zones. The provider is actively advancing its recovery process and continues to indicate that resolution requires extended recovery time. Snowflake's previously implemented mitigation strategies - such as reallocating resources and increasing capacity in high-demand areas - continue to reduce the impact for many of our customers. We remain committed to monitoring the situation closely and optimizing our measures wherever possible to further improve service continuity. Our next update will be shared within three hours or sooner if we receive significant developments from the third-party provider. <b>Customer experience:</b> Customers hosted in the specified region may experience delays while attempting to access or use Snowflake services and features. Virtual warehouses may be delayed in a resuming state. <b>Incident start time:</b> 00:01 UTC January 09, 2025

<b>Current status:</b> We are continuing to coordinate with our third-party service provider to fully recover from an incident recently posted to our status page (INC0123659). As per the previous update from the third-party provider, a configuration change in a regional networking service resulted in an inconsistent service state, resulting in intermittent virtual machine connectivity issues or failures in allocating resources or communicating with resources in the region. Snowflake is designed to support multiple availability zones within the third-party provider's infrastructure. However, the nature of the impact prevents potential workarounds such as bypassing the impacted availability zones within the provider. The service provider continues to work towards service restoration and advises an extended recovery time. In parallel, we have taken measures to alleviate impacts by reallocating available resources and increasing the number of virtual warehouses where demand is high. Some customers have experienced improved performance as a result of these actions. We will provide another update within three hours or as updates are shared by the third-party provider. <b>Customer experience:</b> Customers hosted in the specified region may experience delays while attempting to access or use Snowflake services and features. Virtual warehouses may be delayed in a resuming state. <b>Incident start time:</b> 00:01 UTC January 09, 2025

<b>Current status:</b> We are continuing to coordinate with our third-party service provider to fully recover from an incident posted to our status page earlier today (INC0123659). Per the third-party provider, a configuration change in a regional networking service resulted in an inconsistent service state, causing intermittent virtual machine connectivity issues or failures in allocating resources or communicating with resources in the region. While Snowflake is designed to support multiple availability zones within the third-party provider's infrastructure, the nature of the impact prevents potential workarounds such as bypassing the impacted availability zones within the provider. While the service provider continues to work towards service restoration, they report that extended recovery times are expected. In parallel, we are continuing to investigate any opportunities to assist with mitigation or providing impact relief, such as reallocating available resources and increasing the number of available virtual warehouses whenever possible. We will provide another update within three hours or as updates are shared by the third-party provider. <b>Customer experience:</b> Customers hosted in the specified region may experience delays while attempting to access or use Snowflake services and features. Virtual warehouses may be delayed in a resuming state. <b>Incident start time:</b> 00:01 UTC January 09, 2025

<b>Current status:</b> Snowflake have identified residual impact that may be occurring as a result of ongoing efforts by a third-party service provider to fully recover from an incident posted to our Status Page earlier today (INC0123659). We are continuing to liase with this service provider, who have confirmed a networking issue in the impacted region that remains the focus of their ongoing recovery actions. We are still coordinating with the provider as they work towards service restoration. A fix continues to be gradually rolled out, but extended recovery times are expected. We will provide another update within two hours or as updates are shared by the third-party provider. <b>Customer experience:</b> Customers hosted in the specified region may experience delays while attempting to access or use Snowflake services and features. Virtual warehouses may be delayed in a resuming state. <b>Incident start time:</b> 00:01 UTC January 09, 2025

<b>Current status:</b> Snowflake have identified residual impact that may be occurring as a result of ongoing efforts by a third-party service provider to fully recover from an incident posted to our Status Page earlier today (INC0123659). We are continuing to liase with this service provider, who have confirmed a networking issue in the impacted region that remains the focus of their ongoing recovery actions. We are still coordinating with the provider as they work towards service restoration, and a fix continues to be gradually rolled out. We will provide another update within two hours or as updates are shared by the third-party provider. <b>Customer experience:</b> Customers hosted in the specified region may experience delays while attempting to access or use Snowflake services and features. Virtual warehouses may be delayed in a resuming state. <b>Incident start time:</b> 00:01 UTC January 09, 2025

<b>Current status:</b> Snowflake have identified residual impact that may be occurring as a result of ongoing efforts by a third-party service provider to fully recover from an incident posted to our Status Page earlier today (INC0123659). We are continuing to liase with this service provider, who have confirmed a networking issue in the impacted region that remains the focus of their ongoing recovery actions. We are still coordinating with the provider as they work towards service restoration, and a fix continues to be gradually rolled out. A potential workaround was investigated by Snowflake engineers, but determined to not be feasible for this situation. We will provide another update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may experience delays while attempting to access or use Snowflake services and features. <b>Incident start time:</b> 00:01 UTC January 09, 2025

<b>Current status:</b> Snowflake have identified residual impact that may be occurring as a result of ongoing efforts by a third-party service provider to fully recover from an incident posted to our Status Page earlier today (INC0123659). We are continuing to liase with this service provider, who have confirmed a networking issue in the impacted region that remains the focus of their ongoing recovery actions. This notification has been posted to advise customers on the affected region of this residual impact as the service provider continues their work to fully restore service. We are still coordinating with the provider as they work towards service restoration. The fix continues to be gradually rolled out. Additionally, Snowflake engineers are investigating available actions to move impacted workloads to a stable service zone in the meantime. We will provide another update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may experience delays while attempting to access or use Snowflake services and features. <b>Incident start time:</b> 00:01 UTC January 09, 2025

<b>Current status:</b> Snowflake have identified residual impact that may be occurring as a result of ongoing efforts by a third-party service provider to fully recover from an incident posted to our Status Page earlier today (INC0123659). We are continuing to liase with this service provider, who have confirmed a networking issue in the impacted region that remains the focus of their ongoing recovery actions. This notification has been posted to advise customers on the affected region of this residual impact as the service provider continues their work to fully restore service. We are still coordinating with the provider as they work towards service restoral. The fix continues to be gradually rolled out, and customers should start to see signs of recovery. We will provide another update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may experience delays while attempting to access or use Snowflake services and features. <b>Incident start time:</b> 00:01 UTC January 09, 2025

<b>Current status:</b> Snowflake have identified residual impact that may be occurring as a result of ongoing efforts by a third-party service provider to fully recover from an incident posted to our Status Page earlier today (INC0123659). We are continuing to liase with this service provider, who have confirmed a networking issue in the impacted region that remains the focus of their ongoing recovery actions. This notification has been posted to advise customers on the affected region of this residual impact as the service provider continues their work to fully restore service. We are coordinating with them as they work towards service restoral. A fix is being applied by the service provider and is in the process of being gradually rolled out. We will provide another update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may experience delays while attempting to access or use Snowflake services and features. <b>Incident start time:</b> 00:01 UTC January 09, 2025

<b>Current status:</b> Snowflake have identified residual impact that may be occurring as a result of ongoing efforts by a third-party service provider to fully recover from an incident posted to our Status Page earlier today (INC0123659). We are actively liaising with this service provider, who confirmed a networking issue in the impacted region that remains the focus of their ongoing recovery actions. This notification has been posted to advise customers on the affected region of this residual impact as the service provider continues their work to fully restore service. We're coordinating with them as they work towards service restoral and we'll provide another update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may experience delays while attempting to access or use Snowflake services and features. <b>Incident start time:</b> 00:01 UTC January 09, 2025

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

<b>Current status:</b> We've coordinated with our third-party service provider to implement the fix for this issue, and 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. <b>Customer experience:</b> Customers hosted in the specified region may have experienced delays while attempting to resume virtual warehouses or execute queries. <b>Incident start time:</b> 00:01 UTC January 09, 2025 <b>Incident end time:</b> 04:10 UTC January 09, 2025 <b>Preliminary root cause:</b> A third-party service provider experienced a networking issue that impacted a subset of their infrastructure which caused Snowflake customers to experience elevated warehouse resume times. A root cause analysis (RCA) document will be published within ten business days.

<b>Current status:</b> We've coordinated with our third-party service provider, who has confirmed that the primary networking issue has been resolved. Recovery efforts are ongoing to restore service fully. As these actions continue, customers should see improvements in the performance of affected services. <b>Customer experience:</b> Customers hosted in the specified region may have experienced delays while attempting to resume virtual warehouses or execute queries. <b>Incident start time:</b> 00:01 UTC January 09, 2025 <b>Incident end time:</b> 04:10 UTC January 09, 2025 <b>Preliminary root cause:</b> A third-party service provider experienced a networking issue that impacted a subset of their infrastructure which caused Snowflake customers to experience elevated warehouse resume times.

<b>Current status:</b> We continue coordinating with our third-party service provider to develop and implement a fix to restore service. Our service provider has confirmed that networking issues are affecting customers. They currently don't have an ETA available, but we remain fully engaged in efforts to restore service. We'll provide another update within two hours or as the event warrants. <b>Customer experience:</b> Customers hosted in the specified region may experience delays while attempting to resume virtual warehouses or execute queries. <b>Incident start time:</b> 00:01 UTC January 09, 2025

<b>Current status:</b> We're continuing to coordinate with our third-party service provider to develop and implement a fix to restore service. Our service provider does not currently have an ETA available, but we remain actively engaged. We'll provide another update within two hours. <b>Customer experience:</b> Customers hosted in the specified region may experience delays while attempting to resume virtual warehouses or execute queries. <b>Incident start time:</b> 00:01 UTC January 09, 2025

<b>Current status:</b> We've identified an issue with a third-party service provider, and we're coordinating with the provider to develop and implement a fix to restore service. We'll provide another update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified region may experience delays while attempting to resume virtual warehouses or execute queries. <b>Incident start time:</b> 00:01 UTC January 09, 2025

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

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may intermittently experience delays or failures while attempting to use various Snowflake services and features. <b>Incident start time:</b> 14:00 UTC December 17, 2024 <b>Incident end time:</b> 23:42 UTC December 17, 2024 <b>Preliminary root cause:</b> The current root cause investigation is focused on a recent load balancer change that manages transaction IDs in order to minimize conflicts within the metadata database. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may intermittently experience delays or failures while attempting to use various Snowflake services and features. <b>Incident start time:</b> 14:00 UTC December 17, 2024 <b>Incident end time:</b> 23:42 UTC December 17, 2024 <b>Preliminary root cause:</b> The current root cause investigation is focused on a recent load balancer change that manages transaction IDs in order to minimize conflicts within the metadata database.

<b>Current status:</b> We're continuing to investigate the issue with Snowflake Data Cloud. The current investigation is focused on a recent load balancer change that manages transaction IDs in order to minimize conflicts within the metadata database. We'll provide another update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may intermittently experience delays or failures while attempting to use various Snowflake services and features. <b>Incident start time:</b> 14:00 UTC December 17, 2024

<b>Current status:</b> We're continuing to investigate the issue with Snowflake Data Cloud. We'll provide another update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may intermittently experience delays or failures while attempting to use various Snowflake services and features. <b>Incident start time:</b> 14:00 UTC December 17, 2024

<b>Current status:</b> We're continuing to investigate the issue with Snowflake Data Cloud. We'll provide another update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may intermittently experience delays or failures while attempting to use various Snowflake services and features. <b>Incident start time:</b> 14:00 UTC December 17, 2024

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may intermittently experience delays or failures while attempting to use various Snowflake services and features. <b>Incident start time:</b> 14:00 UTC December 17, 2024

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

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have experienced delays while attempting to execute queries. Affected customers might have encountered query failures. <b>Incident start time:</b> 12:10 UTC December 19, 2024 <b>Incident end time:</b> 13:40 UTC December 19, 2024 <b>Preliminary root cause:</b> A limited number of metadata database storage servers experienced connectivity issues in the region. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have experienced delays while attempting to execute queries. Affected customers might have encountered query failures. <b>Incident start time:</b> 12:10 UTC December 19, 2024 <b>Incident end time:</b> 13:40 UTC December 19, 2024 <b>Preliminary root cause:</b> A limited number of metadata database storage servers experienced connectivity issues in the region.

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may experience delays while attempting to execute queries. Affected customers may encounter query failures. <b>Incident start time:</b> 12:10 UTC December 19, 2024

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

<b>Current status:</b> We've monitored the environment and confirmed the service is restored. If you experience additional issues or have questions, please open a support case via Snowflake Community. <b>Customer experience:</b> Customers hosted in the specified regions may have experienced delays starting and resuming virtual warehouses. Affected customers may have seen virtual warehouses stuck in a resuming state. <b>Incident start time:</b> 18:11 UTC December 03, 2024 <b>Incident end time:</b> 20:08 UTC December 03, 2024 <b>Preliminary root cause:</b> A configuration change introduced in a previous Snowflake release was not compatible with the most recent release, which caused the virtual warehouse start and resume delays experienced by affected customers. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> We've disabled the configuration change and have received confirmation from a subset of affected customers that the impact is resolved. Our internal signals also indicate the issue is mitigated, and we'll continue to monitor the environment until we are confident that all services are functioning properly. <b>Customer experience:</b> Customers hosted in the specified regions may have experienced delays starting and resuming virtual warehouses. Affected customers may have seen virtual warehouses stuck in a resuming state. <b>Incident start time:</b> 18:11 UTC December 03, 2024 <b>Incident end time:</b> 20:08 UTC December 03, 2024 <b>Preliminary root cause:</b> A configuration change introduced in a previous Snowflake release was not compatible with the most recent release, which caused the virtual warehouse start and resume delays experienced by affected customers.

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may experience delays starting and resuming virtual warehouses. Affected customers may see virtual warehouses stuck in a resuming state.

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

<b>Current status:</b> We've coordinated with our third-party service provider to implement the fix for this issue, and 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. <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to resume virtual warehouses for the duration of the issue. <b>Incident start time:</b> 01:00 UTC November 13, 2024 <b>Incident end time:</b> 07:00 UTC November 13, 2024 <b>Preliminary root cause:</b> An update performed by the cloud service provider (CSP), intended to improve network services, caused DNS resolution issues inside an Azure store, which in turn caused virtual warehouse provisioning issues. A root cause analysis (RCA) document will be published within ten business days.

<b>Current status:</b> We're continuing to coordinate with our third-party service provider to develop and implement a fix to restore service. While the service provider does not currently have an ETA available, our telemetry indicates improvements in service in Azure - West Europe (Netherlands) and Azure - East US 2 (Virginia). We will provide another update within two hours. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to resume virtual warehouses. <b>Incident start time:</b> 01:00 UTC November 13, 2024

We are continuing to work on a fix for this issue.

<b>Current status:</b> We're continuing to coordinate with our third-party service provider to develop and implement a fix to restore service. There is not currently an ETA available from the service provider. We'll provide another update within two hours. <b>Customer experience:</b> Customers hosted in the specified region may experience delays while attempting to resume virtual warehouses or execute queries. <b>Incident start time:</b> 01:00 UTC November 13, 2024

<b>Current status:</b> We've identified an issue with a third-party service provider, and we're coordinating with the provider to develop and implement a fix to restore service. We'll provide another update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified region may experience delays while attempting to resume virtual warehouses or execute queries. <b>Incident start time:</b> 01:00 UTC November 13, 2024

<b>Current status:</b> We're continuing to investigate to determine the source of the issue. We'll provide another update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified region may experience delays while attempting to resume virtual warehouses or execute queries. <b>Incident start time:</b> 01:00 UTC November 13, 2024

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified region may experience delays while attempting to resume virtual warehouses or execute queries

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

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. <b>Incident start time:</b> 19:23 UTC November 04, 2024 <b>Incident end time:</b> 20:10 UTC November 04, 2024 <b>Preliminary root cause:</b> We identified a recent network configuration change that resulted in an increase in connectivity failures. We reverted the configuration change to restore service. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. <b>Incident start time:</b> 19:23 UTC November 04, 2024 <b>Incident end time:</b> 20:11 UTC November 04, 2024 <b>Preliminary root cause:</b> We identified a recent network configuration change that resulted in an increase in connectivity failures. We reverted the configuration change to restore service.

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight.

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

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have experienced delays resuming warehouses or query failures with the error message: "SQL execution internal error: Processing aborted due to error 300004:867554464". <b>Incident start time:</b> 09:30 UTC October 14, 2024 <b>Incident end time:</b> 14:02 UTC October 14, 2024 <b>Preliminary root cause:</b> After investigation, the cause was found to be due to a configuration issue within a specific parameter that was recently enabled as part of Snowflake release 8.39. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may experience delays resuming warehouses or query failures with the error message: "SQL execution internal error: Processing aborted due to error 300004:867554464". <b>Incident start time:</b> 09:30 UTC October 14, 2024 <b>Incident end time:</b> 13:50 UTC October 14, 2024 <b>Preliminary root cause:</b> After investigation, the cause was found to be due to a configuration issue within a specific parameter that was recently enabled as part of Snowflake release 8.39.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may experience delays resuming warehouses or query failures with the error message: "SQL execution internal error: Processing aborted due to error 300004:867554464". <b>Workaround:</b> To avoid issues resuming warehouses, please avoid suspending those warehouses already running. <b>Incident start time:</b> 09:30 UTC October 14, 2024

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may experience delays resuming warehouses or query failures with the error message: "SQL execution internal error: Processing aborted due to error 300004:867554464". <b>Workaround:</b> To avoid issues resuming warehouses, please avoid suspending those warehouses already running. <b>Incident start time:</b> 09:30 UTC October 14, 2024

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

<b>Current status:</b> We've coordinated with our third-party service provider to implement the fix for this issue, and 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. <b>Customer experience:</b> Customers hosted in the specified regions may have experienced delays while attempting to access or use Snowflake services and features using Snowsight. Customers not already signed into Snowsight may have seen an error message when attempting to sign in. <b>Incident start time:</b> 21:13 UTC October 02, 2024 <b>Incident end time:</b> 21:40 UTC October 02, 2024 <b>Preliminary root cause:</b> A subset of infrastructure that facilitates Snowsight operations and sign-in requests entered a degraded state. This caused some active requests to become queued until the impact was remediated by automated recovery processes. A root cause analysis (RCA) document will be published within ten business days.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have experienced delays while attempting to access or use Snowflake services and features using Snowsight. Customers not already signed into Snowsight may have seen an error message when attempting to sign in. <b>Incident start time:</b> 21:13 UTC October 02, 2024 <b>Incident end time:</b> 21:40 UTC October 02, 2024 <b>Preliminary root cause:</b> A subset of infrastructure that facilitates Snowsight operations and sign-in requests entered a degraded state. This caused some active requests to become queued until the impact was remediated by automated recovery processes.

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may experience delays while attempting to access or use Snowflake services and features using Snowsight. <b>Incident start time:</b> 21:13 UTC October 02, 2024

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

<b>Current status:</b> 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. <b>Customer experience:</b> Customers may have experienced delays or issues when accessing Snowflake services and features via Snowsight. The nature of the issue caused impact based on a user's geographic region and was not specific to a particular region in which a user or account was hosted. Symptoms included blank pages, error messages, or a spinning Snowflake logo. <b>Incident start time:</b> 23:06 UTC August 13, 2024 <b>Incident end time:</b> 07:30 UTC August 14, 2024 <b>Preliminary root cause:</b> An update intended to enhance Snowsight performance and reliability resulted in impact to the underlying mechanisms controlling access rendering a subset of users unable to log in to Snowsight. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the affected regions may experience delays or issues when accessing Snowflake services and features via Snowsight. Users might encounter symptoms such as blank pages, error messages, or being able to log in only through a different browser after entering their credentials. <b>Incident start time:</b> 23:06 UTC August 14, 2024 <b>Incident end time:</b> 07:30 UTC August 14, 2024 <b>Preliminary root cause:</b> An update intended to enhance Snowsight performance and reliability resulted in impact to the underlying mechanisms controlling access rendering a subset of users unable to log in to Snowsight

<b>Current status:</b> We're continuing to develop and implement a fix to restore service. We'll provide another update within 2 hours. <b>Customer experience:</b> Customers hosted in the affected regions may experience delays or issues when accessing Snowflake services and features via Snowsight. Users might encounter symptoms such as blank pages, error messages, or being able to log in only through a different browser after entering their credentials. <b>Incident start time:</b> 23:06 UTC August 14, 2024

<b>Current status:</b> 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 120 minutes. <b>Customer experience:</b> Customers hosted in the affected regions may experience delays or issues when accessing Snowflake services and features via Snowsight. Users might encounter symptoms such as blank pages, error messages, or being able to log in only through a different browser after entering their credentials. <b>Incident start time:</b> 03:00 UTC August 14, 2024

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 using Snowsight. Incident start time: 03:00 UTC August 14, 2024

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may experience delays while attempting to access or use Snowflake services and features using Snowsight. <b>Incident start time:</b> 03:00 UTC August 14, 2024

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

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified region may experience delays while attempting to resume virtual warehouses or execute queries. <b>Incident start time:</b> 03:00 UTC September 09, 2024 <b>Incident end time:</b> 06:36 UTC September 09, 2024 <b>Preliminary root cause:</b> An unexpected increase in resource utilization within the region. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified region may experience delays while attempting to resume virtual warehouses or execute queries. <b>Incident start time:</b> 03:00 UTC September 09, 2024 <b>Incident end time:</b> 06:36 UTC September 09, 2024 <b>Preliminary root cause:</b> An unexpected increase in resource utilization within the region.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified region may experience delays while attempting to resume virtual warehouses or execute queries. <b>Incident start time:</b> 03:00 UTC September 09, 2024

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may experience delays while attempting to access or use Snowflake services and features. <b>Incident start time:</b> 03:00 UTC September 09, 2024

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

<b>Current status:</b> We've applied remediation action for the identified issue and confirmed that service health metrics have returned to normal after restarting the affected components. We're continuing to closely monitor the environment while we further investigate the underlying root cause with our cloud provider, and we'll provide a preliminary summary of our root cause investigation within two business days. If you experience additional issues or have questions, please open a support case via Snowflake Community. <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. <b>Incident start time:</b> 19:34 UTC August 08, 2024 <b>Incident end time:</b> 21:27 UTC August 08, 2024 <b>Preliminary root cause:</b> Our engineering team is collaborating with the Cloud Service Provider to address a stalled process that would have eventually led to the issues experienced by Snowsight users. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. <b>Incident start time:</b> 19:34 UTC August 08, 2024 <b>Incident end time:</b> 21:27 UTC August 08, 2024 <b>Preliminary root cause:</b> Our preliminary investigation identified that a logging mechanism was experiencing unexpected behavior, which resulted in high resource utilization on the storage infrastructure responsible for managing access requests for Snowsight.

<b>Current status:</b> We've implemented a fix and have observed that some customers are experiencing relief. However, we're continuing to investigate to ensure our mitigation strategy is effective. We'll provide another update within 30 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. <b>Incident start time:</b> 19:34 UTC August 08, 2024

<b>Current status:</b> We've identified an issue affecting the database infrastructure supporting Snowsight and are preparing a mitigation to restore service. We'll provide another update within 30 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. <b>Incident start time:</b> 19:34 UTC August 08, 2024

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. <b>Incident start time:</b> 19:34 UTC August 08, 2024

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

<b>Current status:</b> 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. <b>Customer experience:</b> Customers connecting to Snowflake services may have experienced a certificate revoked error. <b>Incident start time:</b> 02:17 UTC August 01, 2024 <b>Incident end time:</b> 14:29 UTC August 01, 2024 <b>Preliminary root cause:</b> A certificate configuration error within our load balancing infrastructure prevented requests to access the service from completing successfully. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers connecting to Snowflake services may have experienced a certificate revoked error. <b>Incident start time:</b> 02:17 UTC August 01, 2024 <b>Incident end time:</b> 14:29 UTC August 01, 2024 <b>Preliminary root cause:</b> A certificate configuration error within our load balancing infrastructure prevented requests to access the service from completing successfully.

<b>Current status:</b> We've identified the source of the issue, and are taking action to mitigate this. Customers across the deployment should start to see service resume as these actions progress. We'll provide another update within 60 minutes. <b>Customer experience:</b> Customers connecting to Snowflake services may experience a certificate revoked error. <b>Incident start time:</b> 02:17 UTC August 01, 2024

<b>Current status:</b> We've identified the source of the issue, and we're continuing to develop and implement a fix to restore service. We'll provide another update within 120 minutes. <b>Customer experience:</b> Customers connecting to Snowflake services may experience a certificate revoked error. <b>Incident start time:</b> 02:17 UTC August 01, 2024

<b>Current status:</b> We've identified the source of the issue, and we're continuing to develop and implement a fix to restore service. We'll provide another update within 120 minutes. <b>Customer experience:</b> Customers connecting to Snowflake services may experience a certificate revoked error. <b>Incident start time:</b> 02:17 UTC August 01, 2024

<b>Current status:</b> We've identified the source of the issue, and we're continuing to develop and implement a fix to restore service. We'll provide another update within 120 minutes. <b>Customer experience:</b> Customers connecting to Snowflake services may experience a certificate revoked error. <b>Incident start time:</b> 02:17 UTC August 01, 2024

<b>Current status:</b> 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. <b>Customer experience:</b> Customers connecting to Snowflake services may experience a certificate revoked error. <b>Incident start time:</b> 02:17 UTC August 01, 2024

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers connecting to Snowflake services may experience certificate revoked error. <b>Incident start time:</b> 02:17 UTC August 01, 2024

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

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified region(s) may have experienced an inability to execute scheduled tasks via automated or manual procedures. Please note: In the Task History UI page, task executions impacted by this incident may appear in the table function for showing task graphs that are currently running (CURRENT_TASK_GRAPHS) even though they are not currently running, and those same executions may not appear in the table function for showing task graphs that are complete (COMPLETE_TASK_GRAPHS). Additionally, tasks that were impacted by this incident may not have upcoming scheduled task entries in task history if the next scheduled execution is over 2 hours in the future. <b>Incident start time:</b> 06:30 UTC July 30, 2024 <b>Incident end time:</b> 16:50 UTC July 30, 2024 <b>Preliminary root cause:</b> An error within a task maintenance activity resulted in task schedules becoming unavailable, preventing them from running as expected. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified region(s) may have experienced an inability to execute scheduled tasks via automated or manual procedures. Please note: In the Task History UI page, task executions impacted by this incident may appear in the table function for showing task graphs that are currently running (CURRENT_TASK_GRAPHS) even though they are not currently running, and those same executions may not appear in the table function for showing task graphs that are complete (COMPLETE_TASK_GRAPHS). Additionally, tasks that were impacted by this incident may not have upcoming scheduled task entries in task history if the next scheduled execution is over 2 hours in the future. <b>Incident start time:</b> 06:30 UTC July 30, 2024 <b>Incident end time:</b> 16:50 UTC July 30, 2024 <b>Preliminary root cause:</b> An error within a task maintenance activity resulted in task schedules becoming unavailable, preventing them from running as expected.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified region(s) may experience an inability to execute scheduled tasks via automated or manual procedures. <b>Workaround:</b> As an immediate workaround, customers are advised to recreate and replace any business critical tasks while Snowflake teams continue to actively work on restoring service. <b>Incident start time:</b> 06:30 UTC July 30, 2024 <b>Incident end time:</b> 16:50 UTC July 30, 2024 <b>Preliminary root cause:</b> An error within a task maintenance activity resulted in task schedules becoming unavailable, preventing them from running as expected.

<b>Current status:</b> We've identified an issue with Snowflake Data Cloud, resulting in the reported inability to execute scheduled tasks, along with a mitigation plan. The execution of the mitigation plan is in progress. We'll provide an update within 2 hours. <b>Customer experience:</b> Customers hosted in the specified region(s) may experience an inability to execute scheduled tasks via automated or manual procedures. <b>Workaround:</b> As an immediate workaround, customers are advised to recreate and replace any business critical tasks while Snowflake teams continue to actively work on restoring service. <b>Incident start time:</b> 06:30 UTC July 30, 2024

<b>Current status:</b> We've identified an issue with Snowflake Data Cloud resulting in the reported inability to execute scheduled tasks and are working to mitigate this issue. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified region(s) may experience an inability to execute scheduled tasks via automated or manual procedures. <b>Workaround:</b> As an immediate workaround, customers are advised to recreate and replace any business critical tasks while Snowflake teams continue to actively work on restoring service. <b>Incident start time:</b> 06:30 UTC July 30, 2024

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud relating to issues with running scheduled tasks. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified region(s) may experience an inability to execute scheduled tasks via automated or manual procedures. <b>Workaround:</b> As an immediate workaround, customers are advised to recreate and replace any business critical tasks while Snowflake teams actively work to restore service.

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

<b>Current status:</b> We've coordinated with our third-party service provider to implement the fix for this issue, and 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. <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to access or use Snowflake services and features. <b>Incident start time:</b> 22:33 UTC July 18, 2024 <b>Incident end time:</b> 05:30 UTC July 19, 2024 <b>Preliminary root cause:</b> A third-party service provider experienced an issue during a configuration change, which caused connectivity issues for Snowflake services in the impacted region. A root cause analysis (RCA) document will be published within ten business days.

<b>Current status:</b> Our third-party service provider has confirmed that they have implemented a fix to restore service on their platform, and the majority of their services are now restored. Snowflake Engineering has completed additional restoration actions to return to full operational health. We will continue to monitor the environment until we're confident all services are functioning properly. <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to access or use Snowflake services and features. <b>Incident start time:</b> 22:33 UTC July 18, 2024 <b>Incident end time:</b> 05:30 UTC July 19, 2024 <b>Preliminary root cause:</b> A third-party service provider experienced an issue during a configuration change, which caused connectivity issues for Snowflake services in the impacted region.

<b>Current status:</b> Our third-party service provider has confirmed that they have implemented a fix to restore service on their platform, and the majority of their services are now restored. Snowflake Engineering continues to complete restoration actions to return to full operational health. We'll provide another update within 2 hours. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to access or use Snowflake services and features. <b>Workaround:</b> There are currently no available workarounds for this issue. <b>Incident start time:</b> 22:33 UTC July 18, 2024

<b>Current status:</b> We're continuing to coordinate with our third-party service provider to develop and implement a fix to restore service. Our third-party service provider has identified the root cause on their end and is now in the process of applying the fix to mitigate the issue. We'll provide another update within 2 hours. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to access or use Snowflake services and features. <b>Workaround:</b> There are currently no available workarounds for this issue. <b>Incident start time:</b> 22:33 UTC July 18, 2024

<b>Current status:</b> We're continuing to coordinate with our third-party service provider to develop and implement a fix to restore service. We'll provide another update within 2 hours. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to access or use Snowflake services and features. <b>Workaround:</b> There are currently no available workarounds for this issue. <b>Incident start time:</b> 22:33 UTC July 18, 2024

<b>Current status:</b> We're continuing to coordinate with our third-party service provider to develop and implement a fix to restore service. We'll provide another update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to access or use Snowflake services and features. <b>Workaround:</b> There are currently no available workarounds for this issue.

<b>Current status:</b> We've identified an issue with a third-party service provider, and we're coordinating with the provider to develop and implement a fix to restore service. We'll provide another update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to access or use Snowflake services and features.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to access or use Snowflake services and features.

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to access or use Snowflake services and features.

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

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. <b>Incident start time:</b> 20:04 UTC July 09, 2024 <b>Incident end time:</b> 01:51 UTC July 10, 2024 <b>Preliminary root cause:</b> An update intended to help customers manage access to their network resources more effectively inadvertently caused an unexpected service interruption for some customers. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> We're temporarily reverting Snowflake software to its previous release to provide continued service pending remediation of the current version. We'll provide another update within 2 hours. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. <b>Incident start time:</b> 20:04 UTC July 09, 2024

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight.

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

<b>Current status:</b> We've coordinated with our third-party service provider to implement the fix for this issue, and 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. <b>Customer experience:</b> Customers hosted in the specified regions may have experienced delays while attempting to access or use Snowflake services and features. <b>Incident start time:</b> 03:42 UTC July 12, 2024 <b>Incident end time:</b> 06:30 UTC July 12, 2024 <b>Preliminary root cause:</b> A third-party service provider experienced an issue associated with subset of critical services, which affected Snowflake server capacity. A root cause analysis (RCA) document will be published within ten business days.

<b>Current status:</b> We've coordinated with our third-party service provider to implement the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. <b>Customer experience:</b> Customers hosted in the specified regions may have experienced delays while attempting to access or use Snowflake services and features. <b>Incident start time:</b> 03:42 UTC July 12, 2024 <b>Incident end time:</b> 06:30 UTC July 12, 2024 <b>Preliminary root cause:</b> A third-party service provider experienced an issue associated with subset of critical services, which affected Snowflake server capacity.

<b>Current status:</b> We've identified an issue with a third-party service provider, and we're coordinating with the provider to develop and implement a fix to restore service. We'll provide another update within 2 hours. <b>Customer experience:</b> Customers hosted in the specified regions may have experienced delays while attempting to access or use Snowflake services and features. <b>Incident start time:</b> 03:42 UTC July 12, 2024

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified region maybe experiencing delays while attempting to resume virtual warehouses or execute queries

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

<b>Current status:</b> We implemented the fix for this issue on July 03, 2024, at 16:44 UTC, 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. <b>Customer experience:</b> Users in the affected region(s) intermittently were unable to sign in or use the Snowflake service via Snowsight. As the issue was intermittent, attempting to reload the page or sign in again may have succeeded. <b>Incident start time:</b> 15:22 UTC July 03, 2024 <b>Incident end time:</b> 16:44 UTC July 03, 2024 <b>Preliminary root cause:</b> This issue recurred with the previously reported problems associated with incidents INC0110718, INC0110871, and INC0111066. Our investigation revealed an additional configuration change, which added resource pressure to the affected database infrastructure including memory usage. Our engineering teams actively monitored and analyzed all components of the affected database and confirmed we have addressed the contributing factors that resulted in intermittent increases in connection requests A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> Since implementing the latest fixes within the affected environment on July 03, 2024, at 16:44 UTC, there have been no additional periods of impact. We are continuing to monitor the environment closely and will provide another update by 23:00 UTC on July 9, 2024. <b>Customer experience:</b> Users in the affected region(s) intermittently may have been unable to sign in or use the Snowflake service via Snowsight. As the issue was intermittent, attempting to reload the page or sign in again may have succeeded. <b>Incident start time:</b> 15:22 UTC July 03, 2024 <b>Incident end time:</b> 16:44 UTC July 03, 2024 <b>Preliminary root cause:</b> This issue is a recurrence of the previously reported problems associated with incidents INC0110718, INC0110871, and INC0111066. Our latest investigation revealed an additional configuration change, adding resource pressure to the affected database infrastructure. We have now reverted this configuration change. Meanwhile, our engineering teams are actively monitoring and analyzing all components of the affected database to ensure no other factors contribute to the intermittent increases in connection requests.

<b>Current status:</b> There have been no further recurrences since implementing our latest configuration change at 16:44 UTC. We will continue to monitor the environment closely over the weekend and during peak traffic periods on Monday, July 8. We will provide another update by 23:00 UTC on July 8. <b>Customer experience:</b> Users in the affected region(s) intermittently may be unable to sign in or use the Snowflake service via Snowsight. As the issue is intermittent, attempting to reload the page or sign in again may succeed. <b>Incident start time:</b> 15:22 UTC July 03, 2024 <b>Incident end time:</b> 16:44 UTC July 03, 2024 <b>Preliminary root cause:</b> This issue is a recurrence of the previously reported problems associated with incidents INC0110718, INC0110871, and INC0111066. Our latest investigation revealed an additional configuration change, adding resource pressure to the affected database infrastructure. We have now reverted this configuration change. Meanwhile, our engineering teams are actively monitoring and analyzing all components of the affected database to ensure no other factors contribute to the intermittent increases in connection requests.

<b>Current status:</b> There have been no further recurrences since implementing our latest configuration change at 16:44 UTC. We will continue to monitor the environment closely during peak traffic during business hours and provide another update within 24 hours. <b>Customer experience:</b> Users in the affected region(s) intermittently may be unable to sign in or use the Snowflake service via Snowsight. As the issue is intermittent, attempting to reload the page or sign in again may succeed. <b>Incident start time:</b> 15:22 UTC July 03, 2024 <b>Incident end time:</b> 16:44 UTC July 03, 2024 <b>Preliminary root cause:</b> This issue is a recurrence of the previously reported problems associated with incidents INC0110718, INC0110871, and INC0111066. Our latest investigation revealed an additional configuration change, adding resource pressure to the affected database infrastructure. We have now reverted this configuration change. Meanwhile, our engineering teams are actively monitoring and analyzing all components of the affected database to ensure no other factors contribute to the intermittent increases in connection requests.

<b>Current status:</b> There have been no further recurrences since the implementation of our latest configuration change at 16:44 UTC. Further validations are ongoing to ensure system stability. We will continue to monitor the environment closely and provide another update within two hours. <b>Customer experience:</b> Users in the affected region(s) intermittently may be unable to sign in or use the Snowflake service via Snowsight. As the issue is intermittent, attempting to reload the page or sign in again may succeed. <b>Incident start time:</b> 15:22 UTC July 03, 2024 <b>Incident end time:</b> 16:44 UTC July 03, 2024 <b>Preliminary root cause:</b> This issue is a recurrence of the previously reported problems associated with incidents INC0110718, INC0110871, and INC0111066. Our latest investigation revealed an additional configuration change that was adding resource pressure to the affected database infrastructure. We have now reverted this configuration change. Meanwhile, our engineering teams are actively monitoring and analyzing all components of the affected database to ensure there are no other factors contributing to the intermittent increases in connection requests.

<b>Current status:</b> We continue to not see any further reoccurrence of impact since 16:44 UTC following our latest configuration change. We will monitor the environment closely and provide another update within two hours. <b>Customer experience:</b> Users in the affected region(s) intermittently may be unable to sign in or use the Snowflake service via Snowsight. As the issue is intermittent, attempting to reload the page or sign in again may succeed. <b>Incident start time:</b> 15:22 UTC July 03, 2024 <b>Incident end time:</b> 16:44 UTC July 03, 2024 <b>Preliminary root cause:</b> This issue is a recurrence of the previously reported impact associated with issues INC0110718, INC0110871, and INC0111066. The most recent investigation identified an additional configuration change contributing to resource pressure against the affected database infrastructure, and we have reverted the identified configuration change. In parallel, engineering teams are continuing to monitor and analyze all components of the affected database to ensure there are no additional factors contributing to the intermittent increases in connection requests.

<b>Current status:</b> We have seen no further reoccurrence of impact since 16:44 UTC following our latest configuration change. We will continue to closely monitor the environment and provide another update within two hours. <b>Customer experience:</b> Users in the affected region(s) intermittently may be unable to sign in or use the Snowflake service via Snowsight. As the issue is intermittent, attempting to reload the page or sign in again may succeed. <b>Incident start time:</b> 15:22 UTC July 03, 2024 <b>Incident end time:</b> 16:44 UTC July 03, 2024 <b>Preliminary root cause:</b> This issue is a recurrence of the previously reported impact associated with issues INC0110718, INC0110871, and INC0111066. The most recent investigation identified an additional configuration change contributing to resource pressure against the affected database infrastructure, and we have reverted the identified configuration change. In parallel, engineering teams are continuing to monitor and analyze all components of the affected database to ensure there are no additional factors contributing to the intermittent increases in connection requests.

<b>Current status:</b> Service health has remained stable since 16:44 UTC following our latest configuration change. We are continuing to closely monitor the environment and will provide another update in 60 minutes. <b>Customer experience:</b> Users in the affected region(s) intermittently may be unable to sign in or use the Snowflake service via Snowsight. As the issue is intermittent, attempting to reload the page or sign in again may succeed. <b>Incident start time:</b> 15:22 UTC July 03, 2024

<b>Current status:</b> We've completed implementing an emergency configuration change and are monitoring the affected infrastructure to ensure stability. <b>Customer experience:</b> Users in the affected region(s) intermittently may be unable to sign in or use the Snowflake service via Snowsight. As the issue is intermittent, attempting to reload the page or sign in again may succeed. <b>Incident start time:</b> 15:22 UTC July 03, 2024

<b>Current status:</b> We are preparing an emergency configuration change which will cause an additional momentary disruption of five to ten minutes. We'll provide an update after the change is complete. <b>Customer experience:</b> Users in the affected region(s) intermittently may be unable to sign in or use the Snowflake service via Snowsight. As the issue is intermittent, attempting to reload the page or sign in again may succeed. <b>Incident start time:</b> 15:22 UTC July 03, 2024

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight.

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

<b>Current status:</b> We've confirmed that the issue has been remediated following the implementation of the fix and extended monitoring of the affected infrastructure through periods of peak connection requests. If you experience additional issues or have questions, please open a support case via Snowflake Community. <b>Customer experience:</b> Users in the affected region(s) intermittently could not sign in or use the Snowflake service via Snowsight. As the issue was intermittent, attempting to reload the page or sign in again may have succeeded. <b>Incident start time:</b> 13:30 UTC July 01, 2024 <b>Incident end time:</b> 00:15 UTC July 02, 2024 <b>Preliminary root cause:</b> The catalyst for impact has been attributed to a significant increase in connection requests against a primary database supporting Snowsight application infrastructure. Our initial analysis indicated that the increase in requests was due to organic usage increases over time, and during each occurrence of impact (INC0110718, INC0110871, and INC0111066) we implemented a number of optimizations to reduce load and improve performance of the database infrastructure. However, further investigation identified a previously implemented change that resulted in compounded traffic and subsequent connection requests being initiated against the affected database infrastructure over time. During periods of peak traffic, the problem was exacerbated and caused the service to experience intermittent periods of degraded performance while core services were throttled to manage the significant increase in requests. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> We've implemented a fix for this issue and will monitor the environment during peak hours on July 2 and beyond to ensure all services function properly. <b>Customer experience:</b> Users in the affected region(s) intermittently could not sign in or use the Snowflake service via Snowsight. As the issue was intermittent, attempting to reload the page or sign in again may have succeeded. <b>Incident start time:</b> 13:30 UTC July 01, 2024 <b>Incident end time:</b> 00:15 UTC July 02, 2024 <b>Preliminary root cause:</b> An update for Snowsight, intended to improve overall query performance caused an unexpected performance degradation.

<b>Current status:</b> The Engineering team needs to carry out necessary remediation steps that will require momentary service unavailability between 12:15 AM and 12:30 AM UTC. This step is necessary for service recovery to BAU levels. We'll provide another update within 60 minutes. <b>Customer experience:</b> Users in the affected region(s) were intermittently unable to sign in or use the Snowflake service via Snowsight. As the issue was intermittent in nature, attempting to reload the page or sign in again may have succeeded. <b>Incident start time:</b> 13:30 UTC July 01, 2024

<b>Current status:</b> As of 22:10 AM UTC, system performance had improved, and Engineers continued to optimize the request load on the affected system to restore performance to BAU levels. We'll provide another update within 60 minutes. <b>Customer experience:</b> Users in the affected region(s) were intermittently unable to sign in or use the Snowflake service via Snowsight. As the issue was intermittent in nature, attempting to reload the page or sign in again may have succeeded. <b>Incident start time:</b> 13:30 UTC July 01, 2024

<b>Current status:</b> Engineers are actively optimizing request load on the affected system to balance performance more effectively in response to the increase in connections. Error rates have largely subsided as of 21:00 UTC. We'll provide another update within 60 minutes. <b>Customer experience:</b> Users in the affected region(s) may be intermittently unable to sign in or use the Snowflake service via Snowsight. As the issue is intermittent in nature, attempting to reload the page or sign in again may succeed. <b>Incident start time:</b> 13:30 UTC July 01, 2024

<b>Current status:</b> We have observed another occurrence of impact starting at 20:22 UTC. Engineers are actively engaged and investigating the health of the affected systems. We'll provide another update within 60 minutes. <b>Customer experience:</b> Users in the affected region(s) may be intermittently unable to sign in or use the Snowflake service via Snowsight. As the issue is intermittent in nature, attempting to reload the page or sign in again may succeed. <b>Incident start time:</b> 13:30 UTC July 01, 2024

<b>Current status:</b> Following the latest optimizations and mitigations that we implemented, the service has remained stable since 16:35 UTC. We are continuing to investigate background processes and contributing sources of load within the affected database infrastructure while we closely monitor the environment. We'll provide another update within two hours. <b>Customer experience:</b> Users in the affected region(s) may be intermittently unable to sign in or use the Snowflake service via Snowsight. As the issue is intermittent in nature, attempting to reload the page or sign in again may succeed. <b>Incident start time:</b> 13:33 UTC July 01, 2024

<b>Current status:</b> We are continuing to observe periods of intermittent service instability and are actively investigating the latest occurrence between 16:20 and 16:35 UTC. In parallel, we have identified an additional background process that may be contributing to system load during periods of increased connection requests, and we are continuing to tune and optimize throttling and self-healing mechanisms to balance performance during these periods more effectively. We'll provide another update within 90 minutes. <b>Customer experience:</b> Users in the affected region(s) may be intermittently unable to sign in or use the Snowflake service via Snowsight. As the issue is intermittent in nature, attempting to reload the page or sign in again may succeed. <b>Incident start time:</b> 13:33 UTC July 01, 2024

<b>Current status:</b> Our latest investigation efforts identified that a self-healing mechanism was aggressively restarting affected systems after database connection increases occurred, significantly contributing to the observed periods of intermittent impact. We've implemented an additional optimization to the throttling and self-healing mechanisms used by the affected database infrastructure, and we are currently monitoring the environment to ensure stability. We'll provide another update within 60 minutes. <b>Customer experience:</b> Users in the affected region(s) may be intermittently unable to sign in or use the Snowflake service via Snowsight. As the issue is intermittent in nature, attempting to reload the page or sign in again may succeed. <b>Incident start time:</b> 13:33 UTC July 01, 2024

<b>Current status:</b> On July 1, 2024, starting at 13:33 UTC, we began observing a reoccurrence of the intermittent periods of impact associated with INC0110871. Based on the identified increase in connections affecting database performance, we are attempting to implement additional optimizations to reduce impact while we continue our investigation to further isolate and remediate the source of the issue. We'll provide another update within 60 minutes. <b>Customer experience:</b> Users in the affected region(s) may be intermittently unable to sign in or use the Snowflake service via Snowsight. As the issue is intermittent in nature, attempting to reload the page or sign in again may succeed. <b>Incident start time:</b> 13:33 UTC July 01, 2024

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Users in the affected region(s) may be intermittently unable to sign in to the Snowflake service via Snowsight. <b>Incident start time:</b> 13:35 UTC July 01, 2024

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

<b>Current status:</b> 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. <b>Customer experience:</b> Users in the affected region(s) may have been intermittently unable to sign in or use the Snowflake service via Snowsight. As the issue was intermittent in nature, attempting to reload the page or sign in again may have succeeded. <b>Incident start time:</b> 13:48 UTC June 27, 2024 <b>Incident end time:</b> 14:30 UTC June 28, 2024 <b>Preliminary root cause:</b> A significant increase in connection requests against a primary database supporting Snowsight application infrastructure caused the service to experience intermittent periods of degraded performance. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> Since implementing the latest database infrastructure optimizations, service performance has remained stable. We are continuing to closely monitor the environment, and we'll provide another update within 4 hours. <b>Customer experience:</b> Users in the affected region(s) may have been intermittently unable to sign in or use the Snowflake service via Snowsight. As the issue was intermittent in nature, attempting to reload the page or sign in again may have succeeded. <b>Incident start time:</b> 13:48 UTC June 27, 2024 <b>Incident end time:</b> 18:50 UTC June 27, 2024 <b>Preliminary root cause:</b> A significant increase in connection requests against a primary database supporting Snowsight application infrastructure caused the service to experience intermittent periods of degraded performance.

<b>Current status:</b> While the initial mitigations we implemented have increased overall stability on the affected database infrastructure, we have continued to observe some brief periods of intermittent service impact during peak traffic. We are closely monitoring the environment while continuing to implement additional optimizations to more effectively balance periods of increased connection requests. We'll provide another update within 2 hours. <b>Customer experience:</b> Users in the affected region(s) may have been intermittently unable to sign in or use the Snowflake service via Snowsight. As the issue was intermittent in nature, attempting to reload the page or sign in again may have succeeded. <b>Incident start time:</b> 13:48 UTC June 27, 2024 <b>Incident end time:</b> 18:50 UTC June 27, 2024 <b>Preliminary root cause:</b> A significant increase in connection requests against a primary database supporting Snowsight application infrastructure caused the service to experience intermittent periods of degraded performance.

<b>Current status:</b> We've implemented an additional fix for this issue, and we'll continue to monitor the environment over an extended period of time until we're confident all services are functioning properly. We'll provide another update by June 28, 2024, or earlier should there be a significant change in status. <b>Customer experience:</b> Users in the affected region(s) may have been intermittently unable to sign in or use the Snowflake service via Snowsight. As the issue was intermittent in nature, attempting to reload the page or sign in again may have succeeded. <b>Incident start time:</b> 13:48 UTC June 27, 2024 <b>Incident end time:</b> 18:50 UTC June 27, 2024 <b>Preliminary root cause:</b> A significant increase in connection requests against a primary database supporting Snowsight application infrastructure caused the service to experience intermittent periods of degraded performance.

<b>Current status:</b> Following our initial mitigation, we've identified that intermittent impact continues to occur during peak periods of increased connection counts. We are continuing to work on immediate mitigation actions to help alleviate the impact on the affected infrastructure. We'll provide another update within 2 hours. <b>Customer experience:</b> Users in the affected region(s) may be intermittently unable to sign in or use the Snowflake service via Snowsight. As the issue was intermittent in nature, attempting to reload the page or sign in again may succeed. <b>Incident start time:</b> 13:48 UTC June 27, 2024

<b>Current status:</b> 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. <b>Customer experience:</b> Users in the affected region(s) may have been intermittently unable to sign in or use the Snowflake service via Snowsight. As the issue was intermittent in nature, attempting to reload the page or sign in again may have succeeded. <b>Incident start time:</b> 13:48 UTC June 27, 2024 <b>Incident end time:</b> 16:30 UTC June 27, 2024 <b>Preliminary root cause:</b> A significant increase in connection requests against a primary database supporting Snowsight application infrastructure caused the service to experience intermittent periods of degraded performance during peak traffic.

<b>Current status:</b> 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. <b>Customer experience:</b> Users in the affected region(s) may be intermittently unable to sign in to the Snowflake service via Snowsight. As the issue is intermittent in nature, attempting to reload the page or sign in again may succeed. <b>Incident start time:</b> 13:48 UTC June 27, 2024

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Users in the affected region(s) may be intermittently unable to sign in to the Snowflake service via Snowsight. As the issue is intermittent in nature, attempting to reload the page or sign in again may succeed. <b>Incident start time:</b> 13:48 UTC June 27, 2024

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

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to execute queries or may have experienced delays resuming virtual warehouses. Additionally, customers hosted in the AWS - US East (N. Virginia) region saw errors attempting to sign in to Snowsight. <b>Incident start time:</b> 18:25 UTC June 25, 2024 <b>Incident end time:</b> 20:10 UTC June 25, 2024 <b>Preliminary root cause:</b> A recently updated system configuration caused impact to provisioning systems, resulting in an availability issue due to new infrastructure and virtual warehouses not being able to deploy as expected. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to execute queries or may have experienced delays resuming virtual warehouses. Additionally, customers hosted in the AWS - US East (N. Virginia) region saw errors attempting to sign in to Snowsight. <b>Incident start time:</b> 18:25 UTC June 25, 2024 <b>Incident end time:</b> 20:10 UTC June 25, 2024 <b>Preliminary root cause:</b> A recently updated system configuration caused impact to provisioning systems, resulting in an availability issue due to new infrastructure and virtual warehouses not being able to deploy as expected.

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 been unable to execute queries or may experience delays resuming virtual warehouses. Additionally, customers hosted in the AWS - US East (N. Virginia) region saw errors attempting to sign in to Snowsight. Incident start time: 18:25 UTC June 25, 2024 Incident end time: 20:10 UTC June 25, 2024 Preliminary root cause: A recently updated system configuration caused impact to provisioning systems, resulting in an availability issue due to new infrastructure and virtual warehouses not being able to deploy as expected.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to execute queries or access Snowsight. <b>Incident start time:</b> 18:25 UTC June 25, 2024

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to execute queries or access Snowsight. <b>Incident start time:</b> 18:25 UTC June 25, 2024

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

<b>Current status:</b> We've coordinated with our third-party service provider to implement the fix for this issue, and 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. <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to execute queries. <b>Incident start time:</b> 03:25 UTC June 22, 2024 <b>Incident end time:</b> 07:33 UTC June 22, 2024 <b>Preliminary root cause:</b> A technical issue with a third-party service provider caused an impact on Snowflake's operations. We will be contacting the third-party service provider to conduct a RCA. A root cause analysis (RCA) document will be published within ten business days.

<b>Current status:</b> We've coordinated with our third-party service provider to implement the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to execute queries. <b>Incident start time:</b> 03:25 UTC June 22, 2024 <b>Incident end time:</b> 07:33 UTC June 22, 2024 <b>Preliminary root cause:</b> A technical issue with a third-party service provider caused an impact on Snowflake's operations. We will be contacting the third-party service provider to conduct a RCA

<b>Current status:</b> 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 120 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to execute queries.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to execute queries.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to execute queries.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to execute queries.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to execute queries.

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

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified region would have experienced delays while attempting to resume virtual warehouses or execute queries. <b>Incident start time:</b> 23:09 UTC June 27, 2024 <b>Preliminary root cause:</b> A configuration update intended to improve efficiency in managing virtual warehouse resources resulted in performance degradation and warehouse resume delays for the specified region. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified region may experience delays while attempting to resume virtual warehouses or execute queries. <b>Incident start time:</b> 23:09 UTC June 27, 2024

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

<b>Current status:</b> We've coordinated with our third-party service provider to implement the fix for this issue, and 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. <b>Customer experience:</b> Customers hosted in the specified regions experienced delays in resuming warehouse services. <b>Incident start time:</b> 00:08 UTC June 18, 2024 <b>Incident end time:</b> 00:33 UTC June 18, 2024 <b>Preliminary root cause:</b> A third-party service provider encountered an internal issue, resulting in delays in cloud service provisioning. A root cause analysis (RCA) document will be published within ten business days.

<b>Current status:</b> We're investigating an issue with Snowflake Data Warehouse where customers may experience delays in resuming virtual warehouse services. Multiple Snowflake support teams are engaged to address the issue. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may experience delays in resuming warehouse services. <b>Incident start time:</b> 00:08 UTC June 18, 2024

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

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified region may have experienced delays while attempting to resume virtual warehouses or execute queries. <b>Incident start time:</b> 22:58 UTC June 20, 2024 <b>Incident end time:</b> 01:17 UTC June 21, 2024 <b>Preliminary root cause:</b> Preliminary findings indicate that several servers encountered unusual loads, resulting in overall performance problems with the region. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified region may have experienced delays while attempting to resume virtual warehouses or execute queries. <b>Incident start time:</b> 22:58 UTC June 20, 2024 <b>Incident end time:</b> 01:17 UTC June 21, 2024 <b>Preliminary root cause:</b> Preliminary findings indicate that issues with several Cloud Services layer servers contributed to the overall performance problems.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified region may experience delays while attempting to resume virtual warehouses or execute queries.

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

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions experienced difficulty accessing or using Snowflake services and features via the Snowflake classic web interface and Snowsight. API connectivity to Snowflake remained unaffected. <b>Incident start time:</b> 00:51 UTC June 18, 2024 <b>Incident end time:</b> 03:17 UTC June 18, 2024 <b>Preliminary root cause:</b> Initial investigation suggests that multiple Snowsight application services became unavailable. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> We're continuing to investigate the issue with Snowflake Data Cloud. We'll provide another update within 2 hours. <b>Customer experience:</b> Customers hosted in the specified regions may experience difficulty accessing or using Snowflake services and features via the Snowflake classic web interface and Snowsight. API connectivity to Snowflake remains unaffected. <b>Incident start time:</b> 00:51 UTC June 18, 2024

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. <b>Incident start time:</b> 00:51 UTC June 18, 2024

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

<b>Current status:</b> 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 <b>Customer experience:</b> Users with trial accounts may experience issues when using Streamlit in Snowflake and Notebook functionalities. Production accounts are not affected. <b>Incident start time:</b> 05:27 UTC May 29, 2024 <b>Incident end time:</b> 07:20 UTC May 30, 2024 <b>Preliminary root cause:</b> Recent adjustments to the SiS/NB system, aimed at enhancing functionality, inadvertently impacted the usability of Trial Accounts. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> We've identified the source of the issue and successfully tested a fix in lower environments. We are currently implementing a fix to restore service. We'll provide another update within 5 hours. <b>Customer experience:</b> Users with trial accounts may experience issues when using Streamlit in Snowflake and Notebook functionalities. Production accounts are not affected. <b>Incident start time:</b> 05:27 UTC May 29, 2024

<b>Current status:</b> 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. <b>Customer experience:</b> Users with trial accounts may experience issues when using Streamlit in Snowflake and Notebook functionalities. Production accounts are not affected. <b>Incident start time:</b> 05:27 UTC May 29, 2024

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

<b>Current status:</b> 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. <b>Customer experience:</b> A subset of customers might have encountered challenges during query execution, faced difficulties accessing their query history, and experienced performance issues while using Snowsight. <b>Incident start time:</b> 16:50 UTC May 28, 2024 <b>Incident end time:</b> 03:17 UTC May 29, 2024 <b>Preliminary root cause:</b> We have identified an issue localized to a subset of our Metadata Database infrastructure. As part of the remediation activity, some Snowsight users might have encountered performance issues. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> We've implemented the fix for this issue, and we'll continue to monitor the environment until all services are fully recovered. While the fix takes effect on the affected instances, some customers may still encounter occasional issues. <b>Customer experience:</b> A subset of customers might have encountered challenges during query execution, faced difficulties accessing their query history, and experienced performance issues while using Snowsight. <b>Incident start time:</b> 16:50 UTC May 28, 2024 <b>Incident end time:</b> 03:17 UTC May 29, 2024 <b>Preliminary root cause:</b> We have identified an issue localized to a subset of our Metadata Database infrastructure. As part of the remediation activity, some Snowsight users would have encountered performance issues.

<b>Current status:</b> 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. <b>Customer experience:</b> A subset of customers may have faced challenges during query execution and difficulties accessing their query history. <b>Incident start time:</b> 16:50 UTC May 28, 2024 <b>Incident end time:</b> 03:17 UTC May 29, 2024 <b>Preliminary root cause:</b> We have identified an issue localized to a subset of our Metadata Database infrastructure.

<b>Current status:</b> We continue to investigate an issue within the Metadata Database layer and have isolated it to a subset of our Metadata Database infrastructure. Additionally, we've identified several data sets experiencing operational constraints, resulting in queries referencing them to fail. We're currently working on resolving these constraints to alleviate impacts. We will provide another update within 2 hours. <b>Customer experience:</b> A specific subset of customers whose queries reference a particular table we've identified as affected may encounter challenges during query execution, as well as difficulties accessing their query history. <b>Incident start time:</b> 16:50 UTC May 28, 2024

<b>Current status:</b> We continue to investigate an issue within the Metadata Database layer and have isolated it to a subset of our Metadata Database infrastructure. Additionally, we've identified several data sets experiencing operational constraints, resulting in queries referencing them to fail. We're currently working on resolving these constraints to alleviate impacts. We will provide another update within 2 hours. <b>Customer experience:</b> A specific subset of customers whose queries reference a particular table we've identified as affected may encounter challenges during query execution, as well as difficulties accessing their query history. <b>Incident start time:</b> 16:50 UTC May 28, 2024

<b>Current status:</b> We're continuing to investigate an issue within the Metadata Database layer and have isolated the issue to a subset of the Metadata Database infrastructure. We will provide another update within 120 minutes. <b>Customer experience:</b> A subset of customers may experience issues with viewing their query history. <b>Incident start time:</b> 16:50 UTC May 28, 2024

<b>Current status:</b> We're continuing to investigate an issue within the Metadata Database layer and have isolated the issue to a subset of the Metadata Database infrastructure. We will provide another update within 60 minutes. <b>Customer experience:</b> A subset of customers may experience issues with viewing their query history. <b>Incident start time:</b> 16:50 UTC May 28, 2024

<b>Current status:</b> We're continuing to investigate an issue within the Metadata Database layer and will provide another update within 60 minutes. <b>Customer experience:</b> A subset of customers may experience issues with viewing their query history. <b>Incident start time:</b> 16:50 UTC May 28, 2024

<b>Current status:</b> We're continuing to investigate the issue with Snowflake Data Cloud. We'll provide another update within 60 minutes. <b>Customer experience:</b> A subset of customers may experience issues with viewing their query history. <b>Incident start time:</b> 16:50 UTC May 28, 2024

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> A subset of customers may experience issues with viewing their query history. <b>Incident start time:</b> 16:50 UTC May 28, 2024

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

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to execute queries. <b>Workaround:</b> There are currently no available workarounds for this issue. <b>Incident start time:</b> 13:55 UTC May 28, 2024 <b>Incident end time:</b> 15:25 UTC May 28, 2024 <b>Preliminary root cause:</b> A configuration update intended to enhance data load efficiency caused users to be unable to run queries in this region. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to execute queries. <b>Workaround:</b> There are currently no available workarounds for this issue. <b>Incident start time:</b> 13:55 UTC May 28, 2024 <b>Incident end time:</b> 15:25 UTC May 28, 2024 <b>Preliminary root cause:</b> A configuration update intended to enhance data load efficiency caused users to be unable to run queries in this region.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to execute queries. <b>Workaround:</b> There are currently no available workarounds for this issue. <b>Incident start time:</b> 13:55 UTC May 28, 2024

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to execute queries. <b>Workaround:</b> There are currently no available workarounds for this issue. <b>Incident start time:</b> 13:55 UTC May 28, 2024

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

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have experienced delays while attempting to execute queries. Affected customers might have encountered query failures. <b>Incident start time:</b> 16:16 UTC May 24, 2024 <b>Incident end time:</b> 18:20 UTC May 24, 2024 <b>Preliminary root cause:</b> The preliminary investigation points to an issue within a single node of the infrastructure responsible for the Warehouse Scheduling Service. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have experienced delays while attempting to execute queries. Affected customers might have encountered query failures. <b>Incident start time:</b> 16:16 UTC May 24, 2024 <b>Incident end time:</b> 18:20 UTC May 24, 2024 <b>Preliminary root cause:</b> The preliminary investigation points to an issue within a single node of the infrastructure responsible for the Warehouse Scheduling Service.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may experience delays while attempting to execute queries. Affected customers may encounter query failures. <b>Incident start time:</b> 17:12 UTC May 24, 2024

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

<b>Current status:</b> Our third-party service provider continues to address their internal Virtual Private Cloud (VPC) outage, achieving partial service restoration. Since 12:05 UTC, Snowflake services have remained stable due to the server pool secured by the Snowflake Engineering team. We will continue to monitor the environment until stability is achieved. <b>Customer experience:</b> Customers hosted in the specified regions may have experienced delays while attempting to access or use Snowflake services and features. <b>Incident start time:</b> 21:44 UTC May 16, 2024 <b>Incident end time:</b> 00:05 UTC May 17, 2024 <b>Preliminary root cause:</b> The cloud service provider (CSP) encountered an internal network connectivity outage which impacted their Virtual Private Cloud (VPC) service. A root cause analysis (RCA) document will be published within ten business days.

<b>Current status:</b> Our third-party service provider is actively resolving their internal outage, and we'll continue to monitor the environment until stability is achieved. In the meantime, Snowflake Engineering has secured a set of server pools that customers can now utilize. As of 12:05 AM UTC, telemetry shows performance improvement across Snowflake services. <b>Customer experience:</b> Customers hosted in the specified regions may have experienced delays while attempting to access or use Snowflake services and features. <b>Incident start time:</b> 23:18 UTC May 16, 2024 <b>Incident end time:</b> 00:05 UTC May 17, 2024 <b>Preliminary root cause:</b> The Cloud service provider is experiencing an internal outage with their Virtual Private Cloud (VPC) service.

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may experience delays while attempting to access or use Snowflake services and features. <b>Incident start time:</b> 23:18 UTC May 16, 2024

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

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have experienced delays while attempting to access or use Snowflake services and features using Snowsight. <b>Incident start time:</b> 01:16 UTC May 07, 2024 <b>Incident end time:</b> 04:31 UTC May 07, 2024 <b>Preliminary root cause:</b> An update intended for improving query execution in worksheets caused a subset of PrivateLink customers to experience delays while attempting to access or use Snowflake services and features using Snowsight.

<b>Current status:</b> We're continuing to develop and implement a fix to restore service. We'll provide another update within 90 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may experience delays while attempting to access or use Snowflake services and features using Snowsight. <b>Workaround:</b> While we are focused on the remediation, please use alternate UIs to access Snowflake services.

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

<b>Current status:</b> We've coordinated with our third-party service provider to implement the fix for this issue, and 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. <b>Customer experience:</b> A subset of customers hosted in the specified region would have experienced intermittent delays while attempting to resume virtual warehouses or execute queries. <b>Incident start time:</b> 18:16 UTC April 29, 2024 <b>Incident end time:</b> 22:40 UTC April 29, 2024 <b>Preliminary root cause:</b> The issue originated from a recent disruption in our cloud service provider's storage service, which affected queries. After resolving this disruption, service utilization in the region increased due to the resubmission of the affected queries, which led to warehouse resume delays.

<b>Current status:</b> Since 22:40 UTC, there has been a significant improvement in warehouse resumes. Our engineering team is continuously monitoring the environment until we're confident all services are functioning properly. <b>Customer experience:</b> A subset of customers hosted in the specified region would have experienced intermittent delays while attempting to resume virtual warehouses or execute queries. <b>Incident start time:</b> 18:16 UTC April 29, 2024 <b>Incident end time:</b> 22:40 UTC April 29, 2024 <b>Preliminary root cause:</b> The issue originated from a recent disruption in our cloud service provider's storage service, which affected queries. After resolving this disruption, service utilization in the region increased due to the resubmission of the affected queries, which led to warehouse resume delays.

<b>Current status:</b> Telemetry indicates intermittent connectivity issues have significantly subsided as of 22:40 UTC, thus alleviating the issue. We continue to monitor virtual warehouse resume delays and will provide updates on the situation until services return to normal operational levels. <b>Customer experience:</b> A subset of customers hosted in the specified region would have experienced intermittent delays while attempting to resume virtual warehouses or execute queries. <b>Incident start time:</b> 18:16 UTC April 29, 2024 <b>Incident end time:</b> 22:45 UTC April 29, 2024 <b>Preliminary root cause:</b> The issue arose following a recent disruption in our cloud service provider's storage service, which impacted some queries. Subsequent to addressing this disruption, service utilization in the region increased due to the resubmission of the previously affected queries. This led to intermittent delays in warehouse operations resuming fully.

<b>Current status:</b> We're continuing to investigate to determine the source of an increase in intermittent connectivity issues within the region. We'll provide another update within 2 hours. <b>Customer experience:</b> Customers hosted in the specified region may experience intermittent delays while attempting to resume virtual warehouses or execute queries. <b>Incident start time:</b> 18:16 UTC April 29, 2024

<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified region may experience delays while attempting to resume virtual warehouses or execute queries. <b>Incident start time:</b> 18:16 UTC April 29, 2024

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

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. <b>Incident start time:</b> 15:07 UTC May 08, 2024 <b>Incident end time:</b> 17:25 UTC May 08, 2024 <b>Preliminary root cause:</b> A recent Snowsight release caused DNS resolution failures, leading to Snowsight connectivity issues. Please note that the impact start may vary across the affected Regions since the cached session would not have been affected until refreshed. A root cause analysis (RCA) document will be published within seven business days.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. <b>Incident start time:</b> 15:07 UTC May 08, 2024 <b>Incident end time:</b> 17:25 UTC May 08, 2024 <b>Preliminary root cause:</b> A recent Snowsight release caused DNS resolution failures, leading to Snowsight connectivity issues. Please note that the impact start may vary across the affected Regions since the cached session would not have been affected until refreshed.

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. <b>Incident start time:</b> 15:07 UTC May 08, 2024

<b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. <b>Incident start time:</b> 15:07 UTC May 08, 2024