Snowflake

Affected: Databases, Tables, and Views, Applications

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-10-21 07:45 UTC

   Current status: We identified that a subset of infrastructure responsible for routing service traffic in the affected region became intermittently unhealthy, which caused some requests to fail. We removed the affected infrastructure from service and are monitoring the...

2. resolved 2026-10-21 08:36 UTC

   Current status: We've monitored the environment and confirmed 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...

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Databases, Tables, and Views, Data Loading and Unloading, Applications

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-20 06:34 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 region may be unable to access or use multiple Snowflake services and features, including Snowflake Postgres....

2. identified 2026-10-20 07:22 UTC

   Current status: We've identified an issue with a third-party cloud platform that's affecting part of the infrastructure in the specified region, and we're coordinating with the provider to develop and implement a fix to restore service. We have identified an issue with one of...

3. identified 2026-10-20 07:49 UTC

   Current status: Our monitoring has shown healthy service since 06:40 UTC October 20, 2026, but the affected availability zone remains unavailable at our third-party cloud platform provider. We've stopped new workloads from being placed in that zone and paused routine software...

4. identified 2026-10-20 09:39 UTC

   Current status: Our monitoring has shown healthy service since 06:40 UTC October 20, 2026, but the affected availability zone remains unavailable at our third-party cloud platform provider. We've stopped new workloads from being placed in that zone and paused routine software...

5. identified 2026-10-20 12:30 UTC

   Our monitoring still shows healthy service since 06:40 UTC October 20, 2026. As per updates on the Cloud Provider's status page https://status.cloud.google.com, some infrastructure in the affected availability zone at our third-party cloud platform provider has begun to come...

6. identified 2026-10-20 14:34 UTC

   Current status: Our Cloud Provider has confirmed via their status page https://status.cloud.google.com that the issue has been largely mitigated. We're are closely monitoring service health and are preparing to revert our previously completed precautionary changes; though at...

7. resolved 2026-10-20 15:26 UTC

   Current status: We've monitored the environment and confirmed that service has been 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...

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Databases, Tables, and Views

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-10-19 00:26 UTC

   Current status: We identified an issue with our third-party cloud platform that affected private connectivity in the specified region. The issue has been resolved, and we're working with the provider to confirm the underlying cause. We'll continue to monitor the environment...

2. resolved 2026-10-19 01:11 UTC

   Current status: We've monitored the environment and confirmed that service has been 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...

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Databases, Tables, and Views, Applications

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-10-16 01:14 UTC

   Current status: We identified that a subset of infrastructure responsible for processing queries and Snowsight requests in the affected region experienced elevated load, which caused intermittent delays and query failures. The load has since subsided, and query processing and...

2. resolved 2026-10-16 01:43 UTC

   Current status: We've monitored the environment and confirmed 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...

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Data Loading and Unloading

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-13 15:53 UTC

   Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 1 hour. Customer experience: Customers hosted in the specified regions may be unable to execute scheduled or manual tasks. Tasks may be stuck in a pending state or fail to...

2. investigating 2026-10-13 16:40 UTC

   Current status: Our investigation has identified that tasks appear to be failing due to an a potential issue with a backend record lookup on the metadata database layer, and we're working to determine what's causing these records to return null and result in task failures. We'll...

3. investigating 2026-10-13 17:38 UTC

   Current status: We've determined that a directory issue within the components of the metadata store responsible for facilitating the impacted tasks is preventing some task records from being read consistently, which is causing the task failures. We're working to identify the...

4. investigating 2026-10-13 18:36 UTC

   Current status: Our investigation indicates that the directory issue is limited to the records the metadata store keeps for task execution. We're developing a fix to restore the impacted metadata and resolve the impact; however, due to the complexity of the issue, we expect this...

5. investigating 2026-10-13 20:06 UTC

   Current status: We're continuing our development of the fix to restore the impacted metadata. We'll provide another update within 2 hours. While our remediation efforts are ongoing, before rerunning a task that's reported as failed, we recommend checking query history to confirm...

6. investigating 2026-10-13 21:47 UTC

   Current status: We're validating our fix to restore the impacted metadata and preparing to begin deployment to the affected region. We'll provide another update within 2 hours. While our remediation efforts are ongoing, before rerunning a task that's reported as failed, we...

7. investigating 2026-10-13 23:54 UTC

   Current status: We're continuing to develop the fix to restore the impacted task metadata. Once it's fully developed and validated, we'll begin deploying it to the affected region. While our remediation efforts are ongoing, before rerunning a task that's reported as failed, we...

8. investigating 2026-10-14 03:19 UTC

   Current status: We've modified our remediation approach. After further investigation, we've determined that restarting infrastructure in the affected region is the most effective way to restore normal task execution. The infrastructure restart effort is in progress, and we've...

9. identified 2026-10-14 21:47 UTC

   Current status: While the infrastructure restarts in the affected region are still in progress, our monitoring indicates that the service is gradually recovering and the majority of failed tasks are now succeeding after being restarted. We're continuing to monitor the affected...

10. identified 2026-10-15 04:57 UTC

    Current status: The infrastructure restarts in the affected region are complete, and our monitoring indicates that the service is continuing to recover. Tasks that were scheduled before the restarts and haven't yet run afterward may be marked as failed the next time they run,...

11. monitoring 2026-10-15 21:03 UTC

    Current status: The infrastructure restarts in the affected region are complete, and our monitoring indicates that the error leading to task failure has been resolved and previously affected tasks are now consistently running successfully. While the functional impact of the...

12. resolved 2026-10-15 21:51 UTC

    Current status: We've implemented the fix for this issue and monitored the environment to confirm that service was restored. We're continuing our deployment of a secondary fix to restore the remaining task graph run history for the affected time period. If you experience...

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Applications, Applications, Applications

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure, Cloudflare.

Started during Cloudflare: Network routing issue.

1. investigating 2026-10-06 14:44 UTC

   Current status: We're investigating an issue affecting user connections to Snowflake. We've narrowed our investigation to network connectivity between certain customer locations and the affected regions, and we've engaged third-party providers to assist. We're continuing to...

2. monitoring 2026-10-06 15:17 UTC

   Current status: A third-party network provider reported that they are implementing a fix for the connectivity problems, and we have since observed signs of recovery in our health checks. We’ll continue to monitor the environment until we’re confident all services are functioning...

3. resolved 2026-10-06 15:57 UTC

   Current status: We've coordinated with our third-party provider who implemented a 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...

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Databases, Tables, and Views, Databases, Tables, and Views, Virtual Warehouses, Virtual Warehouses, Data Loading and Unloading, Data Loading and Unloading, Applications, Applications

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-09-27 02:15 UTC

   Current status: We identified an issue with our third-party cloud platform that caused impact to Snowflake services. We've coordinated with our third-party cloud platform to implement the fix for this issue, and we'll continue to monitor the environment until we're confident all...

2. resolved 2026-09-27 03:16 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. If you experience additional issues or have questions, please open a support case via Snowflake...

3. postmortem 2026-10-09 09:55 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/INC20000239](https://community.snowflake.com/s/article/INC20000239)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Databases, Tables, and Views, Virtual Warehouses, Data Loading and Unloading, Applications, Security and Privacy Features

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-09-25 23:00 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...

2. monitoring 2026-09-25 23:26 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 have been unable to access or use multiple core...

3. resolved 2026-09-26 00:20 UTC

   Current status: We've implemented the fix for this issue and monitored the environment to confirm that service was restored. Most impact was resolved by 22:59 UTC, with the remaining backlog for scheduled and serverless task execution fully clearing by 23:43 UTC. If you...

4. postmortem 2026-10-02 23:36 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/INC20000237](https://community.snowflake.com/s/article/INC20000237)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Databases, Tables, and Views, Databases, Tables, and Views, Databases, Tables, and Views, Databases, Tables, and Views, Databases, Tables, and Views, Databases, Tables, and Views

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-14 04:48 UTC

   Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 1 hour. Customer experience: Customers in the affected regions may experience performance degradation or issues logging into Snowflake, including delayed sign-ins, query...

2. identified 2026-09-14 05:18 UTC

   Current status: We've identified the source of the issue, and we're developing and implementing a fix to restore service. We'll provide another update within 1 hour. Customer experience: Customers hosted in the affected deployments may experience performance degradation or...

3. monitoring 2026-09-14 05:40 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 affected deployments may have experienced performance degradation or...

4. resolved 2026-09-14 06:09 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...

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Databases, Tables, and Views, Databases, Tables, and Views

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-09-11 07:18 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...

2. investigating 2026-09-11 07:44 UTC

   Current status: We're continuing to investigate the issue with Snowflake Data Cloud. We'll provide another 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....

3. investigating 2026-09-11 08:12 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 region may be unable to sign in to Snowsight, and may receive an error message such as...

4. identified 2026-09-11 09:08 UTC

   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 region may be unable to sign in to Snowsight, and may...

5. monitoring 2026-09-11 09:27 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 region may have been unable to sign in to Snowsight, and...

6. monitoring 2026-09-11 11:24 UTC

   Current status: We've identified additional impact in the AWS - Asia Pacific (Tokyo) region, in which we've applied the same fix for this issue. We'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers...

7. resolved 2026-09-11 13:19 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...

8. postmortem 2026-09-18 14:28 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/INC20000213](https://community.snowflake.com/s/article/INC20000213)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Databases, Tables, and Views, Virtual Warehouses, Data Loading and Unloading, Applications, Snowpark Container Services, AI and ML, Organization and Account Management, Alerts and Notifications, Business Continuity

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-09 21:53 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...

2. identified 2026-09-09 22:08 UTC

   Current status: We've identified the source of the issue, and we're implementing a fix to restore service. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake...

3. monitoring 2026-09-09 22:48 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 have been unable to access or use multiple core...

4. resolved 2026-09-09 23:51 UTC

   Current status: We've monitored the environment and confirmed that service has been 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...

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Databases, Tables, and Views, Applications, Developer Tools

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-04 07:34 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. ETA: An ETA is not...

2. investigating 2026-09-04 08:05 UTC

   Current status: We're continuing to investigate the issue with Snowflake Data Cloud. 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....

3. investigating 2026-09-04 08:35 UTC

   Current status: We're continuing to actively investigate the issue with Snowflake Data Cloud. The specific focus at this time is on infrastructure components responsible for authorizing incoming traffic. We'll provide another update within 30 minutes. Customer experience:...

4. monitoring 2026-09-04 09:04 UTC

   Current status: We've implemented the fix for this issue by rolling back a configuration update to the underlying infrastructure. Our telemetry and internal validations indicate that service has been restored. We'll continue to monitor the environment until we're confident all...

5. resolved 2026-09-04 10:10 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...

6. postmortem 2026-09-14 22:14 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/INC20000199](https://community.snowflake.com/s/article/INC20000199)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-01 09:58 UTC

   Current status: We're investigating an issue affecting sign-ins to Snowflake Cowork. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to sign in to Snowflake Cowork, and may see a message indicating that...

2. identified 2026-09-01 10:32 UTC

   Current status: We've identified the source of the issue, and we're developing and implementing a fix to restore service. We'll provide another update within 1 hour. Customer experience: Customers hosted in the specified regions may be unable to sign in to Snowflake Cowork, and...

3. identified 2026-09-01 11:36 UTC

   Current status: We've identified the source of the issue, and are continuing the deployment of the fix to restore service. The majority of our customers should now be able to sign back into Snowflake Cowork. We'll provide another update within 1 hour. Customer experience:...

4. monitoring 2026-09-01 12:44 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 have been unable to sign in to Snowflake...

5. resolved 2026-09-01 13:50 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...

6. postmortem 2026-09-09 11:25 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/INC20000190](https://community.snowflake.com/s/article/INC20000190)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Databases, Tables, and Views, Virtual Warehouses, Data Loading and Unloading, Applications, Snowpark Container Services

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-31 17:20 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...

2. identified 2026-08-31 17:31 UTC

   Current status: We identified and have since reverted a problematic change as a potential mitigation. Initial telemetry indicates that the service is recovering. We will continue to monitor to confirm recovery. We'll provide an update within 30 minutes. Customer experience:...

3. identified 2026-08-31 17:59 UTC

   Current status: We are continuing to monitor service recovery, and have confirmed that the majority of service impact has been resolved as of 17:25 UTC with some residual impact to Snowsight access and Snowpipe Streaming. We'll provide an update within 30 minutes. Customer...

4. monitoring 2026-08-31 18:45 UTC

   Current status: We've implemented a fix to address the residual impact, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified region may have been unable to access or use...

5. resolved 2026-08-31 19:44 UTC

   Current status: We've monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the...

6. postmortem 2026-09-09 17:27 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/INC20000188](https://community.snowflake.com/s/article/INC20000188)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Virtual Warehouses, Snowpark Container Services

1. identified 2026-08-28 00:07 UTC

   Current status: We've determined that a capacity constraint at our third-party cloud platform has limited the availability of compute resources in the specified region. We're actively working to identify and implement alternative compute options to reduce impact for affected...

2. identified 2026-08-28 23:16 UTC

   Current status: We're continuing to coordinate with our third-party cloud platform provider to restore the compute capacity needed for Snowpark Container Services in the specified region. In parallel, we are taking the following steps to mitigate impact: - We have implemented...

3. identified 2026-08-31 23:36 UTC

   Current status: We have taken additional steps to preserve available compute resources in the specified region, including adjusting compute pool scaling to reduce non-essential resource consumption. We continue to prioritize available resources for Business Critical Edition...

4. identified 2026-09-07 23:50 UTC

   Current status: We've made additional adjustments to further reduce non-essential resource consumption and preserve available compute resources in the specified region. We're continuing to develop a software update to enable additional compute resources, and our other mitigation...

5. identified 2026-09-11 00:04 UTC

   Current status: Our third-party cloud platform provider has informed us that they expect to be able to provide additional capacity allocation by mid-October. In the meantime, we are working to preserve compute resources available to us, reduce non-essential resource consumption,...

6. identified 2026-09-17 23:04 UTC

   Current status: We've taken additional steps with our warehouse team to reduce provisioning latencies for virtual warehouses, and we've observed some improvement in provisioning latencies as a result. Resource availability remains variable and correlated to overall demand, with...

7. identified 2026-09-24 23:13 UTC

   Current status: We've received an update from our third-party cloud provider that improvement for resource availability in this region is now projected by the end of October. In the meantime, we’re continuing our efforts to reduce virtual warehouse provisioning times, building...

8. identified 2026-10-01 22:29 UTC

   Current status: Since our last update, we have seen periods of improved provisioning performance while preserving available compute resources and coordinating closely with our third-party cloud provider. Resource availability remains constrained and variable, and provisioning...

9. identified 2026-10-08 21:37 UTC

   Current status: Since our last update, capacity availability and provisioning performance for virtual warehouses have materially improved. Additional capacity has become available in the region, and Snowflake has increased the resources reserved for customer workloads. We are...

10. identified 2026-10-15 21:22 UTC

    Current status: Since our last update, we have seen improvement in Snowpark Container Services availability. Additional capacity became available in the specified region and has been reserved for customer workloads. Virtual warehouse capacity and provisioning performance also...

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Security and Privacy Features, Security and Privacy Features, Security and Privacy Features

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-27 19:05 UTC

   Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 1 hour. Customer experience: Customers hosted in the specified regions may experience connectivity issues when attempting to connect to Snowflake via private connectivity...

2. identified 2026-08-27 19:22 UTC

   Current status: We've identified the source of the issue, and we're implementing a fix to restore service. We'll provide another update within 1 hour. Customer experience: Customers hosted in the specified regions may experience connectivity issues when attempting to connect to...

3. monitoring 2026-08-27 19:54 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 have experienced connectivity issues when...

4. resolved 2026-08-27 20:26 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...

5. postmortem 2026-09-03 21:03 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/INC20000182](https://community.snowflake.com/s/article/INC20000182)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Databases, Tables, and Views, Applications

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-25 03:53 UTC

   Current status: We're investigating an issue with Snowflake Data Cloud in the Southeast Asia region. We'll provide an update within 30 minutes. Customer experience: Customers hosted in the Southeast Asia region may be unable to access Snowflake services due to infrastructure...

2. monitoring 2026-08-25 04:10 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. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may...

3. resolved 2026-08-25 04:35 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...

4. postmortem 2026-09-03 01:17 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/INC20000175](https://community.snowflake.com/s/article/INC20000175)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Applications

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-24 16:22 UTC

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

2. identified 2026-08-24 16:53 UTC

   Current status: We've identified an issue with a system configuration that is causing authentication problems in Snowsight, and we're developing and implementing a fix to restore service. We'll provide an update within 30 minutes. Customer experience: Customers hosted in the...

3. identified 2026-08-24 17:17 UTC

   Current status: We're in the process of implementing a fix for this issue. We'll provide an update within the next 60 minutes. Customer experience: Customers hosted in the specified region may be unable to remain logged in to Snowsight, experiencing immediate logout after...

4. monitoring 2026-08-24 17:37 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 region may have been unable to remain logged in to...

5. resolved 2026-08-24 18:03 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...

6. postmortem 2026-08-31 22:54 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/INC20000173](https://community.snowflake.com/s/article/INC20000173)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Security and Privacy Features

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-20 13:47 UTC

   Current status: We're investigating an issue with Snowflake Data Cloud. We've engaged the associated Cloud Service Provider to investigate and troubleshoot this issue further. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified...

2. identified 2026-08-20 14:19 UTC

   Current status: We're investigating an issue with Snowflake Data Cloud. We've engaged the associated Cloud Service Provider to investigate and troubleshoot this issue further. We'll provide an update within 30 minutes. Customer experience: Customers hosted in the specified...

3. monitoring 2026-08-20 14:39 UTC

   Current status: We've coordinated with our third-party cloud platform, which has implemented a mitigation for this issue. We will continue to monitor the environment until we're confident that all services are functioning properly. Customer experience: Customers hosted in the...

4. resolved 2026-08-20 15:43 UTC

   Current status: The third-party cloud platform confirmed that the mitigation was complete, and its automated recovery system appears to have initiated. We independently monitored the environment and verified that service was restored. If you experience additional issues or have...

5. postmortem 2026-09-03 20:06 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/INC20000168](https://community.snowflake.com/s/article/INC20000168)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: AI and ML

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-18 12:58 UTC

   Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 1 hour. Customer experience: Customers hosted in the specified regions may experience issues with AI and ML functionality. Specifically, when using Cortex Code in Snowsight,...

2. identified 2026-08-18 13:33 UTC

   Current status: We've identified an issue with container scheduling in our compute infrastructure that is affecting AI and ML functionality, and we're implementing a fix to restore service. We'll provide another update within 30 minutes. Customer experience: Customers hosted in...

3. monitoring 2026-08-18 13:55 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. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified region may...

4. resolved 2026-08-18 14:51 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...

5. postmortem 2026-08-25 22:42 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/INC20000163](https://community.snowflake.com/s/article/INC20000163)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Applications

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-14 17:29 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 using Snowsight....

2. identified 2026-08-14 17:58 UTC

   Current status: We've identified a system configuration issue affecting Snowsight, and we're implementing a fix to restore service. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to access or use...

3. monitoring 2026-08-14 18:30 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 region may have been unable to access or use Snowsight and...

4. resolved 2026-08-14 19:35 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...

5. postmortem 2026-08-21 21:47 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/INC20000158](https://community.snowflake.com/s/article/INC20000158)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Applications

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-08-14 15:19 UTC

   Current status: We've identified an issue that caused elevated error rates for Snowsight availability, and we've validated that service health has returned to normal following action by automated recovery systems. We'll continue to monitor the environment until we're confident...

2. resolved 2026-08-14 16:28 UTC

   Current status: We've monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the...

3. postmortem 2026-08-22 02:37 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/INC20000157](https://community.snowflake.com/s/article/INC20000157)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: AI and ML

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-05 14:41 UTC

   Current status: We're continuing to investigate the issue with Snowflake Data Cloud. We're investigating a portion of infrastructure that appears unhealthy to develop a mitigation plan. We'll provide another update within 1 hour. Customer experience: Customers hosted in the...

2. identified 2026-08-05 15:00 UTC

   Current status: We've identified an issue with the underlying infrastructure supporting CoCo services, and we're implementing a fix to restore service. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to...

3. monitoring 2026-08-05 15:14 UTC

   Current status: We've completed implementing our fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified...

4. resolved 2026-08-05 15:49 UTC

   Current status: We've confirmed that this issue has been resolved, and we have monitored the environment to confirm that the affected functionality is now working as expected. If you experience additional issues or have questions, please open a support case via Snowflake...

5. postmortem 2026-08-14 06:58 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/INC20000139](https://community.snowflake.com/s/article/INC20000139)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Virtual Warehouses

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-03 14:11 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 start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck...

2. investigating 2026-08-03 14:39 UTC

   Current status: We're continuing to investigate the issue with Snowflake Data Cloud, and we're analyzing recent changes and telemetry to determine a mitigation plan. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions...

3. investigating 2026-08-03 15:15 UTC

   Current status: We have so far not identified any recent changes directly contributing to this problem and are currently focused on investigating performance issues affecting the system that controls virtual warehouse management. We'll provide another update within 30 minutes....

4. monitoring 2026-08-03 15:46 UTC

   Current status: We have identified an unhealthy Cloud Services component that is preventing virtual warehouses from starting or resuming. We are implementing a fix and will continue to monitor to confirm that we have fully recovered. We'll provide another update within 30...

5. investigating 2026-08-03 16:42 UTC

   Current status: While we observed a period of recovery, our telemetry identified a recurrence of impact. We are implementing a mitigation to restore warehouse functionality, and we’ll provide another update within 30 minutes. Customer experience: Customers hosted in the...

6. monitoring 2026-08-03 17:17 UTC

   Current status: We have identified that the previously affected Cloud Services component became unhealthy again, which is preventing virtual warehouses from starting or resuming. We've implemented an additional fix and we're continuing to monitor to confirm that we have fully...

7. monitoring 2026-08-03 18:15 UTC

   Current status: We've confirmed that our service has remained stable since 16:35 UTC, following our mitigation action; however, we're continuing to monitor the environment to confirm that the affected functionality continues to work as expected. Customer experience: Customers...

8. resolved 2026-08-03 20:58 UTC

   Current status: We've confirmed that this issue has been resolved, and we have monitored the environment to confirm that the affected functionality is now working as expected. If you experience additional issues or have questions, please open a support case via Snowflake...

9. postmortem 2026-08-11 01:02 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/INC20000129](https://community.snowflake.com/s/article/INC20000129).

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Applications

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-08-03 05:53 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 Snowsight login failures, elevated page load times, or session timeouts...

2. identified 2026-08-03 06:47 UTC

   Current status: We've identified the source of the issue, and we're developing and implementing a fix to restore service. We'll provide another update within 1 hour. Customer experience: Customers hosted in the specified region may experience intermittent Snowsight login...

3. monitoring 2026-08-03 06:58 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 region may have experienced intermittent Snowsight login...

4. monitoring 2026-08-03 06:59 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 region may have experienced intermittent Snowsight login...

5. resolved 2026-08-03 08:15 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...

6. postmortem 2026-08-11 02:00 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/INC20000128](https://community.snowflake.com/s/article/INC20000128)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-30 03:00 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 log in to Snowsight. Affected users may encounter HTTP 404 errors or "Incoming...

2. identified 2026-07-30 03:30 UTC

   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 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to log in to Snowsight. Affected...

3. monitoring 2026-07-30 04:17 UTC

   Current status: We've reverted a recent configuration change and confirmed that service has been restored. 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...

4. resolved 2026-07-30 04:56 UTC

   Current status: We've monitored the environment and confirmed that reverting the configuration change restored service. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer...

5. postmortem 2026-08-10 04:31 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/INC20000115](https://community.snowflake.com/s/article/INC20000115)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Databases, Tables, and Views, Virtual Warehouses

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-25 09:05 UTC

   Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 1 hour. Customer experience: Customers hosted in the specified regions may experience longer than expected warehouse resume and spin-up times for standard warehouses. All other...

2. identified 2026-07-25 09:57 UTC

   Current status: We've identified the source of the issue, and we're developing and implementing a fix to restore service. We'll provide another update within 1 hour. Customer experience: Customers hosted in the specified regions may experience intermittent delays or failures...

3. identified 2026-07-25 10:52 UTC

   Current status: We've identified the source of the issue, and we're developing and implementing a fix to restore service. We'll provide another update within 2 hours. Customer experience: Customers hosted in the specified region may be unable to resume warehouses or may...

4. identified 2026-07-25 12:45 UTC

   Current status: We've identified that IP address exhaustion in the affected region is preventing new compute resources from being provisioned, and we're implementing additional network capacity to restore service. We'll provide another update within 2 hours. Customer experience:...

5. identified 2026-07-25 14:38 UTC

   Current status: We've identified that IP address exhaustion in the affected region is preventing new compute resources from being provisioned, and we're implementing additional network capacity to restore service. We'll provide another update within 2 hours. Customer experience:...

6. monitoring 2026-07-25 15:28 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 region may have been unable to resume warehouses or may...

7. resolved 2026-07-25 16:01 UTC

   Current status: We've confirmed that this issue has been resolved, and we have monitored the environment to confirm that the affected functionality is now working as expected. If you experience additional issues or have questions, please open a support case via Snowflake...

8. postmortem 2026-07-31 20:38 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/INC20000106](https://community.snowflake.com/s/article/INC20000106)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Virtual Warehouses

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-11 17:41 UTC

   Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 1 hour. Customer experience: Customers hosted in the specified regions may experience delays or intermittent failures when resuming or managing virtual warehouses. Existing...

2. monitoring 2026-07-11 18:37 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 have experienced delays or intermittent...

3. resolved 2026-07-11 19:36 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...

4. postmortem 2026-07-18 01:40 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/INC20000085](https://community.snowflake.com/s/article/INC20000085)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Applications, Security and Privacy Features

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-10 14:30 UTC

   Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 1 hour. Customer experience: Customers hosted in the specified regions may be unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. Users may...

2. identified 2026-07-10 15:13 UTC

   Current status: Our telemetry indicates the PrivateLink connectivity health has recovered on July 10, 2026, at approximately 14:33 UTC, mitigating the impact for a majority of customers. We're continuing to investigate to isolate and address the source of the issue. Customer...

3. monitoring 2026-07-10 15:58 UTC

   Current status: We've confirmed PrivateLink connectivity health has recovered, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified regions may have been unable to...

4. resolved 2026-07-10 16:28 UTC

   Current status: We've monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the...

5. postmortem 2026-07-18 01:03 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/INC20000082](https://community.snowflake.com/s/article/INC20000082)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Applications

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-06-30 22:34 UTC

   Current status: We're investigating an issue with Snowsight authentication. We are seeing recovery as of 22:03 UTC and are continuing to monitor. We'll provide an update within 60 minutes. Customer experience: Customers may be unable to access Snowsight or may experience being...

2. monitoring 2026-06-30 22:39 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. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified region may...

3. resolved 2026-06-30 23:34 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...

4. postmortem 2026-07-08 23:14 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/INC20000063](https://community.snowflake.com/s/article/INC20000063)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Databases, Tables, and Views, Virtual Warehouses, Data Loading and Unloading, Applications

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-06-24 15:38 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...

2. identified 2026-06-24 16:06 UTC

   Current status: We've identified the source of the issue, and we've implemented a fix to restore service. We're assessing the recovery of affected components and we'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may...

3. monitoring 2026-06-24 16:44 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 region may have been unable to access or use Snowflake...

4. resolved 2026-06-24 17:22 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...

5. postmortem 2026-07-02 17:01 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/inc20000052](https://community.snowflake.com/s/article/inc20000052)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Applications, Snowpark Container Services

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-23 17:01 UTC

   Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 1 hour. Customer experience: Customers hosted in the specified region may be unable to access or launch Streamlit apps or other services and features that rely on Snowpark...

2. investigating 2026-06-23 17:50 UTC

   Current status: We're continuing to investigate the issue affecting Snowpark Container Services to determine its source. We'll provide another update within 1 hour. Customer experience: Customers hosted in the specified region may be intermittently unable to access or launch...

3. investigating 2026-06-23 19:02 UTC

   Current status: We've narrowed our investigation and remained focused on identifying a mitigation to address the impact to Snowpark Container Services. We'll provide another update within 2 hours. Customer experience: Customers hosted in the specified region may be unable to...

4. investigating 2026-06-23 21:15 UTC

   Current status: We have narrowed the investigation to a request handling and authentication path for affected services. While the exact root cause is still under investigation, our teams have ruled out some earlier hypotheses and are actively evaluating potential mitigation...

5. identified 2026-06-23 23:20 UTC

   Current status: We've narrowed the issue to the request handling and authentication path for the affected services, and we're now applying and testing mitigation actions to restore service. We'll provide another update within 3 hours. Customer experience: Customers hosted in the...

6. identified 2026-06-24 02:20 UTC

   Current status: We've identified the issue and deployed a two-part mitigation to address it, which included adding resources to the affected infrastructure and reverting a change. Affected services are recovering, and we're working to confirm full restoration. We'll provide...

7. identified 2026-06-24 04:16 UTC

   Current status: We're continuing to validate recovery and address residual impact. We'll provide another update within 2 hours. Customer experience: Customers hosted in the specified region may be intermittently unable to access or launch Streamlit apps, or may experience issues...

8. monitoring 2026-06-24 06:01 UTC

   Current status: We restarted the affected infrastructure and confirmed it fully restored the remaining affected services. We'll continue to monitor the environment until we're confident all services are functioning properly. We'll provide another update within 1 hour. Customer...

9. resolved 2026-06-24 07:30 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...

10. postmortem 2026-07-02 21:59 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/INC20000047](https://community.snowflake.com/s/article/INC20000047)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Applications, Snowpark Container Services

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-23 01:05 UTC

   Current status: We're investigating an issue with Snowpark Container Services and Snowsight. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified region may be unable to access Snowpark Container Services, and may intermittently be...

2. monitoring 2026-06-23 01:43 UTC

   Current status: We identified and reverted a recent configuration change to resolve the impact. We'll continue to monitor the environment until we're confident all services are functioning properly. We'll provide another update within 60 minutes. Customer experience: Customers...

3. resolved 2026-06-23 02:35 UTC

   Current status: We've monitored the environment to confirm that reverting the configuration change restored service. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience:...

4. postmortem 2026-07-02 21:47 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/INC20000046](https://community.snowflake.com/s/article/INC20000046)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Databases, Tables, and Views, Data Loading and Unloading

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-06-22 20:35 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...

2. investigating 2026-06-22 20:41 UTC

   Current status: We're continuing to investigate the issue with Snowflake Data Cloud. We'll provide another 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....

3. investigating 2026-06-22 21:10 UTC

   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 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or...

4. investigating 2026-06-22 21:48 UTC

   Current status: We are continuing to investigate the underlying source of the issue. In parallel, we are working to improve processing efficiency in a portion of our service infrastructure as a potential mitigation for the increased downstream load affecting related services....

5. monitoring 2026-06-22 22:16 UTC

   Current status: We've completed actions to improve processing efficiency on the affected infrastructure and are seeing relief. We anticipate some customers may continue to experience latency as processing queues are resolved. We'll continue to monitor the environment until we're...

6. resolved 2026-06-23 00:26 UTC

   Current status: We've monitored the environment to confirm our actions have restored service. 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...

7. postmortem 2026-06-30 19:16 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/INC0159680](https://community.snowflake.com/s/article/INC0159680)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-16 10:29 UTC

   Current status: We've identified a recent release issue affecting Git repository functionality in Workspaces. We're rolling back the affected release across the environment and will provide another update within 60 minutes. Customer experience: Customers hosted in the specified...

2. identified 2026-06-16 11:29 UTC

   Current status: We've identified a recent release issue affecting Git repository functionality in Workspaces. The rollback of the affected release is proceeding as expected across the environment. We will provide another update within 60 minutes. Customer experience: Customers...

3. identified 2026-06-16 12:29 UTC

   Current status: We've identified a recent release issue affecting Git repository functionality in Workspaces. The rollback of the affected release is continuing and is approximately halfway completed. We will provide another update within two hours. Customer experience:...

4. identified 2026-06-16 14:36 UTC

   Current status: We're continuing to roll back a recent software release affecting Git repository functionality in Snowsight Workspaces. The rollback of the affected release is approximately 70% completed. We will provide another update within four hours. Customer experience:...

5. monitoring 2026-06-16 18:30 UTC

   Current status: We've implemented the fix for this issue. Any customers still encountering the error condition may need to refresh their browser session. We'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience:...

6. resolved 2026-06-16 20:20 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...

7. postmortem 2026-06-24 21:57 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/INC0159144](https://community.snowflake.com/s/article/INC0159144)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Applications

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-15 14:30 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.

2. identified 2026-06-15 15:13 UTC

   Current status: We've identified an issue affecting Snowsight backend infrastructure, and we're attempting to restart affected components to restore service. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be...

3. identified 2026-06-15 16:19 UTC

   Current status: Following our initial recovery actions, authentication and basic navigation have been restored for most customers; however, other core Snowsight features are continuing to experience failures or degraded performance. We have identified a network connectivity...

4. identified 2026-06-15 17:43 UTC

   Current status: We have implemented recovery actions and telemetry indicates that service health has currently returned to normal. However, we are continuing to coordinate with our cloud provider to address the underlying issue affecting backend infrastructure health that may...

5. monitoring 2026-06-15 19:22 UTC

   Current status: Services remain stable following our previously implemented mitigation actions; however, customers could experience performance issues until the underlying issue is resolved. We are closely monitoring the environment while we continue to collaborate with the...

6. monitoring 2026-06-15 21:55 UTC

   Current status: We are continuing to coordinate with our third-party cloud provider on addressing the underlying infrastructure issue while we closely monitor the environment. Service health has remained stable after implementing our previous mitigation actions; however,...

7. monitoring 2026-06-16 04:00 UTC

   Current status: Our third-party cloud platform has confirmed that the underlying infrastructure issue was resolved as of 21:45 UTC. Service health remains stable, and out of an abundance of caution, we will continue to actively monitor the environment before posting our final...

8. resolved 2026-06-16 21:15 UTC

   Current status: We've validated the fix for this issue with our third-party provider 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...

9. postmortem 2026-07-02 21:58 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/INC20000034](https://community.snowflake.com/s/article/INC20000034)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Developer Tools

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-12 18:21 UTC

   Current status: We're investigating an issue with stored procedures that use Snowpark External Access integrations. We'll provide an update within 1 hour. Customer experience: Customers hosted in the specified regions may see that stored procedures that use Snowpark External...

2. identified 2026-06-12 19:14 UTC

   Current status: Our investigation indicates the issue is related to a recent network configuration change affecting outbound connectivity for stored procedures that use Snowpark external access integrations. We are reverting the suspected change and manually correcting the...

3. monitoring 2026-06-12 19:53 UTC

   Current status: We've fully reverted the impacting network configuration change, and our telemetry indicates that service health is recovering. We'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers...

4. resolved 2026-06-12 20:57 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...

5. postmortem 2026-06-22 22:16 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/INC20000033](https://community.snowflake.com/s/article/INC20000033)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Applications

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-06-11 00:30 UTC

   Current status: We identified and reverted a misconfigured 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 or the Support page in Snowsight....

2. postmortem 2026-06-18 03:59 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/INC20000032](https://community.snowflake.com/s/article/INC20000032)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Applications

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-08 15:23 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.

2. monitoring 2026-06-08 15:42 UTC

   Current status: During our investigation, the service self-recovered. 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...

3. resolved 2026-06-08 16:40 UTC

   Current status: We've monitored the environment and confirmed 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...

4. postmortem 2026-06-16 02:07 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/INC20000030](https://community.snowflake.com/s/article/INC20000030)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Virtual Warehouses

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

Started during Azure: Multiple services – Power/cooling issues in West US 2.

1. investigating 2026-05-29 06:47 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 start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck...

2. identified 2026-05-29 07:45 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...

3. identified 2026-05-29 08:45 UTC

   Current status: We're seeing services recover as our third-party provider continues its efforts to restore its environment, and we're actively monitoring recovery as these actions progress. We'll provide another update within 60 minutes. Customer experience: Customers hosted in...

4. monitoring 2026-05-29 09:36 UTC

   Current status: We've coordinated with our third-party cloud platform to implement 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...

5. monitoring 2026-05-29 12:40 UTC

   Current status: Although the broadest impact has been remediated by our third-party cloud platform, customers may still experience performance latency or degradation as our service provider continues to work on full restoration. As an ETA from them is unavailable, our service...

6. resolved 2026-05-29 22:28 UTC

   Current status: Our third-party cloud platform has confirmed that the impact to their infrastructure has been mitigated, and we've observed that the impact to Snowflake customers has been resolved. If you experience additional issues or have questions, please open a support case...

7. postmortem 2026-06-12 09:38 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/INC0157956](https://community.snowflake.com/s/article/INC0157956)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: AI and ML, AI and ML, AI and ML, AI and ML

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-15 04:01 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 Cortex Code in Snowsight stopping mid-response after completing only one step of a...

2. monitoring 2026-05-15 04:34 UTC

   Current status: We've identified and rolled back a Cortex Code update to resolve this issue. 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...

3. resolved 2026-05-15 05:25 UTC

   Current status: We've monitored the environment and confirmed the rollback restored service. 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...

4. postmortem 2026-05-22 00:26 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/INC0157230](https://community.snowflake.com/s/article/INC0157230)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity, Business Continuity

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-13 23:08 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 failures when replicating data between accounts or regions.

2. investigating 2026-05-14 00:04 UTC

   Current status: We're continuing to investigate and troubleshoot 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 or failures when replicating data between...

3. resolved 2026-05-14 00:19 UTC

   Current status: After investigating, we've determined this to be a false positive. There were no customer replication refresh operations impacted. We've confirmed replication services are functioning normally. If you experience issues or have questions, please open a support...

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Organization and Account Management

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-05-05 04:12 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 region may observe stale or delayed data in account usage views and organization usage views. Usage reporting...

2. investigating 2026-05-05 05:10 UTC

   Current status: We've identified an issue affecting a subset of data files, which is resulting in a delay for account usage updates. We're working on identifying a mitigation to restore normal processing. We'll provide another update within two hours. Customer experience:...

3. investigating 2026-05-05 07:09 UTC

   Current status: We've identified an issue affecting a subset of data files, which is resulting in a delay for account usage updates. We are preparing changes to safely exclude the affected files and allow processing to resume. Account Usage data in the affected region remains...

4. identified 2026-05-05 09:27 UTC

   Current status: We've identified an issue affecting a subset of internal metering files, causing a delay in account usage updates. We have now completed changes to exclude those files, allowing processes to resume. Data freshness in this region is now improving as the processing...

5. monitoring 2026-05-05 11:30 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 region may have observed stale or delayed data in account...

6. resolved 2026-05-05 12:30 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...

7. postmortem 2026-05-13 00:16 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/INC0156645](https://community.snowflake.com/s/article/INC0156645)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Snowpark Container Services

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-04-29 03:23 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 experience errors or connectivity issues when using Snowpark Container Services. Openflow users...

2. investigating 2026-04-29 03:53 UTC

   Current status: We're continuing to investigate the issue with Snowflake Data Cloud. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may experience errors or connectivity issues when using Snowpark Container...

3. monitoring 2026-04-29 04:27 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 errors or connectivity issues when...

4. resolved 2026-04-29 04:44 UTC

   Current status: We identified a subset of infrastructure that was unhealthy. We restarted that infrastructure and monitored the environment to confirm that the service has been restored. If you experience additional issues or have questions, please open a support case via...

5. postmortem 2026-05-07 02:26 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/INC0156355](https://community.snowflake.com/s/article/INC0156355)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Applications

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. monitoring 2026-04-16 14:08 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 have been unable to access or use Snowflake...

2. resolved 2026-04-16 15:08 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...

3. postmortem 2026-04-23 22:12 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/INC0155608](https://community.snowflake.com/s/article/INC0155608)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Databases, Tables, and Views, Virtual Warehouses, Data Loading and Unloading, Applications

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-04-07 18:26 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...

2. identified 2026-04-07 19:13 UTC

   Current status: We've identified the source of the issue as a portion of the infrastructure which supports core Snowflake services operating below operational thresholds. We've taken the affected portion of infrastructure out of active rotation and confirmed that Snowflake...

3. monitoring 2026-04-07 20:08 UTC

   Current status: We've confirmed that our service has recovered following the routing of affected traffic to healthy infrastructure, and we're continuing to monitor as the health of Snowsight continues to improve. Other services are fully recovered, but some users who were...

4. resolved 2026-04-07 20:56 UTC

   Current status: We've rerouted Snowflake traffic to healthy infrastructure to address this issue, and we've monitored the environment to confirm that service has been restored. If you experience additional issues or have questions, please open a support case via Snowflake...

5. postmortem 2026-04-15 00:21 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/INC0155020](https://community.snowflake.com/s/article/INC0155020)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools, Developer Tools

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. identified 2026-03-27 18:34 UTC

   Current status: We've identified an issue affecting the visibility of Native Apps listings within Snowsight, and we're developing and implementing a fix to restore service. We'll provide another update within 12 hours. Customer experience: Customers are unable to see or manage...

2. identified 2026-03-28 05:30 UTC

   Current status: We've determined a recent Snowsight UI update introduced a code issue that prevented Native Apps from being visible on the "Apps" page of Snowsight. The fix has finished rolling out to all but one region at 03:51 UTC on March 28, 2026. The rollout's progression...

3. identified 2026-03-30 17:10 UTC

   Current status: We've implemented the fix for this issue across all regions except GCP - US East 4, where we're working to complete the rollout of the fix. We'll continue to monitor the environment and provide another update by 18:00 UTC on March 31, 2026. Customer experience:...

4. resolved 2026-03-30 21:38 UTC

   Current status: We've confirmed that the infrastructure issue delaying deployment of the fix to the GCP - US East 4 (N. Virginia) region was resolved, and we have monitored the environment to confirm that the affected functionality is now working as expected. If you experience...

5. postmortem 2026-04-06 18:28 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/INC0154408](https://community.snowflake.com/s/article/INC0154408)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Databases, Tables, and Views, Virtual Warehouses, Data Loading and Unloading, Applications, Snowpark Container Services, Security and Privacy Features, AI and ML, Organization and Account Management, Listings and Collaboration, Alerts and Notifications, Developer Tools, Business Continuity

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-03-21 06:02 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...

2. identified 2026-03-21 06:23 UTC

   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 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core...

3. monitoring 2026-03-21 06:38 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 have been unable to access or use multiple core...

4. resolved 2026-03-21 07:12 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...

5. postmortem 2026-03-27 23:14 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/INC0154019](https://community.snowflake.com/s/article/INC0154019)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Affected: Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-03-16 22:46 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 create or alter Snowflake alerts. Incident start time: 14:53 UTC March 14, 2026

2. identified 2026-03-16 23:45 UTC

   Current status: We've determined a recent improvement to Snowflake alerts creation and alteration contains a code issue, which is causing the impact. We've developed a fix and are rolling it out to restore service. We'll provide another update within 6 hours. Customer...

3. monitoring 2026-03-17 04:58 UTC

   Current status: We've finished rolling out the fix to restore service. 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 create or alter...

4. resolved 2026-03-17 05:49 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...

5. postmortem 2026-03-24 23:55 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/INC0153706](https://community.snowflake.com/s/article/INC0153706)

Excerpts are shortened. Read the full incident on Snowflake's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

Started during AWS: Multiple services (UAE): Region Availability.

1. investigating 2026-03-01 13:33 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...

2. identified 2026-03-01 14:07 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...

3. identified 2026-03-01 14:55 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...

4. identified 2026-03-01 18:18 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...

5. identified 2026-03-02 00:23 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...

6. identified 2026-03-02 06:24 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...

7. identified 2026-03-02 12:24 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...

8. identified 2026-03-02 18:17 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...

9. identified 2026-03-03 18:18 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...

10. identified 2026-03-04 06:02 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...

11. identified 2026-03-05 04:39 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...

12. resolved 2026-05-15 15:10 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...

Excerpts are shortened. Read the full incident on Snowflake's status page.