Looking for an update now? Check the current status, or follow Snowflake for future changes.
4.1%of 49 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
0%
30
30
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 14Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Current status: Since our last update, capacity availability and provisioning performance for virtual warehouses have materially improved. Additional capacity has become available in the region, and Snowflake has increased the resources reserved for customer workloads. We are continuing to monitor warehouse capacity and provisioning performance through periods of peak demand.
Snowpark Container Services remains subject to capacity constraints. We continue to preserve available resources, coordinate with our third-party cloud provider, and work on additional capacity options. We are not yet declaring the broader incident resolved because SPCS workloads that require new capacity may still be affected.
We will provide another update within 7 days, or sooner if there is a material change.
Customer experience: Customers using virtual warehouses should see improved availability when starting or resuming warehouses. Residual delays or intermittent failures may still occur while we validate the improvement under sustained demand. Customers with continued warehouse reliability issues should contact Snowflake Support for case-by-case assistance.
Customers using Snowpark Container Services may still encounter delays, timeouts, or failures when starting or resuming Notebooks, provisioning or resuming compute pools, or setting up OpenFlow runtimes. The remaining risk is concentrated in workloads that require new capacity; existing workloads continue to run normally.
ETA: We continue to expect additional compute resources to become available in the specified region by late October. Warehouse capacity is currently in an improved state, and we will continue monitoring before declaring the warehouse impact resolved. For Snowpark Container Services, the timing of meaningful customer impact improvement remains dependent on the availability of those resources and service readiness to use them. We will provide an updated ETA if the timeline changes.
Workaround: For virtual warehouses, we are no longer recommending a broad migration to Gen1 as a workaround for this incident. Customers who previously moved affected warehouses to Gen1 may work with Snowflake Support or their account team to evaluate returning to Gen2 based on current capacity, workload requirements, and observed reliability. Gen1 remains a possible short-term mitigation for customers who continue to experience verified Gen2 reliability issues, but performance and cost characteristics may differ.
Customers running warehouse-based Notebooks may continue to defer migration to Snowpark Container Services where feasible. There is currently no general workaround for Snowpark Container Services compute pool impact; customers experiencing specific failures should contact Snowflake Support.
Incident start time: 08:41 UTC August 09, 2026
Preliminary root cause: A third-party cloud platform is experiencing constrained compute capacity in the specified region, limiting the availability of compute resources for Snowpark Container Services and causing delays or failures when provisioning or resuming virtual warehouses.
identified
Current status: Since our last update, we have seen periods of improved provisioning performance while preserving available compute resources and coordinating closely with our third-party cloud provider. Resource availability remains constrained and variable, and provisioning delays or failures may still occur. The provider continues to project improved resource availability in the specified region by the end of October.
We will provide another update within 7 days, or sooner if there is a material change.
Customer experience: Customers in the specified region may still encounter delays, timeouts, or failures when running Snowpark Container Services workloads, including starting or resuming Notebooks, provisioning or resuming compute pools, and setting up OpenFlow runtimes.
Virtual Warehouses: Customers using second generation (Gen2) warehouses may experience delays or intermittent failures when starting or resuming their warehouses, which can extend query run times or delay completion of data pipelines. Warehouses that are already running are generally less affected.
ETA: Based on information from our third-party cloud platform provider, we currently expect additional compute resources to become available in the specified region by late October, although the benefit may vary by workload. We'll provide an updated ETA if that timeline changes.
Workaround: While we remain focused on reducing provisioning times and building on measures that have already shown improvement, we recommend the following actions, where feasible for affected customers.
-Delay migrating warehouse-based Notebooks to SPCS where possible.
-For customers experiencing Gen2 warehouse start or resume delays, and where appropriate for their workload, moving the affected warehouse to Gen1 may provide short-term relief. Gen1 warehouses are not affected by this capacity constraint, but Gen1 capacity is limited and performance characteristics may differ.
-Contact Snowflake Support for case-by-case assistance with SPCS compute-pool failures.
Incident start time: 08:41 UTC August 09, 2026
Preliminary root cause: A third-party cloud platform is experiencing constrained compute capacity in the specified region, limiting the availability of compute resources for Snowpark Container Services and causing delays or failures when provisioning or resuming virtual warehouses.
identified
Current status: We've received an update from our third-party cloud provider that improvement for resource availability in this region is now projected by the end of October. In the meantime, we’re continuing our efforts to reduce virtual warehouse provisioning times, building on measures that have already shown improvement. In parallel, we’re preserving available compute resources and continuing to closely coordinate with our third-party cloud provider on resource availability updates in the specified region. Resource availability continues to vary with demand, and provisioning delays or failures may still occur. We’ll provide another update within 7 days.
Customer experience: Over the past few weeks, we've seen periods of fewer failures as we continue working to preserve available compute resources. However, resource availability at our third-party cloud provider remains constrained. Customers in the specified region may still encounter failures, timeouts, or delays when running Snowpark Container Services workloads, including starting or resuming Notebooks and provisioning or resuming compute pools.
Creating additional workloads in new accounts adds to demand for these limited resources. Customers setting up Snowpark Container Services services or jobs, or Openflow runtimes, in those accounts may therefore encounter more frequent provisioning failures or be unable to complete setup.
Customers using second generation (Gen2) warehouses may also continue to experience delays or intermittent failures when starting or resuming their warehouses, which can extend query run times or delay completion of data pipelines.
ETA: Our third-party cloud platform provider remains committed to making additional compute resources available, which are now projected to be ready by late-October. We'll provide an updated ETA if that timeline changes.
Workaround: Customers running Notebooks on virtual warehouses can delay migrating to Snowpark Container Services until this issue is resolved.
Customers experiencing virtual warehouse resume delays can migrate affected warehouses to first generation (Gen1) using ALTER WAREHOUSE <warehouse_name> SET GENERATION = '1';. Gen1 warehouses are not affected by this capacity constraint. This is a short-term mitigation; Gen1 capacity is limited and performance characteristics may differ.
There are currently no general workarounds available for Snowpark Container Services compute pool impact. Customers with specific compute pool failures should contact Snowflake Support for case-by-case assistance.
Incident start time: 08:41 UTC August 09, 2026
Preliminary root cause: A third-party cloud platform experienced constrained compute capacity, causing limited availability of compute resources for Snowpark Container Services and delays or failures when provisioning or resuming virtual warehouses in the specified region.
identified
Current status: We've taken additional steps with our warehouse team to reduce provisioning latencies for virtual warehouses, and we've observed some improvement in provisioning latencies as a result. Resource availability remains variable and correlated to overall demand, with some intermittent delays occurring during high-volume times. We're continuing to work closely with our warehouse team to maintain available capacity and keep provisioning times low. Our third-party cloud platform provider has indicated that the additional compute capacity remains on track, and we're continuing to coordinate with them to restore the needed capacity. We'll provide another update within 7 days.
Customer experience: Customers hosted in the specified region may intermittently be unable to use Snowpark Container Services. Affected customers may experience failures, timeouts, or delays when running Snowpark Container Services workloads, such as starting or resuming Notebooks, or provisioning or resuming compute pools. Notebooks running on virtual warehouses are not affected.
Additionally, starting from 04:00 UTC September 04, 2026, customers hosted in the specified region with workloads on second generation (Gen2) warehouses may experience delays or intermittent failures when resuming or starting virtual warehouses. This may result in longer than expected query run times or delays in completing data pipelines. Warehouses that are already running are largely unaffected.
ETA: Based on information from our third-party cloud platform provider, we expect additional compute resources to become available in the specified region by mid-October. We'll provide an updated ETA as we receive more information.
Workaround: While we're focused on remediation, customers running Notebooks on virtual warehouses can delay migrating to Snowpark Container Services until this issue is resolved.
For customers experiencing impact to virtual warehouses, and who have already performed a failover, we recommend remaining in the alternate region until we have received additional capacity allocation from the third-party provider.
Customers who are continuing to experience impact to virtual warehouses may see additional relief by migrating workloads to first generation (Gen1) warehouses, which remain less impacted by this issue.
Incident start time: 08:41 UTC August 09, 2026
Preliminary root cause: A third-party cloud platform provider is experiencing constrained compute capacity, affecting compute resource provisioning, and causing limited availability of compute resources as well as delays and intermittent failures when resuming or starting virtual warehouses in the specified region.
identified
Current status: Our third-party cloud platform provider has informed us that they expect to be able to provide additional capacity allocation by mid-October. In the meantime, we are working to preserve compute resources available to us, reduce non-essential resource consumption, and investigate any alternative methods to further reduce impact. Resource availability remains variable and correlated to overall demand, with some intermittent delays occurring during high-volume times. We'll provide another update by 23:00 UTC September 17, 2026.
Customer experience: Customers hosted in the specified region may intermittently be unable to use Snowpark Container Services. Affected customers may experience failures, timeouts, or delays when running Snowpark Container Services workloads, such as starting or resuming Notebooks, or provisioning or resuming compute pools. Notebooks running on virtual warehouses are not affected.
Additionally, starting from 04:00 UTC September 04, 2026, customers hosted in the specified region with workloads on second generation (Gen2) warehouses may experience delays or intermittent failures when resuming or starting virtual warehouses. This may result in longer than expected query run times or delays in completing data pipelines. Warehouses that are already running are largely unaffected.
ETA: Based on information from our third-party cloud platform provider, we anticipate a solution in mid-October.
Workaround: While we're focused on remediation, customers running Notebooks on virtual warehouses can delay migrating to Snowpark Container Services until this issue is resolved.
For customers experiencing impact to virtual warehouses, and who have already performed a failover, we recommend remaining in the alternate region until we have received additional capacity allocation from the third-party provider.
Customers who are continuing to experience impact to virtual warehouses may see additional relief by migrating workloads to first generation (Gen1) warehouses, which remain less impacted by this issue.
Incident start time: 08:41 UTC August 09, 2026
Preliminary root cause: A third-party cloud platform provider is experiencing constrained compute capacity, affecting compute resource provisioning, and causing limited availability of compute resources as well as delays and intermittent failures when resuming or starting virtual warehouses in the specified region.
identified
Current status: We've made additional adjustments to further reduce non-essential resource consumption and preserve available compute resources in the specified region. We're continuing to develop a software update to enable additional compute resources, and our other mitigation actions remain in place. We're also continuing to coordinate with our third-party cloud platform provider to restore the compute capacity needed for Snowpark Container Services. We'll provide another update within 7 days.
Customer experience: Customers hosted in the specified region may intermittently be unable to use Snowpark Container Services. Affected customers may experience failures, timeouts, or delays when running Snowpark Container Services workloads, such as starting or resuming Notebooks, or provisioning or resuming compute pools. Notebooks running on virtual warehouses are not affected.
ETA: Based on information from our third-party cloud platform provider, we expect this capacity constraint to persist for several more months. We'll provide an updated ETA as we receive more information.
Workaround: While we're focused on remediation, customers running Notebooks on virtual warehouses can delay migrating to Snowpark Container Services until this issue is resolved.
Incident start time: 08:41 UTC August 09, 2026
Preliminary root cause: A third-party cloud platform experienced constrained compute capacity, which caused limited availability of compute resources in the specified region.
identified
Current status: We have taken additional steps to preserve available compute resources in the specified region, including adjusting compute pool scaling to reduce non-essential resource consumption. We continue to prioritize available resources for Business Critical Edition accounts, and non-essential maintenance operations in the specified region remain paused. The software update to enable additional compute resources for Snowpark Container Services in the specified region is in the testing and validation stage. We continue to be in contact with our third-party cloud platform, and we'll provide another update by 00:00 UTC September 8, 2026.
Customer experience: Customers hosted in the specified region may intermittently be unable to use Snowpark Container Services. Affected customers may experience failures, timeouts, or delays when running Snowpark Container Services workloads, such as starting or resuming Notebooks, or provisioning or resuming compute pools. Notebooks running on virtual warehouses are not affected.
ETA: An ETA is not yet available. We'll provide one as soon as possible.
Workaround: While we're focused on remediation, customers running Notebooks on virtual warehouses can delay migrating to Snowpark Container Services until this issue is resolved.
Incident start time: 08:41 UTC August 09, 2026
Preliminary root cause: A third-party cloud platform experienced constrained compute capacity, which caused limited availability of compute resources in the specified region.
identified
Current status: We're continuing to coordinate with our third-party cloud platform provider to restore the compute capacity needed for Snowpark Container Services in the specified region. In parallel, we are taking the following steps to mitigate impact:
- We have implemented capacity prioritization measures to help ensure available resources are directed to Business Critical tier accounts.
- We are working to expand the set of instance types available for compute pool provisioning through a software update, which is currently in an expedited release process.
- We have paused non-essential maintenance operations and internal workloads in the affected region to preserve available capacity.
While we are in continuous contact with the provider, we expect the provider efforts to continue into next week, as such, the next update will be on Monday August 31, end of business day.
Customer experience: Customers hosted in the specified region may intermittently be unable to use Snowpark Container Services. Affected customers may experience failures, timeouts, or delays when running Snowpark Container Services workloads, such as starting or resuming Notebooks, or provisioning or resuming compute pools. Notebooks running on virtual warehouses are not affected.
ETA: An ETA is not yet available. We'll provide one as soon as possible.
Workaround: While we're focused on remediation, customers running Notebooks on virtual warehouses can delay migrating to Snowpark Container Services until this issue is resolved.
Incident start time: 08:41 UTC August 09, 2026
Preliminary root cause: A third-party cloud platform experienced constrained compute capacity, which caused limited availability of compute resources in the specified region.
identified
Current status: We've determined that a capacity constraint at our third-party cloud platform has limited the availability of compute resources in the specified region. We're actively working to identify and implement alternative compute options to reduce impact for affected customers while our third-party cloud platform works to restore availability. We are in continuous contact with our third-party cloud platform, and we'll provide another update within 24 hours.
Customer experience: Customers hosted in the specified region may intermittently be unable to use Snowpark Container Services. Affected customers may experience failures or timeouts when running Snowpark Container Services workloads, such as starting or resuming Notebooks, or provisioning or resuming compute pools. Notebooks running on virtual warehouses are not affected.
ETA: An ETA is not yet available. We'll provide one as soon as possible.
Workaround: While we're focused on remediation, customers running Notebooks on virtual warehouses can delay migrating to Snowpark Container Services until this issue is resolved.
Incident start time: 08:41 UTC August 09, 2026
Preliminary root cause: A capacity constraint at our third-party cloud platform is limiting the availability of compute resources in the affected region.
Legacy Incident Archive
34 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
March 2026
AWS - US West (Oregon): INC0154019
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
<b>Current status:</b> We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly.
<b>Customer experience:</b> Customers hosted in the specified regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have beeen unable to sign in, execute queries, or manage data. Users would have encountered HTTP 404 or other similar errors.
<b>Incident start time:...
identified
<b>Current status:</b> We've identified the source of the issue, and we're developing and implementing a fix to restore service. We'll provide another update within 30 minutes.
<b>Customer experience:</b> 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.
<b>ETA:</b> An ETA is not yet available. We'll provide one as soon as possible.
<b>Incident sta...
investigating
<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 30 minutes.
<b>Customer experience:</b> 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.
<b>Incident start time:</b> 05:31 UTC March 21, 2026
INC0153706
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
<b>Current status:</b> 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.
<b>Customer experience:</b> Customers hosted in the specified regions may have been unable to create or alter Snowflake alerts.
<b>Incident start time:</b> 14:53 UTC March 14, 2026
<b>Incident end time:</b> 04:39 UTC March 17, 2026
<b>Preliminary root cause:</b> A recent improvement to Snowflake alerts creation ...
identified
<b>Current status:</b> 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.
<b>Customer experience:</b> Customers hosted in the specified regions may be unable to create or alter Snowflake alerts.
<b>ETA:</b> Our current estimate is that service will be restored for all affected customers within 6 hours...
investigating
<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes.
<b>Customer experience:</b> Customers hosted in the specified regions may be unable to create or alter Snowflake alerts.
<b>Incident start time:</b> 14:53 UTC March 14, 2026
INC0153465
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
<b>Current status:</b> 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.
<b>Customer experience:</b> 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 se...
identified
<b>Current status:</b> 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.
<b>Customer experience:</b> 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 S...
identified
<b>Current status:</b> 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.
<b>Customer experience:</b> Customers hosted in the specified regions may be unable to use Snowflake Intelligence services and features. Additi...
AWS - Middle East (UAE): INC0152681
criticalSource not attested
Last archived state: resolved
View archived record details
identified
<b>Current status:</b> We continue to actively monitor the situation, and our cloud service provider affirms that meaningful progress is being made toward recovery, with several distinct services showing sustained improvement. While focused efforts continue toward full-service restoration for the region, the cloud service providers' initial advice to migrate your workloads and traffic to alternate Region(s) remains in place. We are in continuous contact with the provider and will post our nex...
identified
<b>Current status:</b> We continue to actively monitor the situation as we work with our cloud service provider to restore service following a power outage at a primary data center. Recovery efforts remain focused on foundational services, and multiple paths to restoration continue to be pursued. Work to restore the underlying infrastructure needed for full restoration is still in progress. Additionally, we've been informed that our cloud service provider will supplement their public service ...
identified
<b>Current status:</b> We're closely monitoring as coordination with our cloud service provider continues in an effort to restore service following the impacting power outage at a primary data center. They are prioritizing recovery for foundational services and pursuing multiple mitigation paths that do not depend on the underlying facilities being fully brought back online to provide some relief. However, full restoration will require that the underlying infrastructure be fully repaired, and...
identified
<b>Current status:</b> We're continuing to coordinate with our cloud service provider as they troubleshoot the impacting power outage at a primary data center. Elevated connectivity issues and error rates within the region will continue until the power issue has been resolved. While they're working to fully restore power and stabilize the environment, they now expect that this may take a day or more. We will provide our next update within 24 hours.
<b>Customer experience:</b> Customers hoste...
identified
<b>Current status:</b> We continue to coordinate with our cloud provider following a power outage at a primary data center. Although we had observed early indicators of recovery, the provider has confirmed additional, ongoing impact that continues to cause elevated connectivity issues and error rates within the region. They continue to actively work on full restoration and environment stability but this is expected to take several hours. We will provide our next update within 6 hours.
<b>Cus...
identified
<b>Current status:</b> We continue to coordinate with our cloud provider following a power outage at a primary data center. While we have observed consistent signs of recovery in several key services, the provider is currently investigating a localized connectivity issues and elevated error rates within the region. Full restoration is expected to take several hours as they work to safely stabilize the environment. We will provide our next update within 6 hours.
<b>Customer experience:</b> Cu...
identified
<b>Current status:</b> We continue to coordinate closely with our cloud provider as they work to resolve a major service disruption caused by a power outage at a primary data center. While we are seeing initial signs of recovery across several services, the provider expects full restoration to take multiple hours as they safely stabilize the environment. We'll provide another update within 6 hours.
<b>Customer experience:</b> Customers hosted in the specified regions may be unable to access ...
identified
<b>Current status:</b> We're continuing to coordinate with our third-party cloud platform to develop and implement a fix to restore service. The provider has confirmed that the issue is due to a power disruption, and they expect full recovery to take multiple hours to complete. We'll provide another update within 6 hours.
<b>Customer experience:</b> Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be un...
identified
<b>Current status:</b> We're continuing to coordinate with our third-party cloud platform to develop and implement a fix to restore service. We'll provide another update within 4 hours.
<b>Customer experience:</b> 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.
<b>ETA:</b> The third-party platform has advised that it may take multiple hours to res...
identified
<b>Current status:</b> 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.
<b>Customer experience:</b> 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.
<b>ETA:</b> An ETA is not yet available. We'll pr...
investigating
<b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 30 minutes.
<b>Customer experience:</b> 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.
