Snowflake Outage History

Started Jul 30, 2026, 03:00 AM UTC· resolved Jul 30, 2026, 04:56 AM UTC

1. investigating Jul 30, 2026, 03:00 AM 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 request with IP/Token is not allowed to access Snowflake" errors when attempting to access Snowsight via private endpoints.

2. identified Jul 30, 2026, 03:30 AM 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 users may encounter HTTP 404 errors or "Incoming request with IP/Token is not allowed to access Snowflake" errors when attempting to access Snowsight via private endpoints. ETA: Our current estimate is that service will be restored within 1 hour. Workaround: There are currently no available workarounds for this issue.

3. monitoring Jul 30, 2026, 04:17 AM 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 have been unable to log in to Snowsight. Affected users may have encountered HTTP 404 errors or "Incoming request with IP/Token is not allowed to access Snowflake" errors when attempting to access Snowsight via private endpoints. Workaround: There were no available workarounds for this issue. Incident start time: 00:18 UTC July 30, 2026 Incident end time: 03:52 UTC July 30, 2026 Preliminary root cause: A recent configuration change to a subset of the routing infrastructure caused connectivity failures for customers accessing Snowsight via private endpoints.

4. resolved Jul 30, 2026, 04:56 AM 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 experience: Customers hosted in the specified regions may have been unable to log in to Snowsight. Affected users may have encountered HTTP 404 errors or "Incoming request with IP/Token is not allowed to access Snowflake" errors when attempting to access Snowsight via private endpoints. Workaround: There were no available workarounds for this issue. Incident start time: 00:18 UTC July 30, 2026 Incident end time: 03:52 UTC July 30, 2026 Preliminary root cause: A recent configuration change to a subset of the routing infrastructure caused connectivity failures for customers accessing Snowsight via private endpoints. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

5. postmortem Aug 10, 2026, 04:31 AM UTC

   Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC20000115](https://community.snowflake.com/s/article/INC20000115)

Read the full incident report →

Started Jul 25, 2026, 09:05 AM UTC· resolved Jul 25, 2026, 04:01 PM UTC

1. investigating Jul 25, 2026, 09:05 AM 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 Snowflake features are not impacted. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Workaround: There are currently no available workarounds for this issue. Incident start time: 07:45 UTC July 25, 2026

2. identified Jul 25, 2026, 09:57 AM 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 when accessing or using Snowflake services and features. This may include slower query execution, intermittent availability, or limited feature functionality. ETA: We're working with a third-party cloud platform to increase capacity limits. An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 07:45 UTC July 25, 2026 Preliminary root cause: Unexpected demand exceeded available capacity in the affected region, causing the third-party cloud platform to throttle provisioning requests.

3. identified Jul 25, 2026, 10:52 AM 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 experience delays with serverless tasks and other workloads that require compute resources. Queries may queue instead of executing immediately. ETA: We're working with a third-party cloud platform to remove throttling limits. An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 07:45 UTC July 25, 2026 Preliminary root cause: Unexpected demand exceeded available capacity in the affected region, causing the third-party cloud platform to throttle provisioning requests.

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

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

6. monitoring Jul 25, 2026, 03:28 PM UTC

   Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified region may have been unable to resume warehouses or may have experienced significant delays with serverless tasks and other workloads that required compute resources. Queries may have queued for extended periods instead of executing immediately, with some customers experiencing delays of several hours. Workaround: There were no available workarounds for this issue. Incident start time: 07:45 UTC July 25, 2026 Incident end time: 15:05 UTC July 25, 2026 Preliminary root cause: Unexpected demand from a large-scale workload exceeded available network capacity in the affected region, causing resource exhaustion that prevented new compute resources from being provisioned.

7. resolved Jul 25, 2026, 04:01 PM 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 Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified region may have been unable to resume warehouses or may have experienced significant delays with serverless tasks and other workloads that required compute resources. Queries may have queued for extended periods instead of executing immediately, with some customers experiencing delays of several hours. Workaround: There were no available workarounds for this issue. Incident start time: 07:45 UTC July 25, 2026 Incident end time: 15:05 UTC July 25, 2026 Preliminary root cause: Unexpected demand from a large-scale workload exceeded available network capacity in the affected region, causing resource exhaustion that prevented new compute resources from being provisioned. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

8. postmortem Jul 31, 2026, 08:38 PM UTC

   Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC20000106](https://community.snowflake.com/s/article/INC20000106)

Read the full incident report →

Started Jul 11, 2026, 05:41 PM UTC· resolved Jul 11, 2026, 07:36 PM UTC

1. investigating Jul 11, 2026, 05:41 PM 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 warehouses that are already running may be unaffected. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 16:30 UTC July 11, 2026

2. monitoring Jul 11, 2026, 06:37 PM UTC

   Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified regions may have experienced delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that were already running may have been unaffected. Incident start time: 16:35 UTC July 11, 2026 Incident end time: 18:10 UTC July 11, 2026 Preliminary root cause: Resource exhaustion in the binary download service caused delays when virtual warehouses attempted to download required software components during startup.

3. resolved Jul 11, 2026, 07:36 PM UTC

   Current status: We've implemented the fix for this issue and monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified regions may have experienced delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that were already running may have been unaffected. Incident start time: 16:35 UTC July 11, 2026 Incident end time: 18:10 UTC July 11, 2026 Preliminary root cause: Resource exhaustion in the binary download service caused delays when virtual warehouses attempted to download required software components during startup. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

4. postmortem Jul 18, 2026, 01:40 AM UTC

   Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC20000085](https://community.snowflake.com/s/article/INC20000085)

Read the full incident report →

Started Jul 10, 2026, 02:30 PM UTC· resolved Jul 10, 2026, 04:28 PM UTC

1. investigating Jul 10, 2026, 02:30 PM 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 encounter connection errors or timeouts. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. This may require DNS configuration changes for PrivateLink functionality.

2. identified Jul 10, 2026, 03:13 PM 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 experience: Customers hosted in the specified regions may be unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. Users may encounter connection errors or timeouts. ETA: An ETA is not yet available. We'll provide one as soon as possible. Incident start time: 13:26 UTC July 10, 2026

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

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

5. postmortem Jul 18, 2026, 01:03 AM UTC

   Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC20000082](https://community.snowflake.com/s/article/INC20000082)

Read the full incident report →

Started Jun 30, 2026, 10:34 PM UTC· resolved Jun 30, 2026, 11:34 PM UTC

1. identified Jun 30, 2026, 10:34 PM 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 logged out unexpectedly. All other Snowflake features are not impacted. ETA: We have taken action to address the issue and expect it to be resolved as of 22:03 UTC. Incident start time: 21:47 UTC June 30, 2026

2. monitoring Jun 30, 2026, 10:39 PM UTC

   Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified region may have been unable to access Snowsight or may have experienced being logged out unexpectedly. All other Snowflake features were not impacted. Workaround: While we were focused on remediation, customers who were logged out needed to log back in to Snowsight. Incident start time: 21:47 UTC June 30, 2026 Incident end time: 23:03 UTC June 30, 2026 Preliminary root cause: A routine system configuration change caused authentication issues with Snowsight. Once identified, the configuration was reverted.

3. resolved Jun 30, 2026, 11:34 PM UTC

   Current status: We've implemented the fix for this issue and monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified region may have been unable to access Snowsight or may have experienced being logged out unexpectedly. All other Snowflake features were not impacted. Workaround: While we were focused on remediation, customers who were logged out needed to log back in to Snowsight. Incident start time: 21:47 UTC June 30, 2026 Incident end time: 23:03 UTC June 30, 2026 Preliminary root cause: A routine system configuration change caused authentication issues with Snowsight. Once identified, the configuration was reverted. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

4. postmortem Jul 08, 2026, 11:14 PM UTC

   Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC20000063](https://community.snowflake.com/s/article/INC20000063)

Read the full incident report →

Started Jun 24, 2026, 03:38 PM UTC· resolved Jun 24, 2026, 05:22 PM UTC

1. identified Jun 24, 2026, 03:38 PM UTC

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

2. identified Jun 24, 2026, 04:06 PM 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 have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data. Following initial recovery actions, sign in functionality has been restored, but customers may observe some increased latency or performance issues until service has fully recovered. ETA: Our current estimate is that service is recovering and will be fully restored within the next 30 minutes. Incident start time: 15:10 UTC June 24, 2026

3. monitoring Jun 24, 2026, 04:44 PM UTC

   Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified region may have been unable to access or use Snowflake services and features using Snowsight. A subset of affected users in the region may also have been unable to execute queries, manage data, or may have experienced increased latency or performance issues with database operations. Incident start time: 15:10 UTC June 24, 2026 Incident end time: 15:50 UTC June 24, 2026 Preliminary root cause: A configuration issue caused an unexpected increase in load on our metadata database layer, resulting in cascading impact to dependent services like Snowsight and database operations.

4. resolved Jun 24, 2026, 05:22 PM UTC

   Current status: We've implemented the fix for this issue and monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified region may have been unable to access or use Snowflake services and features using Snowsight. A subset of affected users in the region may also have been unable to execute queries, manage data, or may have experienced increased latency or performance issues with database operations. Incident start time: 15:10 UTC June 24, 2026 Incident end time: 15:50 UTC June 24, 2026 Preliminary root cause: A configuration issue caused an unexpected increase in load on our metadata database layer, resulting in cascading impact to dependent services like Snowsight and database operations. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

5. postmortem Jul 02, 2026, 05:01 PM UTC

   Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/inc20000052](https://community.snowflake.com/s/article/inc20000052)

Read the full incident report →

Started Jun 23, 2026, 05:01 PM UTC· resolved Jun 24, 2026, 07:30 AM UTC

1. investigating Jun 23, 2026, 05:01 PM 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 Container Services. Incident start time: 15:20 UTC June 23, 2026

2. investigating Jun 23, 2026, 05:50 PM 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 Streamlit apps or may experience issues with other services and features that rely on Snowpark Container Services. Incident start time: 15:20 UTC June 23, 2026

3. investigating Jun 23, 2026, 07:02 PM 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 access or launch Streamlit apps or may experience connection timeouts and receive a "Connection error" when interacting with other services and features that rely on Snowpark Container Services. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 15:20 UTC June 23, 2026

4. investigating Jun 23, 2026, 09:15 PM 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 actions. 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 with other services and features that rely on Snowpark Container Services, such as Notebooks. Users may experience connection timeouts and receive a "Connection error" when interacting with affected services. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 15:20 UTC June 23, 2026

5. identified Jun 23, 2026, 11:20 PM 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 specified region may be intermittently unable to access or launch Streamlit apps, or may experience issues with other services and features that rely on Snowpark Container Services, such as Notebooks. Users may experience connection timeouts and receive a "Connection error" when interacting with affected services. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 15:20 UTC June 23, 2026

6. identified Jun 24, 2026, 02:20 AM 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 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 with other services and features that rely on Snowpark Container Services, such as Notebooks. Users may experience connection timeouts and receive a "Connection error" when interacting with affected services. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 15:20 UTC June 23, 2026

7. identified Jun 24, 2026, 04:16 AM 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 with other services and features that rely on Snowpark Container Services, such as Notebooks. Users may experience connection timeouts and receive a "Connection error" when interacting with affected services. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 15:20 UTC June 23, 2026

8. monitoring Jun 24, 2026, 06:01 AM 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 experience: Customers hosted in the specified region may have been intermittently unable to access or launch Streamlit apps, or may have experienced issues with other services and features that rely on Snowpark Container Services, such as Notebooks. Users may have experienced connection timeouts and received a "Connection error" when interacting with affected services. Workaround: There were no available workarounds for this issue. Incident start time: 15:20 UTC June 23, 2026 Incident end time: 05:10 UTC June 24, 2026 Preliminary root cause: A subset of infrastructure responsible for processing service requests experienced degraded performance, which prevented requests from completing and caused connectivity failures for services that rely on Snowpark Container Services.

9. resolved Jun 24, 2026, 07:30 AM UTC

   Current status: We've implemented the fix for this issue and monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified region may have been intermittently unable to access or launch Streamlit apps, or may have experienced issues with other services and features that rely on Snowpark Container Services, such as Notebooks. Users may have experienced connection timeouts and received a "Connection error" when interacting with affected services. Workaround: There were no available workarounds for this issue. Incident start time: 15:20 UTC June 23, 2026 Incident end time: 05:10 UTC June 24, 2026 Preliminary root cause: A subset of infrastructure responsible for processing service requests experienced degraded performance, which prevented requests from completing and caused connectivity failures for services that rely on Snowpark Container Services. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

10. postmortem Jul 02, 2026, 09:59 PM UTC

    Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC20000047](https://community.snowflake.com/s/article/INC20000047)

Read the full incident report →

Started Jun 23, 2026, 01:05 AM UTC· resolved Jun 23, 2026, 02:35 AM UTC

1. investigating Jun 23, 2026, 01:05 AM 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 unable to sign in to Snowsight. Affected user may see HTTP 500 errors. Incident start time: 22:38 UTC June 22, 2026

2. monitoring Jun 23, 2026, 01:43 AM 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 hosted in the specified region may have been unable to access Snowpark Container Services, and may have intermittently been unable to sign in to Snowsight. Affected users may have seen HTTP 500 errors. Workaround: There were no available workarounds for this issue. Incident start time: 22:38 UTC June 22, 2026 Incident end time: 01:28 UTC June 23, 2026 Preliminary root cause: A recent configuration change affected DNS resolution in the affected region, which caused connectivity failures for Snowpark Container Services and Snowsight.

3. resolved Jun 23, 2026, 02:35 AM 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: Customers hosted in the specified region may have been unable to access Snowpark Container Services, and may have intermittently been unable to sign in to Snowsight. Affected users may have seen HTTP 500 errors. Workaround: There were no available workarounds for this issue. Incident start time: 22:38 UTC June 22, 2026 Incident end time: 01:28 UTC June 23, 2026 Preliminary root cause: A recent system configuration change affected DNS resolution in the region, which caused connectivity failures for Snowpark Container Services and Snowsight. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

4. postmortem Jul 02, 2026, 09:47 PM UTC

   Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC20000046](https://community.snowflake.com/s/article/INC20000046)

Read the full incident report →

Started Jun 22, 2026, 08:35 PM UTC· resolved Jun 23, 2026, 12:26 AM UTC

1. investigating Jun 22, 2026, 08:35 PM UTC

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

2. investigating Jun 22, 2026, 08:41 PM 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. Affected users may be unable to sign in, execute queries, or manage data. Users may may experience delays or failures when using Snowpipe to ingest files.

3. investigating Jun 22, 2026, 09:10 PM 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 use multiple core Snowflake services and features. Affected users may be unable to execute queries and tasks, or manage data. Users may may experience delays or failures when using Snowpipe to ingest files. Affected users may see a SQL execution internal error: Processing aborted due to error. Incident start time: 20:12 UTC June 22, 2026

4. investigating Jun 22, 2026, 09:48 PM 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. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to execute queries and tasks, or manage data. Users may experience delays or failures with replication or when using Snowpipe to ingest files. Affected users may see a SQL execution internal error: Processing aborted due to error. Workaround: There are currently no available workarounds for this issue. An ETA is not yet available. We'll provide one as soon as possible. Incident start time: 20:12 UTC June 22, 2026

5. monitoring Jun 22, 2026, 10:16 PM UTC

   Current status: We've completed actions to improve processing efficiency on the affected infrastructure and are seeing relief. We anticipate some customer may continue to experience latency as processing queues are resolved. We'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to execute queries and tasks, or manage data. Users may have experienced delays or failures with replication or when using Snowpipe to ingest files. Affected users may have seen a SQL execution internal error: Processing aborted due to error. Incident start time: 20:12 UTC June 22, 2026 Incident end time: 21:45 UTC June 22, 2026 Preliminary root cause: Elevated load in a critical internal coordination service affected request processing for a subset of workloads. The underlying cause of the issue remains under investigation.

6. resolved Jun 23, 2026, 12:26 AM 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 specified regions may have been unable to access or use multiple core Snowflake services and features, and may have experienced delays or failures with replication or when using Snowpipe to ingest files. Affected users may have been unable to execute queries and tasks or manage data, and may have seen a "Processing aborted due to error" SQL execution internal error. Incident start time: 20:12 UTC June 22, 2026 Incident end time: 21:45 UTC June 22, 2026 Preliminary root cause: Elevated load in a critical internal coordination service affected request processing for a subset of workloads. The underlying cause of the issue remains under investigation. A root cause analysis (RCA) document will be published within five business days.

7. postmortem Jun 30, 2026, 07:16 PM UTC

   Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC0159680](https://community.snowflake.com/s/article/INC0159680)

Read the full incident report →

Started Jun 16, 2026, 10:29 AM UTC· resolved Jun 16, 2026, 08:20 PM UTC

1. investigating Jun 16, 2026, 10:29 AM 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 regions may be unable to use Git repository functionality in Workspaces, including pulling changes from a connected Git repository and performing related Git operations in a Git-synced workspace. Affected customers may see an error message: "Workspace feature disabled: Internal only system function." Workaround: While we're focused on remediation, please open a support case if you need immediate restoration of this functionality so we can apply a temporary account-level configuration change. Incident start time: 00:03 UTC June 16, 2026

2. identified Jun 16, 2026, 11:29 AM 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 hosted in the specified regions may be unable to use Git repository functionality in Workspaces, including pulling changes from a connected Git repository and performing related Git operations in a Git-synced workspace. Affected customers may see an error message: "Workspace feature disabled: Internal only system function." ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: While we're focused on remediation, please open a support case if you need immediate restoration of this functionality so we can apply a temporary account-level configuration change. Incident start time: 00:03 UTC June 16, 2026

3. identified Jun 16, 2026, 12:29 PM 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: Customers hosted in the specified regions may be unable to use Git repository functionality in Workspaces, including pulling changes from a connected Git repository and performing related Git operations in a Git-synced workspace. Affected customers may see an error message: "Workspace feature disabled: Internal only system function." ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: While we're focused on remediation, please open a support case if you need immediate restoration of this functionality so we can apply a temporary account-level configuration change. Incident start time: 00:03 UTC June 16, 2026

4. identified Jun 16, 2026, 02:36 PM 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: Customers hosted in the specified regions may be unable to use Git repository functionality in Workspaces, including pulling changes from a connected Git repository and performing related Git operations in a Git-synced workspace. Affected customers may see an error message: "Workspace feature disabled: Internal only system function." ETA: Based on current progress, we expect the rollback to complete within the next four hours. Workaround: While we're focused on remediation, please open a support case if you need immediate restoration of this functionality so we can apply a temporary account-level configuration change. Incident start time: 00:03 UTC June 16, 2026

5. monitoring Jun 16, 2026, 06:30 PM 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: Customers hosted in the specified regions may have been unable to use Git repository functionality in Workspaces, including pulling changes from a connected Git repository and performing related Git operations in a Git-synced workspace. Affected customers may have seen an error message: "Workspace feature disabled: Internal only system function." Incident start time: 00:03 UTC June 16, 2026 Incident end time: 17:29 UTC June 16, 2026 Preliminary root cause: A recent Snowsight Workspaces software update changed how certain Workspace Git operations were routed and classified. Due to a code issue, some customer Git repository actions were tagged with an incorrect internal classification, causing those operations to fail.

6. resolved Jun 16, 2026, 08:20 PM UTC

   Current status: We've implemented the fix for this issue and monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified regions may have been unable to use Git repository functionality in Workspaces, including pulling changes from a connected Git repository and performing related Git operations in a Git-synced workspace. Affected customers may have seen an error message: "Workspace feature disabled: Internal only system function." Incident start time: 00:03 UTC June 16, 2026 Incident end time: 17:29 UTC June 16, 2026 Preliminary root cause: A recent Snowsight Workspaces software update changed how certain Workspace Git operations were routed and classified. Due to a code issue, some customer Git repository actions were tagged with an incorrect internal classification, causing those operations to fail. A root cause analysis (RCA) document will be published within five business days.

7. postmortem Jun 24, 2026, 09:57 PM UTC

   Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC0159144](https://community.snowflake.com/s/article/INC0159144)

Read the full incident report →

Started Jun 15, 2026, 02:30 PM UTC· resolved Jun 16, 2026, 09:15 PM UTC

1. investigating Jun 15, 2026, 02:30 PM UTC

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

2. identified Jun 15, 2026, 03:13 PM 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 unable to access or use Snowflake services and features using Snowsight. Customers may see "something went wrong" or "no healthy upstream" error messages. Some customers may be able to access Snowsight but are unable to perform operations within the UI. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Workaround: There are currently no available workarounds for this issue. Incident start time: 14:15 UTC June 15, 2026

3. identified Jun 15, 2026, 04:19 PM 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 issue affecting infrastructure components used by Snowsight's backend infrastructure, and we are attempting to recover the affected components. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. Customers may see "something went wrong" or "no healthy upstream" error messages. Some customers may be able to access Snowsight but are unable to perform operations within the UI. Recovery may be inconsistent as different parts of Snowsight are restored. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: While we're focused on remediation, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 14:15 UTC June 15, 2026

4. identified Jun 15, 2026, 05:43 PM 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 result in periods of intermittent performance impact. We are actively monitoring health and network connectivity of the affected components and will provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. Customers may see "something went wrong" or "no healthy upstream" error messages. Some customers may be able to access Snowsight but are unable to perform operations within the UI. Recovery may be inconsistent as different parts of Snowsight are restored. ETA: Service is currently healthy; however an ETA for confirming resolution of the underlying infrastructure issue is not yet available. We’ll provide one as soon as possible. For affected customers using replication that have initiated their failover procedures, we don’t currently recommend failback to the region until after we have finished validating recovery. Incident start time: 14:15 UTC June 15, 2026

5. monitoring Jun 15, 2026, 07:22 PM 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 third-party cloud provider to ensure the underlying infrastructure remains healthy. We'll provide another update in the next 2 hours. Customer experience: Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. The most significant periods of impact for most customers were between 14:05-14:35 UTC and 16:27-16:46, during which customers could not authenticate or access Snowsight. After initial recovery actions, customers were able to access Snowsight but were unable to perform operations within the UI or experienced significant performance issues. Customers may have seen "something went wrong" or "no healthy upstream" error messages. ETA: Service is currently healthy; however an ETA for confirming resolution of the underlying infrastructure issue is not yet available. We’ll provide one as soon as possible. For affected customers using replication that have initiated their failover procedures, we don’t currently recommend failback to the region until after we have finished validating recovery. Incident start time: 14:15 UTC June 15, 2026 Incident end time: 17:05 UTC June 15, 2026 Preliminary root cause: Backend infrastructure that supports authentication to the Snowsight service experienced a degradation due to a third-party cloud platform infrastructure issue. This triggered a cascade of connectivity issues in backend components supporting the Snowsight platform, resulting in service disruptions and intermittent access problems.

6. monitoring Jun 15, 2026, 09:55 PM 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, customers may continue to experience intermittent periods of degraded service performance until the issue is fully resolved. We'll provide another update in the next 4 hours. Customer experience: Customers hosted in the specified regions may experience short periods of intermittent impact to Snowflake services and features using Snowsight. The most significant periods of impact for most customers were between 14:05-14:35 UTC and 16:27-16:46, during which customers could not authenticate or access Snowsight. After initial recovery actions, customers were able to access Snowsight but were unable to perform operations within the UI or experienced significant performance issues. Customers may have seen "something went wrong" or "no healthy upstream" error messages. ETA: Service is currently healthy; however an ETA for confirming resolution of the underlying infrastructure issue is not yet available. We’ll provide one as soon as possible. For affected customers using replication that have initiated their failover procedures, we don’t currently recommend failback to the region until after we have finished validating recovery. Incident start time: 14:15 UTC June 15, 2026 Incident end time: 17:05 UTC June 15, 2026 Preliminary root cause: Backend infrastructure that supports authentication to the Snowsight service experienced a degradation due to a third-party cloud platform infrastructure issue. This triggered a cascade of connectivity issues in backend components supporting the Snowsight platform, resulting in service disruptions and intermittent access problems.

7. monitoring Jun 16, 2026, 04:00 AM 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 update. We'll provide another update within 18 hours. Customer experience: Customers hosted in the specified region may have been unable to access or use Snowflake services and features using Snowsight, or may have experienced short periods of intermittent impact. The most significant periods of impact for most customers were between 14:05-14:35 and 16:27-16:46 UTC, during which customers could not authenticate or access Snowsight. After initial recovery actions, customers were able to access Snowsight but were unable to perform operations within the UI or experienced significant performance issues. Customers may have seen "something went wrong" or "no healthy upstream" error messages. ETA: Service is currently healthy and the underlying infrastructure issue has been resolved; however, we're continuing to validate recovery. For affected customers using replication that have initiated their failover procedures, we don't currently recommend failback to the region until after we have finished validating recovery. Incident start time: 14:15 UTC June 15, 2026 Incident end time: 21:45 UTC June 15, 2026 Preliminary root cause: Backend infrastructure that supports authentication to the Snowsight service experienced a degradation due to a third-party cloud platform infrastructure issue. This triggered a cascade of connectivity issues in backend components supporting the Snowsight platform, resulting in service disruptions and intermittent access problems.

8. resolved Jun 16, 2026, 09:15 PM 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 in Snowsight. Customer experience: Customers hosted in the specified region may have been unable to access or use Snowflake services and features using Snowsight. The most significant periods of impact for most customers were between 14:05-14:35 and 16:27-16:46 UTC, during which customers could not authenticate or access Snowsight. After initial recovery actions, customers were able to access Snowsight but may have been unable to perform operations within the UI or experienced intermittent periods of significant performance issues. Customers may have seen "something went wrong" or "no healthy upstream" error messages. Incident start time: 14:15 UTC June 15, 2026 Incident end time: 21:45 UTC June 15, 2026 Preliminary root cause: Backend infrastructure that supports authentication to the Snowsight service experienced a degradation due to a third-party cloud platform infrastructure issue. This triggered a cascade of connectivity issues in backend components supporting the Snowsight platform, resulting in service disruptions and intermittent access problems. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 10 business days.

9. postmortem Jul 02, 2026, 09:58 PM UTC

   Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC20000034](https://community.snowflake.com/s/article/INC20000034)

Read the full incident report →

Started Jun 12, 2026, 06:21 PM UTC· resolved Jun 12, 2026, 08:57 PM UTC

1. investigating Jun 12, 2026, 06:21 PM 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 Access integrations may fail with the following SQL execution internal error: 300010:4004234085. Incident start time: 15:10 UTC June 12, 2026

2. identified Jun 12, 2026, 07:14 PM 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 affected network configuration to restore service as quickly as possible. 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 access integrations may fail with the following SQL execution internal error: 300010:4004234085. ETA: Our current estimate is that service will be restored within 1 hour. Incident start time: 15:10 UTC June 12, 2026

3. monitoring Jun 12, 2026, 07:53 PM 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 hosted in the specified regions may have seen that stored procedures that use Snowpark external access integrations failed with the following SQL execution internal error: 300010:4004234085. Incident start time: 15:10 UTC June 12, 2026 Incident end time: 19:15 UTC June 12, 2026 Preliminary root cause: A misconfiguration introduced by a recent network configuration change affecting outbound connectivity for stored procedures that use Snowpark external access integrations resulted in impact.

4. resolved Jun 12, 2026, 08:57 PM UTC

   Current status: We've implemented the fix for this issue and monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified regions may have seen that stored procedures that use Snowpark external access integrations failed with the following SQL execution internal error: 300010:4004234085. Incident start time: 15:10 UTC June 12, 2026 Incident end time: 19:15 UTC June 12, 2026 Preliminary root cause: A misconfiguration introduced by a recent network configuration change affecting outbound connectivity for stored procedures that use Snowpark external access integrations resulted in impact. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

5. postmortem Jun 22, 2026, 10:16 PM UTC

   Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC20000033](https://community.snowflake.com/s/article/INC20000033)

Read the full incident report →

Started Jun 11, 2026, 12:30 AM UTC· resolved Jun 11, 2026, 11:58 PM UTC

1. resolved Jun 11, 2026, 12:30 AM UTC

   Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified region may be unable to access Snowsight or sign in to the Snowflake web interface. Customers using Snowflake Openflow, Snowpark Container Services, or Cortex AI services — including Cortex LLM functions, Agents, Analyst, and Search — may encounter errors or failures when using these services. Workaround: There were no available workarounds for this issue. Incident start time: 23:23 UTC June 10, 2026 Incident end time: 23:58 UTC June 10, 2026 Preliminary root cause: A routine system configuration change intended to unblock a cluster upgrade caused connectivity issues with Snowpark Container Services. Once identified, the configuration was reverted.

2. postmortem Jun 18, 2026, 03:59 AM UTC

   Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC20000032](https://community.snowflake.com/s/article/INC20000032)

Read the full incident report →

Started Jun 08, 2026, 03:23 PM UTC· resolved Jun 08, 2026, 04:40 PM UTC

1. investigating Jun 08, 2026, 03:23 PM UTC

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

2. monitoring Jun 08, 2026, 03:42 PM 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 Snowflake services and features using Snowsight. Customers may have experienced page not found errors or general login failures. Workaround: There are currently no available workarounds for this issue. Incident start time: 14:58 UTC June 08, 2026

3. resolved Jun 08, 2026, 04:40 PM 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 specified regions may have been unable to access or use Snowflake services and features using Snowsight. Customers may have experienced page not found errors or general login failures. Incident start time: 14:58 UTC June 08, 2026 Incident end time: 15:20 UTC June 08, 2026 Preliminary root cause: An internal system degradation occurred within backend database infrastructure that supports Snowsight in the affected region, causing Snowsight request failures. The issue was detected by system health monitoring, and automated recovery systems performed scaling and targeted infrastructure restart operations that helped to restore service. We’re continuing to investigate to confirm the underlying root cause details and the contributing factors. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

4. postmortem Jun 16, 2026, 02:07 AM UTC

   Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC20000030](https://community.snowflake.com/s/article/INC20000030)

Read the full incident report →

Started May 29, 2026, 06:47 AM UTC· resolved May 29, 2026, 10:28 PM UTC

1. investigating May 29, 2026, 06:47 AM UTC

   Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that are already running may be unaffected. Incident start time: 05:15 UTC May 29, 2026

2. identified May 29, 2026, 07:45 AM UTC

   Current status: We've identified an issue with a third-party cloud platform, and we're coordinating with the provider to develop and implement a fix to restore service. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that are already running may be unaffected. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 05:15 UTC May 29, 2026

3. identified May 29, 2026, 08:45 AM 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 the specified regions may be unable to start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that are already running may be unaffected. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 05:15 UTC May 29, 2026

4. monitoring May 29, 2026, 09:36 AM 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 may be unable to start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that are already running may be unaffected. Incident start time: 05:15 UTC May 29, 2026 Incident end time: 07:24 UTC May 29, 2026 Preliminary root cause: A third-party cloud platform experienced a power outage in its data center, affecting the underlying infrastructure and causing increased latency and intermittent connectivity for some resources Snowflake depends on.

5. monitoring May 29, 2026, 12:40 PM 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 provider has advised these customers to enact failover to other regions where possible. We will 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 start, resume, or manage virtual warehouses. Virtual warehouses may have appeared stuck in the associated state. At this time, there should be no further impact on virtual warehouses. Incident start time: 05:15 UTC May 29, 2026 Incident end time: 07:24 UTC May 29, 2026 Preliminary root cause: A third-party cloud platform experienced a power outage in its data center, affecting the underlying infrastructure and causing increased latency and intermittent connectivity for some resources Snowflake depends on.

6. resolved May 29, 2026, 10:28 PM 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 via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified regions may have been unable to start, resume, or manage virtual warehouses. Virtual warehouses may have appeared to be stuck in the associated state. The majority of the impact occurred during the period of 05:15 UTC to 07:24 UTC on May 29, 2026. Incident start time: 04:24 UTC May 29, 2026 Incident end time: 07:24 UTC May 29, 2026 Preliminary root cause: A third-party cloud platform experienced a power outage in its data center, which affected the underlying infrastructure and caused increased latency and intermittent connectivity for some resources on which Snowflake depends. A root cause analysis (RCA) document will be published within ten business days.

7. postmortem Jun 12, 2026, 09:38 AM UTC

   Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC0157956](https://community.snowflake.com/s/article/INC0157956)

Read the full incident report →

Started May 15, 2026, 04:01 AM UTC· resolved May 15, 2026, 05:25 AM UTC

1. investigating May 15, 2026, 04:01 AM UTC

   Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may experience Cortex Code in Snowsight stopping mid-response after completing only one step of a request. The response may stop without an error message or may repeat without progressing.

2. monitoring May 15, 2026, 04:34 AM 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 Cortex Code in Snowsight stopping mid-response after completing only one step of a request. The response may have stopped without an error message or may have repeated without progressing. Incident start time: 22:50 UTC May 14, 2026 Incident end time: 04:05 UTC May 15, 2026 Preliminary root cause: A recent update to Cortex Code introduced a code issue that caused Cortex Code in Snowsight to incorrectly halt responses, preventing requests from completing.

3. resolved May 15, 2026, 05:25 AM 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 specified regions may have experienced Cortex Code in Snowsight stopping mid-response after completing only one step of a request. The response may have stopped without an error message or may have repeated without progressing. Incident start time: 22:50 UTC May 14, 2026 Incident end time: 04:05 UTC May 15, 2026 Preliminary root cause: A recent update to Cortex Code introduced a code issue that caused Cortex Code in Snowsight to incorrectly halt responses, preventing requests from completing. A root cause analysis (RCA) document will be published within five business days.

4. postmortem May 22, 2026, 12:26 AM UTC

   Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC0157230](https://community.snowflake.com/s/article/INC0157230)

Read the full incident report →

Started May 13, 2026, 11:08 PM UTC· resolved May 14, 2026, 12:19 AM UTC

1. investigating May 13, 2026, 11:08 PM UTC

   Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may experience delays or failures when replicating data between accounts or regions.

2. investigating May 14, 2026, 12:04 AM 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 accounts or regions. Incident start time: 21:13 UTC May 13, 2026

3. resolved May 14, 2026, 12:19 AM UTC

   Current status: After investigating, we've determined the issue is limited to internal Snowflake systems and did not affect customer replication operations. We've confirmed replication services are functioning normally. If you experience issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight.

Read the full incident report →

Started May 05, 2026, 04:12 AM UTC· resolved May 05, 2026, 12:30 PM UTC

1. investigating May 05, 2026, 04:12 AM UTC

   Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to create, manage, or update organizations, accounts, or users in Snowflake. Incident start time: 16:50 UTC May 04, 2026

2. investigating May 05, 2026, 05:10 AM 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: Customers hosted in the specified region may observe stale or delayed data in account usage views. Usage reporting may not reflect activity after 16:00 UTC on May 4, 2026. Workaround: There are currently no available workarounds for this issue. Incident start time: 16:50 UTC May 04, 2026

3. investigating May 05, 2026, 07:09 AM 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 delayed while we finalize validation of the impacted files and complete recovery steps. Customer experience: Customers hosted in the specified region may observe stale or delayed data in account usage views and organization usage views. Usage reporting may not reflect activity after 16:00 UTC on May 4, 2026. Workaround: There are currently no available workarounds for this issue. Incident start time: 12:03 UTC May 04, 2026

4. identified May 05, 2026, 09:27 AM 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 backfill catches up. We are validating the remaining backlog and any required backfill before marking full recovery. We'll provide another update within two hours. Customer experience: Customers hosted in the specified region may observe stale or delayed data in account usage views and organization usage views. Usage reporting may not reflect activity after 16:00 UTC on May 4, 2026. ETA: Our current estimate is that service will be restored within 2 hours. Workaround: There are currently no available workarounds for this issue. Incident start time: 12:03 UTC May 04, 2026 Incident end time: 08:54 UTC May 05, 2026

5. monitoring May 05, 2026, 11:30 AM UTC

   Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified region may have observed stale or delayed data in account usage views and organization usage views. Incident start time: 12:03 UTC May 04, 2026 Incident end time: 08:54 UTC May 05, 2026 Preliminary root cause: We identified an issue affecting a small number of internal metering files in this region. When Snowflake attempted to read these files as part of metering and account usage processing, the reads failed, blocking downstream processing.

6. resolved May 05, 2026, 12:30 PM UTC

   Current status: We've implemented the fix for this issue and monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified region may have observed stale or delayed data in account usage views and organization usage views. Incident start time: 12:03 UTC May 04, 2026 Incident end time: 08:54 UTC May 05, 2026 Preliminary root cause: We identified an issue affecting a small number of internal metering files in this region. When Snowflake attempted to read these files as part of metering and account usage processing, the reads failed, blocking downstream processing. A root cause analysis (RCA) document will be published within five business days.

7. postmortem May 13, 2026, 12:16 AM UTC

   Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC0156645](https://community.snowflake.com/s/article/INC0156645)

Read the full incident report →

Started Apr 29, 2026, 03:23 AM UTC· resolved Apr 29, 2026, 04:44 AM UTC

1. investigating Apr 29, 2026, 03:23 AM 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 Snowflake Openflow. Incident start time: 02:05 UTC April 29, 2026

2. investigating Apr 29, 2026, 03:53 AM 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 Snowflake Openflow. Incident start time: 02:05 UTC April 29, 2026

3. monitoring Apr 29, 2026, 04:27 AM UTC

   Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified regions may experience errors or connectivity issues when using Snowpark Container Services. Openflow users may be unable to access their runtimes, and Openflow Connectors may fail to pull data from sources or push data to Snowflake. Incident start time: 02:05 UTC April 29, 2026 Incident end time: 04:11 UTC April 29, 2026 Preliminary root cause: An internal component responsible for processing DNS requests in the affected region became unhealthy, which caused service connectivity failures for Snowpark Container Services and Openflow.

4. resolved Apr 29, 2026, 04:44 AM 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 Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified regions may experience errors or connectivity issues when using Snowpark Container Services. Openflow users may be unable to access their runtimes, and Openflow Connectors may fail to pull data from sources or push data to Snowflake. Incident start time: 02:05 UTC April 29, 2026 Incident end time: 04:11 UTC April 29, 2026 Preliminary root cause: A subset of infrastructure that processes DNS requests in the affected region became unhealthy, which caused service connectivity failures for Snowpark Container Services and Openflow. A root cause analysis (RCA) document will be published within five business days.

5. postmortem May 07, 2026, 02:26 AM UTC

   Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC0156355](https://community.snowflake.com/s/article/INC0156355)

Read the full incident report →

Started Apr 16, 2026, 02:08 PM UTC· resolved Apr 16, 2026, 03:08 PM UTC

1. monitoring Apr 16, 2026, 02:08 PM UTC

   Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. Incident start time: 12:25 UTC April 16, 2026 Incident end time: 13:45 UTC April 16, 2026 Preliminary root cause: Some application instances entered a degraded state and were unable to handle downstream connections. Snowflake mitigated the issue by restarting the affected instances.

2. resolved Apr 16, 2026, 03:08 PM UTC

   Current status: We've implemented the fix for this issue and monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. Incident start time: 12:25 UTC April 16, 2026 Incident end time: 13:45 UTC April 16, 2026 Preliminary root cause: Some application instances entered a degraded state and were unable to handle downstream connections. Snowflake mitigated the issue by restarting the affected instances. A root cause analysis (RCA) document will be published within five business days.

3. postmortem Apr 23, 2026, 10:12 PM UTC

   Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC0155608](https://community.snowflake.com/s/article/INC0155608)

Read the full incident report →

Started Apr 07, 2026, 06:26 PM UTC· resolved Apr 07, 2026, 08:56 PM UTC

1. investigating Apr 07, 2026, 06:26 PM UTC

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

2. identified Apr 07, 2026, 07:13 PM 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 traffic is being routed to healthy infrastructure. Affected users may experience delayed query history. While the majority of impact appears to have subsided, we're working to confirm that impact to Snowsight specifically is recovering as well. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features, and may experience latency when using Snowsight. Affected users may be unable to sign in, execute queries, or manage data. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 17:47 UTC April 07, 2026

3. monitoring Apr 07, 2026, 08:08 PM 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 affected during the period of impact may temporarily experience delayed or incomplete query history. Customer experience: Customers hosted in the specified regions may have been unable to access or use multiple core Snowflake services and features, and may have experienced latency when using Snowsight. Affected users may have been unable to sign in, execute queries, or manage data. Incident start time: 17:47 UTC April 07, 2026 Incident end time: 19:45 UTC April 07, 2026 Preliminary root cause: A portion of the infrastructure that supports core Snowflake services was operating below operational thresholds, which resulted in impact.

4. resolved Apr 07, 2026, 08:56 PM 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 Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. A subset of affected customers were also unable to use other core Snowflake services and features, such as executing queries or tasks. Incident start time: 17:47 UTC April 07, 2026 Incident end time: 19:45 UTC April 07, 2026 Preliminary root cause: A subset of our metadata database infrastructure in this region became degraded, which impacted the overall availability of the service for affected customers. Concurrently, Snowsight infrastructure experienced a period of increased latency and failures, which correlated specifically to Snowsight availability issues in the region. A root cause analysis (RCA) document will be published within five business days.

5. postmortem Apr 15, 2026, 12:21 AM UTC

   Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC0155020](https://community.snowflake.com/s/article/INC0155020)

Read the full incident report →

Started Mar 27, 2026, 06:34 PM UTC· resolved Mar 30, 2026, 09:38 PM UTC

1. identified Mar 27, 2026, 06:34 PM 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 their Native Apps within the "Apps" page of the Snowsight UI. App execution and all other Snowflake features are not impacted. ETA: Our current estimate is that service will be restored within 12 hours. Workaround: While we're focused on remediation, please use SQL commands (e.g., SHOW APPLICATIONS) or search for apps using the Catalog > Database Explorer page to view and manage Native Apps. Incident start time: 00:00 UTC March 27, 2026

2. identified Mar 28, 2026, 05:30 AM 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 is temporarily stalled in the remaining GCP - US East 4 (N. Virginia) region due to an infrastructure issue that we're investigating. Once that underlying infrastructure issue is mitigated, the fix will finish rolling out in that final region. We'll provide another update at 18:00 UTC on March 30, 2026. Customer experience: Customers may be unable to see or manage their Native Apps within the "Apps" page of the Snowsight UI. App execution and all other Snowflake features are not impacted. ETA: Service has been restored in all but one region. An ETA is not yet available for the remaining GCP - US East 4 (N. Virginia) region; we'll provide one as soon as possible. In the meantime, we recommend affected users in that region use the suggested workaround. Workaround: While we're focused on remediation, please use SQL commands (e.g., SHOW APPLICATIONS) or search for apps using the Catalog > Database Explorer page to view and manage Native Apps. Incident start time: 00:00 UTC March 27, 2026

3. identified Mar 30, 2026, 05:10 PM 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: Customers may be unable to see or manage their Native Apps within the "Apps" page of the Snowsight UI. App execution and all other Snowflake features are not impacted. ETA: The affected functionality has been restored in all but one region. An ETA is not yet available for the remaining GCP - US East 4 (N. Virginia) region; we'll provide one as soon as possible. In the meantime, we recommend affected users in that region use the suggested workaround. Workaround: While we're focused on remediation, please use SQL commands (e.g., SHOW APPLICATIONS) or search for apps using the Catalog > Database Explorer page to view and manage Native Apps. Incident start time: 00:00 UTC March 27, 2026

4. resolved Mar 30, 2026, 09:38 PM 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 additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers may have been unable to see or manage their Native Apps within the "Apps" page of the Snowsight UI. App execution and all other Snowflake features were not impacted. SQL commands (e.g., SHOW APPLICATIONS) or searching for apps using the Catalog > Database Explorer page could still be used to view and manage Native Apps. Incident start time: 00:00 UTC March 27, 2026 Incident end time: 05:55 UTC March 29, 2026 Preliminary root cause: A recent Snowsight release introduced a code issue that caused an error to occur when attempting to load application metadata within the Apps page. This prevented the page from rendering the list of installed applications as expected. A root cause analysis (RCA) document will be published within five business days.

5. postmortem Apr 06, 2026, 06:28 PM UTC

   Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC0154408](https://community.snowflake.com/s/article/INC0154408)

Read the full incident report →

Started Mar 21, 2026, 06:02 AM UTC· resolved Mar 21, 2026, 07:12 AM UTC

1. investigating Mar 21, 2026, 06:02 AM UTC

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

2. identified Mar 21, 2026, 06:23 AM 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 Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: An ETA is not yet available. We'll provide one as soon as possible. Incident start time: 05:31 UTC March 21, 2026

3. monitoring Mar 21, 2026, 06:38 AM UTC

   Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data. Users would have encountered HTTP 404 or other similar errors. Incident start time: 05:27 UTC March 21, 2026 Incident end time: 06:18 UTC March 21, 2026 Preliminary root cause: The investigation determined that infrastructure responsible for high-level traffic routing and name resolution became degraded, which caused customers to encounter HTTP 404 errors when attempting to access or use certain Snowflake services.

4. resolved Mar 21, 2026, 07:12 AM UTC

   Current status: We've implemented the fix for this issue and monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data. Users would have encountered HTTP 404 or other similar errors. Incident start time: 05:27 UTC March 21, 2026 Incident end time: 06:18 UTC March 21, 2026 Preliminary root cause: The investigation determined that infrastructure responsible for high-level traffic routing and name resolution became degraded, which caused customers to encounter HTTP 404 errors when attempting to access or use certain Snowflake services. A root cause analysis (RCA) document will be published within five business days.

5. postmortem Mar 27, 2026, 11:14 PM UTC

   Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC0154019](https://community.snowflake.com/s/article/INC0154019)

Read the full incident report →

Started Mar 16, 2026, 10:46 PM UTC· resolved Mar 17, 2026, 05:49 AM UTC

1. investigating Mar 16, 2026, 10:46 PM UTC

   Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to create or alter Snowflake alerts. Incident start time: 14:53 UTC March 14, 2026

2. identified Mar 16, 2026, 11:45 PM 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 experience: Customers hosted in the specified regions may be unable to create or alter Snowflake alerts. ETA: Our current estimate is that service will be restored for all affected customers within 6 hours. Customers will see relief as the fix rolls out. In the meantime, affected customers using replication in an unaffected region may initiate their failover procedures as a way to bypass the issue. Workaround: There are currently no available workarounds for this issue. Incident start time: 14:53 UTC March 14, 2026

3. monitoring Mar 17, 2026, 04:58 AM 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 Snowflake alerts. Incident start time: 14:53 UTC March 14, 2026 Incident end time: 04:39 UTC March 17, 2026 Preliminary root cause: A recent improvement to Snowflake alerts creation and alteration contained a code issue.

4. resolved Mar 17, 2026, 05:49 AM UTC

   Current status: We've implemented the fix for this issue and monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified regions may have been unable to create or alter Snowflake alerts. Incident start time: 14:53 UTC March 14, 2026 Incident end time: 04:39 UTC March 17, 2026 Preliminary root cause: A recent improvement to Snowflake alerts creation and alteration contained a code issue. A root cause analysis (RCA) document will be published within five business days.

5. postmortem Mar 24, 2026, 11:55 PM UTC

   Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC0153706](https://community.snowflake.com/s/article/INC0153706)

Read the full incident report →

Started Mar 12, 2026, 07:42 PM UTC· resolved Mar 12, 2026, 11:13 PM UTC

1. identified Mar 12, 2026, 07:42 PM UTC

   Current status: We're aware of an issue affecting the Snowflake Data Cloud, and we've identified the source as a recent Snowflake Intelligence update. We're rolling back the change to restore service. Customers should experience relief as the rollback progresses across the affected infrastructure. We'll provide another update within 2 hours. Customer experience: Customers hosted in the specified regions may be unable to use Snowflake Intelligence services and features. Additionally, users may experience issues with expired sessions attempting to access Snowflake Intelligence. Existing sessions should be unaffected. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: While we're focused on remediation, please access the service or content using the AI.Snowflake.com URL through a private browser tab.

2. identified Mar 12, 2026, 08:18 PM UTC

   Current status: We're continuing to monitor as the rollback of the Snowflake Intelligence update progresses. Affected customers should continue to experience relief as the rollback advances and reaches their environment. We'll provide another update within 4 hours. Customer experience: Customers hosted in the specified regions may be unable to use Snowflake Intelligence services and features. Additionally, users may experience issues with expired sessions attempting to access Snowflake Intelligence. Existing sessions should be unaffected. ETA: Our current estimate is that service will be restored within approximately 4 hours. We're continuing to monitor the rollback's progress to ensure this timeline remains accurate. Workaround: While we're focused on remediation, users may be able to work around the issue by accessing the service directly via the non-account-specific URL, AI.Snowflake.com, in a private browser tab.

3. monitoring Mar 12, 2026, 09:50 PM UTC

   Current status: We've confirmed that the rollback of the impacting Snowflake Intelligence update has completed, 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 use Snowflake Intelligence services and features. Additionally, users may have experienced issues with expired sessions attempting to access Snowflake Intelligence. Existing sessions should have been unaffected. Workaround: While we were focused on remediation, users may have been able to work around the issue by accessing the service directly via the non-account-specific URL, AI.Snowflake.com, in a private browser tab. Incident start time: 16:30 UTC March 12, 2026 Incident end time: 20:39 UTC March 12, 2026 Preliminary root cause: An update intended to optimize Snowflake Intelligence introduced a code issue that caused problems with expired sessions attempting to access Snowflake Intelligence.

4. resolved Mar 12, 2026, 11:13 PM UTC

   Current status: We've confirmed that the rollback of the impacting Snowflake Intelligence update has completed, 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 use Snowflake Intelligence services and features. Additionally, users may have experienced issues with expired sessions attempting to access Snowflake Intelligence. Existing sessions should have been unaffected. Workaround: While we were focused on remediation, users may have been able to work around the issue by accessing the service directly via the non-account-specific URL, AI.Snowflake.com, in a private browser tab. Incident start time: 16:30 UTC March 12, 2026 Incident end time: 20:39 UTC March 12, 2026 Preliminary root cause: An update intended to optimize Snowflake Intelligence introduced a code issue that caused problems with expired sessions attempting to access Snowflake Intelligence.

5. postmortem Mar 19, 2026, 09:24 PM UTC

   Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC0153465](https://community.snowflake.com/s/article/INC0153465)

Read the full incident report →