Snowflake Outage History

Started Mar 07, 2026, 08:05 PM UTC· resolved Mar 07, 2026, 10:20 PM UTC

1. investigating Mar 07, 2026, 08:05 PM UTC

   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 multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data.

2. identified Mar 07, 2026, 08:37 PM UTC

   Current status: We've identified an issue with a third-party cloud platform, and we're coordinating with the provider to restore service. We're beginning to see some relief as mitigation actions take effect. We're continuing to monitor, and we'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 19:30 UTC March 07, 2026

3. monitoring Mar 07, 2026, 09:23 PM UTC

   Current status: We've coordinated with our third-party cloud platform to remediate 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 multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data. Incident start time: 19:30 UTC March 07, 2026 Incident end time: 21:10 UTC March 07, 2026 Preliminary root cause: A third-party cloud platform experienced an issue with part of their storage service, which temporarily prevented some Snowflake services and features from working for a subset of customers in this region.

4. resolved Mar 07, 2026, 10:20 PM UTC

   Current status: We've coordinated with our third-party cloud platform to confirm that the fix for this issue was successfully implemented, and we've monitored the environment to confirm that service has been fully restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data. Incident start time: 19:30 UTC March 07, 2026 Incident end time: 21:10 UTC March 07, 2026 Preliminary root cause: A third-party cloud platform experienced an issue with part of their storage service, which temporarily prevented some Snowflake services and features from working for a subset of customers in this region. A root cause analysis (RCA) document will be published within ten business days.

5. postmortem Mar 20, 2026, 09:32 PM UTC

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

Read the full incident report →

Started Mar 01, 2026, 01:33 PM UTC· resolved May 15, 2026, 03:10 PM UTC

1. investigating Mar 01, 2026, 01:33 PM UTC

   Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data.

2. identified Mar 01, 2026, 02:07 PM UTC

   Current status: We've identified an issue with a third-party cloud platform, and we're coordinating with the provider 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 be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures.

3. identified Mar 01, 2026, 02:55 PM UTC

   Current status: We're continuing to coordinate with our third-party cloud platform to develop and implement a fix to restore service. We'll provide another update within 4 hours. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: The third-party platform has advised that it may take multiple hours to resolve the issue. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 12:25 UTC March 01, 2026

4. identified Mar 01, 2026, 06:18 PM UTC

   Current status: We're continuing to coordinate with our third-party cloud platform to develop and implement a fix to restore service. The provider has confirmed that the issue is due to a power disruption, and they expect full recovery to take multiple hours to complete. We'll provide another update within 6 hours. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: The third-party platform has advised that it may take multiple hours to resolve the issue. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 12:25 UTC March 01, 2026

5. identified Mar 02, 2026, 12:23 AM UTC

   Current status: We continue to coordinate closely with our cloud provider as they work to resolve a major service disruption caused by a power outage at a primary data center. While we are seeing initial signs of recovery across several services, the provider expects full restoration to take multiple hours as they safely stabilize the environment. We'll provide another update within 6 hours. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: The third-party platform has advised that it may take multiple hours to resolve the issue. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 12:25 UTC March 01, 2026

6. identified Mar 02, 2026, 06:24 AM UTC

   Current status: We continue to coordinate with our cloud provider following a power outage at a primary data center. While we have observed consistent signs of recovery in several key services, the provider is currently investigating a localized connectivity issues and elevated error rates within the region. Full restoration is expected to take several hours as they work to safely stabilize the environment. We will provide our next update within 6 hours. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: The third-party platform has advised that it may take multiple hours to resolve the issue. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 12:25 UTC March 01, 2026

7. identified Mar 02, 2026, 12:24 PM UTC

   Current status: We continue to coordinate with our cloud provider following a power outage at a primary data center. Although we had observed early indicators of recovery, the provider has confirmed additional, ongoing impact that continues to cause elevated connectivity issues and error rates within the region. They continue to actively work on full restoration and environment stability but this is expected to take several hours. We will provide our next update within 6 hours. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: The third-party platform has advised that it may take multiple hours to resolve the issue. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 12:25 UTC March 01, 2026

8. identified Mar 02, 2026, 06:17 PM UTC

   Current status: We're continuing to coordinate with our cloud service provider as they troubleshoot the impacting power outage at a primary data center. Elevated connectivity issues and error rates within the region will continue until the power issue has been resolved. While they're working to fully restore power and stabilize the environment, they now expect that this may take a day or more. We will provide our next update within 24 hours. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: The third-party platform has advised that it may take a day or more to resolve the issue. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 12:25 UTC March 01, 2026

9. identified Mar 03, 2026, 06:18 PM UTC

   Current status: We're closely monitoring as coordination with our cloud service provider continues in an effort to restore service following the impacting power outage at a primary data center. They are prioritizing recovery for foundational services and pursuing multiple mitigation paths that do not depend on the underlying facilities being fully brought back online to provide some relief. However, full restoration will require that the underlying infrastructure be fully repaired, and this effort is ongoing. We're continuing to monitor for improvement, and we will provide our next update within 12 hours. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: An updated ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Affected customers should look for additional updates in their cloud service provider's personal health dashboard. Incident start time: 12:25 UTC March 01, 2026

10. identified Mar 04, 2026, 06:02 AM UTC

    Current status: We continue to actively monitor the situation as we work with our cloud service provider to restore service following a power outage at a primary data center. Recovery efforts remain focused on foundational services, and multiple paths to restoration continue to be pursued. Work to restore the underlying infrastructure needed for full restoration is still in progress. Additionally, we've been informed that our cloud service provider will supplement their public service health updates with a targeted communications approach, delivered directly to customers through their personal health dashboards, for a more localized, relevant view of service health. We will provide our next update within 24 hours. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: An updated ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Affected customers should look for additional updates in their cloud service provider's personal health dashboard. Incident start time: 12:25 UTC March 01, 2026

11. identified Mar 05, 2026, 04:39 AM UTC

    Current status: We continue to actively monitor the situation, and our cloud service provider affirms that meaningful progress is being made toward recovery, with several distinct services showing sustained improvement. While focused efforts continue toward full-service restoration for the region, the cloud service providers' initial advice to migrate your workloads and traffic to alternate Region(s) remains in place. We are in continuous contact with the provider and will post our next update once they confirm significant progress in restoring the site's physical environment, or when other material updates become available. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: An updated ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Affected customers should look for additional updates in their cloud service provider's personal health dashboard. Incident start time: 12:25 UTC March 01, 2026

12. resolved May 15, 2026, 03:10 PM UTC

    To ensure the best possible service for our customers amid the persistent issues in the AWS Middle East (UAE) region and following the cloud service provider’s advice to transition workloads to other regions, we have decided to remove this region from our available listings until further notice.

Read the full incident report →

Started Feb 23, 2026, 09:09 PM UTC· resolved Feb 23, 2026, 10:07 PM UTC

1. investigating Feb 23, 2026, 09:09 PM UTC

   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 failures when accessing or using Snowflake services and features. This may include slower query execution, intermittent availability, or limited feature functionality. Incident start time: 19:28 UTC February 23, 2026

2. monitoring Feb 23, 2026, 09:47 PM UTC

   Current status: We identified a networking issue that caused a component to be unable to process traffic and resolve DNS requests as expected, resulting in impact. We 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 experience intermittent delays or failures when accessing or using Snowflake services and features. This may include slower query execution, intermittent availability, or limited feature functionality. Incident start time: 19:26 UTC February 23, 2026 Incident end time: 21:11 UTC February 23, 2026 Preliminary root cause: A networking issue caused a component to be unable to process traffic and resolve DNS requests as expected.

3. resolved Feb 23, 2026, 10:07 PM UTC

   Current status: Our observations of service telemetry continue to indicate that our service has recovered following our mitigation. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified regions may have experienced intermittent delays or failures when accessing or using Snowflake services and features. This may have included slower query execution, intermittent availability, or limited feature functionality. Incident start time: 19:26 UTC February 23, 2026 Incident end time: 21:11 UTC February 23, 2026 Preliminary root cause: A networking issue caused a component to be unable to process traffic and resolve DNS requests as expected. A root cause analysis (RCA) document will be published within five business days.

4. postmortem Mar 02, 2026, 10:33 PM UTC

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

Read the full incident report →

Started Jan 27, 2026, 06:13 PM UTC· resolved Jan 27, 2026, 07:30 PM UTC

1. investigating Jan 27, 2026, 06:13 PM UTC

   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 multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. Additionally, they may be unable to continuously stream data into Snowflake using Snowpipe Streaming, and may be unable to execute queries, retrieve results, or manage data objects such as tables and views.

2. monitoring Jan 27, 2026, 07:02 PM UTC

   Current status: We've identified a recent change to our service infrastructure that resulted in impact. We've reverted this change to remediate the issue, and we've observed that the issue has been resolved. 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 multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data. Additionally, they may have been unable to continuously stream data into Snowflake using Snowpipe Streaming, or ingest data using Snowpipe, and may have been unable to execute queries, retrieve results, or manage data objects such as tables and views. Incident start time: 17:51 UTC January 27, 2026 Incident end time: 18:25 UTC January 27, 2026 Preliminary root cause: A recent change to our service infrastructure experienced an incompatibility issue on a subset of instances in the metadata database layer, causing requests to fail.

3. resolved Jan 27, 2026, 07:30 PM UTC

   Current status: We've implemented the fix for this issue and monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data. Additionally, they may have been unable to continuously stream data into Snowflake using Snowpipe Streaming, or ingest data using Snowpipe, and may have been unable to execute queries, retrieve results, or manage data objects such as tables and views. Incident start time: 17:51 UTC January 27, 2026 Incident end time: 18:25 UTC January 27, 2026 Preliminary root cause: A recent change to our service infrastructure experienced an incompatibility issue on a subset of instances in the metadata database layer, causing requests to fail. A root cause analysis (RCA) document will be published within five business days.

4. postmortem Feb 04, 2026, 01:34 AM UTC

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

Read the full incident report →

Started Jan 22, 2026, 07:18 PM UTC· resolved Jan 22, 2026, 11:24 PM UTC

1. investigating Jan 22, 2026, 07:18 PM UTC

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

2. investigating Jan 22, 2026, 07:48 PM UTC

   Current status: Our investigation has led us to focus on a potential issue with the Snowsight application-hosting layer. We're restarting the systems related to the Snowsight application-hosting layer, and our initial observation of telemetry indicates that this is providing relief. We're continuing to monitor as this trend continues to ensure the service returns to normal health. 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 or may experience delays.

3. monitoring Jan 22, 2026, 08:48 PM UTC

   Current status: Our observations of service telemetry indicate that our service has recovered following the restart of the systems related to the Snowsight application-hosting layer. 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 or may have experienced delays. Incident start time: 19:02 UTC January 22, 2026 Incident end time: 19:30 UTC January 22, 2026 Preliminary root cause: While we're continuing to investigate to determine the underlying root cause of this issue, we suspect that a recent change made to our internal monitoring systems may have resulted in the problem with the Snowsight application-hosting layer.

4. resolved Jan 22, 2026, 11:24 PM UTC

   Current status: Our observations of service telemetry continue to indicate that our service has recovered following the restart of the systems related to the Snowsight application-hosting layer. 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 or may have experienced delays. A subset of customers may have encountered errors while executing queries and other related operations. Incident start time: 19:02 UTC January 22, 2026 Incident end time: 19:30 UTC January 22, 2026 Preliminary root cause: While we're continuing to investigate to determine the underlying root cause of this issue, we suspect that a recent change made to our internal monitoring systems may have resulted in the problem with the Snowsight application-hosting layer. A root cause analysis (RCA) document will be published within five business days.

5. postmortem Jan 28, 2026, 11:58 PM UTC

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

Read the full incident report →

Started Jan 21, 2026, 07:23 PM UTC· resolved Jan 21, 2026, 09:57 PM UTC

1. investigating Jan 21, 2026, 07:23 PM UTC

   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 multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data.

2. investigating Jan 21, 2026, 07:31 PM UTC

   Current status: We're continuing to investigate the issue with Snowflake Data Cloud. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data.

3. investigating Jan 21, 2026, 07:33 PM UTC

   Current status: We're continuing to investigate the issue with Snowflake Data Cloud. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data.

4. investigating Jan 21, 2026, 08:14 PM UTC

   Current status: We have refined our understanding of how this issue manifests, and determined that it is isolated to Snowsight. Our investigation is currently focused on potential issues with the Snowsight application-hosting layer and the Snowsight-specific database layer. We're in the process of restarting systems related to the application layer and reverting any recent application releases that were in progress to mitigate the issue as quickly as possible. We will 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 and may experience delays. Incident start time: 19:00 UTC January 21, 2026

5. monitoring Jan 21, 2026, 08:57 PM UTC

   Current status: We've completed a restart on systems related to the application layer. Our telemetry indicates that this issue is no longer occurring, and users should be able to successfully access the service via the Snowsight User Interface (UI). 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 via Snowsight and may have experienced delays. Incident start time: 19:00 UTC January 21, 2026 Incident end time: 20:08 UTC January 21, 2026 Preliminary root cause: Our preliminary investigation identified that the Snowsight application-hosting layer and the Snowsight-specific database layer experienced an issue that led to an unexpected surge in requests, leading to high resource utilization and preventing the service from processing the associated traffic, resulting in suspended login attempts.

6. resolved Jan 21, 2026, 09:57 PM UTC

   Current status: We've implemented the fix for this issue and monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified regions may have been unable to access or use Snowflake services and features via Snowsight and may have experienced delays. Incident start time: 19:00 UTC January 21, 2026 Incident end time: 20:08 UTC January 21, 2026 Preliminary root cause: Our preliminary investigation identified that the Snowsight application-hosting layer and the Snowsight-specific database layer experienced an issue that led to an unexpected surge in requests, leading to high resource utilization and preventing the service from processing the associated traffic, resulting in suspended login attempts. A root cause analysis (RCA) document will be published within five business days.

7. postmortem Jan 28, 2026, 11:57 PM UTC

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

Read the full incident report →

Started Jan 08, 2026, 06:49 PM UTC· resolved Jan 08, 2026, 08:22 PM UTC

1. investigating Jan 08, 2026, 06:49 PM UTC

   Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. This is specifically impacting users with existing sessions in Snowsight and not new sessions.

2. monitoring Jan 08, 2026, 07:22 PM UTC

   Current status: Our investigation has identified that a change within the recent Snowsight release caused this issue and resulted in errors for users with existing sessions. We've reverted the offending change and we're continuing to monitor to ensure our service remains healthy. Users with existing sessions that are still impacted should refresh their sessions to experience relief. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. This is specifically impacting users with existing sessions in Snowsight and not new sessions. Incident start time: 18:02 UTC January 08, 2026 Incident end time: 19:00 UTC January 08, 2026 Preliminary root cause: A change contained within the recent Snowsight release related to a network policy check caused issues with session deserialization, which resulted in errors for users with active sessions.

3. resolved Jan 08, 2026, 08:22 PM UTC

   Current status: We've confirmed after a period of monitoring that our reversal of the offending change has remediated the issue, and our service is healthy. Users with existing sessions that are still impacted should refresh their sessions to experience relief. 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. This specifically impacted users with existing sessions in Snowsight and not new sessions. Incident start time: 18:02 UTC January 08, 2026 Incident end time: 19:00 UTC January 08, 2026 Preliminary root cause: A change contained within the recent Snowsight release related to a network policy check caused issues with session deserialization, which resulted in errors for users with active sessions. A root cause analysis (RCA) document will be published within five business days.

4. postmortem Jan 15, 2026, 08:56 PM UTC

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

Read the full incident report →

Started Jan 08, 2026, 09:38 AM UTC· resolved Jan 08, 2026, 12:18 PM UTC

1. investigating Jan 08, 2026, 09:38 AM UTC

   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.

2. investigating Jan 08, 2026, 10:30 AM UTC

   Current status: We've confirmed that this issue is restricted to Snowsight availability, all other methods of accessing Snowflake remain available. We're actively engaging with our cloud service provider (CSP) to identify and resolve the issue. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. Workaround: This issue impacts Snowsight availability only. Snowflake services and features remain available via all other methods of access. Incident start time: 09:02 UTC January 08, 2026

3. identified Jan 08, 2026, 10:59 AM UTC

   Current status: Snowflake engineers have performed recovery actions expected to restore Snowsight connectivity and are currently confirming that service has resumed. In parallel, we remain engaged with our cloud service provider (CSP) to identify and resolve the issue.This issue has been confirmed as being restricted to Snowsight availability, all other methods of We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. ETA: Although an ETA is not yet available, our initial validations indicate service is beginning to return to expected levels. Workaround: This issue impacts Snowsight availability only. Snowflake services and features remain available via all other methods of access. Incident start time: 09:02 UTC January 08, 2026

4. identified Jan 08, 2026, 11:06 AM UTC

   Current status: Snowflake engineers have performed recovery actions expected to restore Snowsight connectivity and are currently confirming that service has resumed. In parallel, we remain engaged with our cloud service provider (CSP) to identify and resolve the issue. This issue has been confirmed as being restricted to Snowsight availability. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. ETA: Although an ETA is not yet available, our initial validations indicate service is beginning to return to expected levels. Workaround: This issue impacts Snowsight availability only. Snowflake services and features remain available via all other methods of access. Incident start time: 09:02 UTC January 08, 2026

5. monitoring Jan 08, 2026, 11:15 AM UTC

   Current status: Snowflake engineers have performed recovery actions to restore Snowsight connectivity and have confirmed that service has resumed. Customer experience: Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. Incident start time: 09:02 UTC January 08, 2026 Incident end time: 10:43 UTC January 08, 2026 Preliminary root cause: A third-party cloud platform experienced an as-yet-undiagnosed issue which caused underlying infrastructure for Snowsight to become unavailable.

6. resolved Jan 08, 2026, 12:18 PM UTC

   Current status: Snowflake engineers have performed recovery actions to restore Snowsight availability and monitored the environment to confirm that service has resumed. We remain engaged with our third-party cloud platform provider as they work to identify root cause and follow-up actions. 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. Incident start time: 09:02 UTC January 08, 2026 Incident end time: 10:43 UTC January 08, 2026 Preliminary root cause: A third-party cloud platform experienced an as-yet-undiagnosed issue which caused underlying infrastructure for Snowsight to become unavailable. A root cause analysis (RCA) document will be published within ten business days.

7. postmortem Jan 16, 2026, 02:41 PM UTC

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

Read the full incident report →

Started Dec 16, 2025, 03:48 AM UTC· resolved Dec 16, 2025, 05:25 PM UTC

1. investigating Dec 16, 2025, 03:48 AM UTC

   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 execute queries. Affected users may see a "SQL execution internal error" message or similar error messages. Incident start time: 02:55 UTC December 16, 2025

2. identified Dec 16, 2025, 04:34 AM UTC

   Current status: We've identified the source of the issue, and we're developing a fix to resolve the impact. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to execute queries. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025

3. identified Dec 16, 2025, 05:04 AM UTC

   Current status: We've developed the fix, and we're preparing it for deployment to the affected regions. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to execute queries. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimate is that service will be restored within 5 hours. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025

4. identified Dec 16, 2025, 05:50 AM UTC

   Current status: We're performing the final rounds of validation to ensure the fix will effectively restore service. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to execute queries and may experience query performance degradation. Data clustering may appear to be in an unhealthy state. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimate is that service will be restored within 4 hours. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025

5. identified Dec 16, 2025, 06:40 AM UTC

   Current status: We're continuing our validations and will provide another update within 2 hours, after which we anticipate the fix will begin deploying. Customer experience: Customers hosted in the specified regions may be unable to execute queries and may experience query performance degradation. Data clustering may appear to be in an unhealthy state. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimate is that service will be restored within 4 hours. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025

6. identified Dec 16, 2025, 08:36 AM UTC

   Current status: Validation of our solution has encountered an unexpected issue. We've resolved these issues, and we're continuing with our mitigation efforts. We will provide another update within 2 hours. Customer experience: Customers hosted in the specified regions may be unable to execute queries and may experience query performance degradation. Data clustering may appear to be in an unhealthy state. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimate is that service will be restored within 4 hours. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025

7. identified Dec 16, 2025, 10:31 AM UTC

   Current status: We've resolved the unexpected issues. We're continuing with our mitigation efforts. We will provide another update within 2 hours. Customer experience: Customers hosted in the specified regions may be unable to execute queries and may experience query performance degradation. Data clustering may appear to be in an unhealthy state. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimate is that service will be restored by 14:00 UTC. In the meantime, we recommend that customers using replication affected by this issue initiate their failover procedures. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025

8. identified Dec 16, 2025, 12:21 PM UTC

   Current status: We are executing our mitigation efforts. As mitigation progresses, customers might expect gradual improvements as we work through the resolution steps. We will provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to execute queries and may experience query performance degradation. Data clustering may appear to be in an unhealthy state. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimate is that service will be restored by 15:00 UTC. In the meantime, we recommend that customers using replication affected by this issue initiate their failover procedures. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025

9. identified Dec 16, 2025, 12:50 PM UTC

   Current status: We continue executing our mitigation efforts. As mitigation continues to progress, customers might expect gradual improvements as we work through the resolution steps. We will provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to execute queries and may experience query performance degradation. Data clustering may appear to be in an unhealthy state. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimate remains that service will be restored by 15:00 UTC. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025

10. identified Dec 16, 2025, 01:20 PM UTC

    Current status: We continue executing our mitigation efforts. As progress continues, customers will experience gradual improvements as we work through the resolution steps. We will provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to execute queries and may experience query performance degradation. Data clustering may appear to be in an unhealthy state. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimate remains that service will be restored by 15:00 UTC. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025

11. identified Dec 16, 2025, 01:48 PM UTC

    Current status: We continue executing our mitigation efforts and see significant improvements in the affected regions. We continue working through the resolution steps. We will provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to execute queries and may experience query performance degradation. Data clustering may appear to be in an unhealthy state. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimate remains that service will be restored by 15:00 UTC. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025

12. identified Dec 16, 2025, 02:15 PM UTC

    Current status: We continue executing our mitigation efforts and continue to see significant improvements in the affected regions. We continue working through the resolution steps. We will provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to execute queries and may experience query performance degradation. Data clustering may appear to be in an unhealthy state. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimate remains that service will be restored by 15:00 UTC. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025

13. identified Dec 16, 2025, 02:44 PM UTC

    Current status: We continue executing our mitigation efforts and continue to see improvements in the affected regions. We continue working through the resolution steps. We will provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to execute queries and may experience query performance degradation. Data clustering may appear to be in an unhealthy state. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimate remains that service will be restored by 15:00 UTC. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025

14. identified Dec 16, 2025, 03:00 PM UTC

    Current status: We've successfully mitigated all affected regions except Azure - East US 2 (Virginia), where we are continuing to work through the resolution steps for the remainder of the region. We will provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to execute queries and may experience query performance degradation. Data clustering may appear to be in an unhealthy state. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimate remains that service will be restored by 15:00 UTC. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025

15. identified Dec 16, 2025, 03:29 PM UTC

    Current status: We are continuing to work through the resolution steps for the Azure - East U.S. 2 (Virginia) region, which are taking longer than previously estimated. We will provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to execute queries and may experience query performance degradation. Data clustering may appear to be in an unhealthy state. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimate for service resolution has been updated to 16:30 UTC. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025

16. identified Dec 16, 2025, 03:57 PM UTC

    Current status: We are continuing to work through the resolution steps for the Azure - East U.S. 2 (Virginia) region. We will provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to execute queries and may experience query performance degradation. Data clustering may appear to be in an unhealthy state. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimated time for service resolution remains 16:30 UTC. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025

17. monitoring Dec 16, 2025, 04:28 PM UTC

    Current status: We've completed the resolution steps for the Azure - East U.S. 2 (Virginia) region. We expect that the majority of the impact should be mitigated at this time; however, we are currently monitoring and assessing for any residual impact. We'll continue to monitor the environment until we're confident all services are functioning properly. Since resolution is being observed in affected regions, failing over is no longer recommended for customers with replication enabled in other regions, unless they continue to experience impact. Customer experience: Customers hosted in the specified regions may have been unable to execute queries and may have experienced query performance degradation. Additionally, data clustering may have also appeared to be in an unhealthy state. Users may have experienced delays or failures when using Snowpipe or Snowpipe Streaming to ingest files, and users may have seen a "SQL execution internal error" message or similar error messages. Workaround: There were no available workarounds for this issue outside of customers with replication failing over to non-impacted regions. Incident start time: 02:55 UTC December 16, 2025 Incident end time: 15:59 UTC December 16, 2025 Preliminary root cause: Our initial investigation has identified that our most recent release introduced a backwards-incompatible database schema update. As a result, previous release packages errantly referenced the updated fields, resulting in version mismatch errors and causing operations to fail or take an extended amount of time to complete.

18. resolved Dec 16, 2025, 05:25 PM UTC

    Current status: We've implemented the fix for this issue and monitored the environment to confirm that the service was restored. Some customers may experience delays in ingestion as the backlog of requests is cleared. 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 execute queries and may have experienced query performance degradation. Additionally, data clustering may have appeared to be in an unhealthy state. Users may have experienced delays or failures when using Snowpipe or Snowpipe Streaming to ingest files, and users may have seen a "SQL execution internal error" message or similar error messages. Workaround: There were no available workarounds for this issue except for customers with replication failing over to non-impacted regions. Incident start time: 02:55 UTC December 16, 2025 Incident end time: 15:59 UTC December 16, 2025 Preliminary root cause: Our initial investigation has identified that our most recent release introduced a backwards-incompatible database schema update. As a result, previous release packages incorrectly referenced the updated fields, resulting in version mismatch errors and causing operations to fail or take an extended amount of time to complete. A root cause analysis (RCA) document will be published within five business days.

19. postmortem Dec 20, 2025, 02:02 AM UTC

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

Read the full incident report →

Started Dec 10, 2025, 12:23 AM UTC· resolved Dec 10, 2025, 01:59 AM UTC

1. investigating Dec 10, 2025, 12:23 AM UTC

   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 degraded performance or delayed query results when managing or querying data. Queries may take longer than usual to complete, and affected users may see timeout errors.

2. monitoring Dec 10, 2025, 01:12 AM UTC

   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 experience degraded performance or delayed query results when managing or querying data. Queries may take longer than usual to complete, and affected users may see timeout errors. Incident start time: 23:45 UTC December 09, 2025 Incident end time: 00:23 UTC December 10, 2025 Preliminary root cause: The metadata database infrastructure experienced an increase in workload, resulting in degraded query performance for a subset of customers.

3. resolved Dec 10, 2025, 01:59 AM UTC

   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 experience degraded performance or delayed query results when managing or querying data. Queries may take longer than usual to complete, and affected users may see timeout errors. Incident start time: 23:45 UTC December 09, 2025 Incident end time: 00:23 UTC December 10, 2025 Preliminary root cause: The metadata database infrastructure experienced an increase in workload, resulting in degraded query performance for a subset of customers. A root cause analysis (RCA) document will be published within five business days.

4. postmortem Dec 16, 2025, 12:59 AM UTC

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

Read the full incident report →

Started Nov 20, 2025, 08:19 PM UTC· resolved Nov 20, 2025, 11:01 PM UTC

1. investigating Nov 20, 2025, 08:19 PM UTC

   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 multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. Incident start time: 19:50 UTC November 20, 2025

2. investigating Nov 20, 2025, 09:13 PM UTC

   Current status: We're continuing to investigate the issue with Snowflake Data Cloud. In the meantime, we recommend that affected customers using replication initiate their failover procedures. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. Incident start time: 19:50 UTC November 20, 2025

3. monitoring Nov 20, 2025, 10:15 PM UTC

   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 multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. Incident start time: 19:50 UTC November 20, 2025 Incident end time: 21:15 UTC November 20, 2025 Preliminary root cause: Our investigation identified that a recent configuration change to our firewall rules resulted in a communication issue between our Cloud Services and Storage layer infrastructure. As a result, customer requests were unable to be processed successfully.

4. resolved Nov 20, 2025, 11:01 PM UTC

   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 multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data. Incident start time: 19:50 UTC November 20, 2025 Incident end time: 21:15 UTC November 20, 2025 Preliminary root cause: Our investigation identified that a recent configuration change to our firewall rules resulted in a communication issue between our Cloud Services and Storage layer infrastructure. As a result, customer requests were unable to be processed successfully. A root cause analysis (RCA) document will be published within five business days.

5. postmortem Dec 02, 2025, 10:33 PM UTC

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

Read the full incident report →

Started Nov 19, 2025, 06:49 AM UTC· resolved Nov 19, 2025, 06:49 AM UTC

1. resolved Nov 19, 2025, 06:49 AM UTC

   Current status: We've rolled back the configuration change 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 Snowpark Container Services services that expose public ingress endpoints. Affected customers saw a certificate error. Workaround: Affected customers could have worked around the issue by bypassing Transport Layer Security (TLS) verification. Incident start time: 04:13 UTC November 19, 2025 Incident end time: 06:18 UTC November 19, 2025 Preliminary root cause: A configuration change for optimizing our infrastructure was incorrectly implemented, which caused a certificate error. A root cause analysis (RCA) document will be published within five business days.

2. postmortem Nov 26, 2025, 11:54 PM UTC

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

Read the full incident report →

Started Nov 05, 2025, 03:58 PM UTC· resolved Nov 05, 2025, 08:10 PM UTC

1. investigating Nov 05, 2025, 03:58 PM UTC

   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.

2. identified Nov 05, 2025, 05:12 PM UTC

   Current status: We've observed elevated load on a backend database that is causing intermittent errors and timeouts in Snowsight. We've identified a background maintenance process that is contributing to periodic contention and degraded performance, and we're working on a mitigation to provide relief. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 15:27 UTC November 05, 2025

3. identified Nov 05, 2025, 06:14 PM UTC

   Current status: While our service health metrics indicate that impact may be occurring with less frequency, we're working to disable the background maintenance process that we've identified is contributing to the periodic contention and degraded performance of our service. We're closely monitoring our service health, and 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. ETA: We anticipate that our mitigation action to disable the background maintenance process contributing to impact should be complete in approximately two hours. Incident start time: 15:27 UTC November 05, 2025

4. monitoring Nov 05, 2025, 07:49 PM UTC

   Current status: We've disabled the background maintenance process that we've identified is contributing to the periodic contention and degraded performance of our service. We're closely monitoring our service health to ensure that this continues to provide relief and impact does not return. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. Incident start time: 15:27 UTC November 05, 2025 Incident end time: 18:36 UTC November 05, 2025 Preliminary root cause: A background maintenance process was contributing to periodic contention and degraded performance, resulting in elevated load on a backend database. This caused intermittent errors and timeouts in Snowsight.

5. resolved Nov 05, 2025, 08:10 PM UTC

   Current status: We've monitored our service health metrics after disabling the background maintenance process, and we've confirmed that this has resolved the issue. 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. Incident start time: 15:27 UTC November 05, 2025 Incident end time: 18:36 UTC November 05, 2025 Preliminary root cause: A background maintenance process was contributing to periodic contention and degraded performance, which resulted in elevated load on a backend database. This caused intermittent errors and timeouts in Snowsight. A root cause analysis (RCA) document will be published within five business days.

6. postmortem Nov 14, 2025, 12:07 AM UTC

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

Read the full incident report →

Started Nov 03, 2025, 08:44 PM UTC· resolved Nov 03, 2025, 09:23 PM UTC

1. investigating Nov 03, 2025, 08:44 PM UTC

   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 intermittent failures when resuming or managing virtual warehouses. Existing warehouses that are already running may be unaffected. Incident start time: 20:00 UTC November 03, 2025

2. monitoring Nov 03, 2025, 09:05 PM UTC

   Current status: We have confirmed that our third-party cloud platform has 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 experience delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that are already running may be unaffected. Incident start time: 20:00 UTC November 03, 2025 Incident end time: 20:39 UTC November 03, 2025 Preliminary root cause: A third-party cloud platform experienced a resource issue, which caused intermittent delays or failures when resuming or managing virtual warehouses.

3. resolved Nov 03, 2025, 09:23 PM UTC

   Current status: We've monitored the environment to confirm that all services are functioning properly after our third-party cloud platform implemented the fix for this issue. 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 or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that were already running may have been unaffected. Incident start time: 20:00 UTC November 03, 2025 Incident end time: 20:39 UTC November 03, 2025 Preliminary root cause: A third-party cloud platform experienced a resource issue, which caused intermittent delays or failures when resuming or managing virtual warehouses. A root cause analysis (RCA) document will be published within ten business days.

4. postmortem Nov 20, 2025, 03:20 PM UTC

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

Read the full incident report →

Started Oct 22, 2025, 08:23 PM UTC· resolved Oct 22, 2025, 09:30 PM UTC

1. investigating Oct 22, 2025, 08:23 PM UTC

   Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. Customer experience: A subset of customers hosted in the specified regions may experience intermittent delays when using Snowpipe and may experience delayed query execution. Incident start time: 19:00 UTC October 22, 2025

2. monitoring Oct 22, 2025, 09:01 PM UTC

   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: A subset of customers hosted in the specified regions may have experienced intermittent delays when using Snowpipe and may have experienced delayed query execution. Incident start time: 19:00 UTC October 22, 2025 Incident end time: 20:45 UTC October 22, 2025 Preliminary root cause: Our investigation identified that this issue was related to a configuration change that unexpectedly increased compilation times, leading to delayed query execution and Snowpipe ingestion.

3. resolved Oct 22, 2025, 09:30 PM UTC

   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: A subset of customers hosted in the specified regions may have experienced intermittent delays when using Snowpipe and may have experienced delayed query execution. Incident start time: 19:00 UTC October 22, 2025 Incident end time: 20:45 UTC October 22, 2025 Preliminary root cause: Our investigation identified that this issue was related to a configuration change that unexpectedly increased compilation times, leading to delayed query execution and Snowpipe ingestion. A root cause analysis (RCA) document will be published within five business days.

4. postmortem Oct 30, 2025, 09:19 PM UTC

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

Read the full incident report →

Started Oct 20, 2025, 08:36 AM UTC· resolved Oct 21, 2025, 01:57 AM UTC

1. identified Oct 20, 2025, 08:36 AM UTC

   Current status: We've identified an issue with a third-party cloud platform, and we're coordinating with the provider 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 intermittent delays or failures when accessing or using Snowflake services and features. This may include slower query execution, intermittent availability, or limited feature functionality. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 07:20 UTC October 20, 2025

2. identified Oct 20, 2025, 09:28 AM UTC

   Current status: We're continuing to coordinate with our third-party cloud platform 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 intermittent delays or failures when accessing or using Snowflake services and features. This may include slower query execution, intermittent availability, or limited feature functionality. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 07:20 UTC October 20, 2025

3. identified Oct 20, 2025, 10:25 AM UTC

   Current status: Our third-party cloud platform implemented a mitigation, and we are slowly seeing signs of recovery. However, services continue to be impacted. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may experience intermittent delays or failures when accessing or using Snowflake services and features. This may include slower query execution, intermittent availability, or limited feature functionality. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 07:20 UTC October 20, 2025

4. identified Oct 20, 2025, 11:17 AM UTC

   Current status: Our third-party cloud platform implemented a mitigation and is in the process of recovery, which we are also seeing signs of. However, services continue to be impacted due to third-party service provider backlog, with the largest impact observed in virtual warehouse management. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may experience intermittent delays or failures when accessing or using Snowflake services and features. This may include slower query execution, intermittent availability, or limited feature functionality. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 07:20 UTC October 20, 2025

5. identified Oct 20, 2025, 11:48 AM UTC

   Current status: Our third-party cloud platform implemented a mitigation and is in the process of recovery, which we are also seeing signs of. However, services continue to be impacted due to third-party service provider backlog, with the largest impact observed in virtual warehouse management. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may experience intermittent delays or failures when accessing or using Snowflake services and features. This may include slower query execution, intermittent availability, or limited feature functionality. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 07:20 UTC October 20, 2025

6. identified Oct 20, 2025, 12:45 PM UTC

   Current status: Our third-party cloud platform implemented a mitigation and is in the process of recovery, which we are also seeing signs of. However, services continue to be impacted due to third-party service provider backlog and capacity issues, with the largest impact observed in virtual warehouse management. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may experience intermittent delays or failures when accessing or using Snowflake services and features. This may include slower query execution, intermittent availability, or limited feature functionality. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 07:20 UTC October 20, 2025

7. identified Oct 20, 2025, 01:22 PM UTC

   Current status: Our third-party cloud platform implemented a mitigation and is in the process of recovery, which we are also seeing signs of. However, services continue to be impacted due to third-party service provider backlog and capacity issues, with the largest impact observed in virtual warehouse management. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may experience intermittent delays or failures when accessing or using Snowflake services and features. This may include slower query execution, intermittent availability, or limited feature functionality. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 07:20 UTC October 20, 2025

8. identified Oct 20, 2025, 01:47 PM UTC

   Current status: Our third-party cloud platform implemented a mitigation and is in the process of recovery. However, services continue to be impacted due to third-party service provider backlog, capacity issues, and imposed rate limiting, with the largest impact observed in virtual warehouse management and Snowsight usage. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 07:20 UTC October 20, 2025

9. identified Oct 20, 2025, 02:54 PM UTC

   Current status: While our telemetry shows early signs of improvement, we are continuing to monitor the third-party service provider's recovery progress, and we'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: While an exact ETA is not yet available, we'll provide an exact timeline as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures for immediate relief. Incident start time: 07:20 UTC October 20, 2025

10. identified Oct 20, 2025, 03:59 PM UTC

    Current status: Our third-party cloud platform has identified network connectivity issues and isolated their source. They are implementing mitigations, and we are continuing to monitor recovery progress. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: While an exact ETA is not yet available, we'll provide an exact timeline as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures for immediate relief. Incident start time: 07:20 UTC October 20, 2025

11. identified Oct 20, 2025, 04:57 PM UTC

    Current status: We are closely monitoring as our third-party cloud platform continues to observe their service health following their latest mitigation actions. While they report initial signs of recovery due to these steps, they are assessing additional measures to address the rate throttling impacting Snowflake's services. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: While an exact ETA is not yet available, we'll provide an exact timeline as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures for immediate relief. Incident start time: 07:20 UTC October 20, 2025

12. identified Oct 20, 2025, 06:00 PM UTC

    Current status: Our third-party cloud platform continues to observe their service health following their latest mitigation actions, and they have reported ongoing signs of recovery. In parallel, they're taking additional measures to address the rate throttling impacting Snowflake's services. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: While an exact ETA is not yet available, we'll provide an exact timeline as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures for immediate relief. Incident start time: 07:20 UTC October 20, 2025

13. identified Oct 20, 2025, 07:12 PM UTC

    Current status: Our third-party cloud platform continues to see their service health recovering due to their mitigations, and actions to address the rate throttling impacting Snowflake's services are ongoing. We are continuing to monitor as these actions progress to ensure Snowflake's services recover. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: While an exact ETA is not yet available, we'll provide an exact timeline as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures for immediate relief. Incident start time: 07:20 UTC October 20, 2025

14. identified Oct 20, 2025, 08:17 PM UTC

    Current status: Our third-party cloud platform continues to see their service health recover, and they are continuing to address the rate throttling. Our service health metrics are beginning to show some signs of recovery, and we will continue to monitor to ensure this positive trend continues. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: While an exact ETA is not yet available, we'll provide an exact timeline as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures for immediate relief. Incident start time: 07:20 UTC October 20, 2025

15. identified Oct 20, 2025, 08:31 PM UTC

    Current status: Our third-party cloud platform is continuing to take action to mitigate the issue and rate throttling. Based on the current progress, we estimate that the Snowflake service should be recovered by approximately 21:30 UTC. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: We anticipate that the issue will be resolved by approximately 21:30 UTC. We recommend that customers who initiated their failover procedures should not fail back until our service has fully recovered within the impacted region. Incident start time: 07:20 UTC October 20, 2025

16. monitoring Oct 20, 2025, 09:59 PM UTC

    Current status: While our third-party cloud platform continues to monitor their service health following their mitigation actions, we have observed that the Snowflake service health has recovered as of 21:18 UTC. We're continuing to monitor to ensure our service remains healthy, and we recommend that customers who initiated their failover procedures should not fail back until we have confirmed with our third-party cloud platform that it is safe to do so. Customer experience: Customers hosted in the specified regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data. Incident start time: 07:20 UTC October 20, 2025 Incident end time: 21:18 UTC October 20, 2025 Preliminary root cause: A third-party cloud platform experienced networking issues, which caused access problems for Snowflake services and features impacting Snowflake customers hosted in the specified regions.

17. resolved Oct 21, 2025, 01:57 AM UTC

    Current status: We've coordinated with our third-party cloud platform to implement the fix for this issue, and we've monitored the environment to confirm that service was restored. We have observed stable and healthy performance across the Snowflake service since 21:18 UTC. Failback operations to origin regions may now be initiated by customers who previously failed over. In light of the recent operational severity, we provide guidance for customers to cautiously evaluate their failback criticality and determine the appropriate timing. If the failback is not strictly time-sensitive or immediately critical to your business operations, postponing the procedure until the next business day will minimize potential transition risks. 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 multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data. Incident start time: 07:20 UTC October 20, 2025 Incident end time: 21:18 UTC October 20, 2025 Preliminary root cause: A third-party cloud platform experienced networking issues, which were traced to the failure of an underlying internal subsystem responsible for monitoring the health of its network load balancers. This ultimately caused access issues for Snowflake services and features, impacting customers hosted in the specified regions. A root cause analysis (RCA) document will be published within ten business days.

18. postmortem Nov 04, 2025, 05:55 AM UTC

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

Read the full incident report →

Started Oct 14, 2025, 09:14 PM UTC· resolved Oct 14, 2025, 11:31 PM UTC

1. investigating Oct 14, 2025, 09:14 PM UTC

   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 multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data.

2. investigating Oct 14, 2025, 10:16 PM UTC

   Current status: Our preliminary investigation has identified that a critical metadata management service within our cloud services layer is failing. Immediate mitigation actions to restart the cluster have not provided relief, and we are continuing our analysis of affected components within the environment to isolate the source of the issue and identify recovery actions. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. Incident start time: 20:35 UTC October 14, 2025

3. monitoring Oct 14, 2025, 10:49 PM UTC

   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 multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. Incident start time: 20:35 UTC October 14, 2025 Incident end time: 22:31 UTC October 14, 2025 Preliminary root cause: The investigation determined that, following an infrastructure update, a subset of newly added machines experienced connectivity issues and were unable to communicate with other components.

4. resolved Oct 14, 2025, 11:31 PM UTC

   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 be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. Incident start time: 20:35 UTC October 14, 2025 Incident end time: 22:31 UTC October 14, 2025 Preliminary root cause: An investigation determined that, following a recent infrastructure update, a subset of newly added machines experienced connectivity issues and were unable to communicate with other components. A root cause analysis (RCA) document will be published within five business days.

5. postmortem Oct 22, 2025, 12:15 AM UTC

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

Read the full incident report →