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.
June 2026
INC20000033
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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...
identified
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 Snowpa...
investigating
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
INC20000030
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
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 tim...
investigating
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.
May 2026
Azure - West US 2 (Washington): INC0157956
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
<b>Current status:</b> 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.
<b>Customer experie...
monitoring
<b>Current status:</b> 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.
<b>Customer experience:</b> 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.
<b>Incident st...
identified
<b>Current status:</b> 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.
<b>Customer experience:</b> 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 una...
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 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.
<b>ETA:</b>...
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 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.
<b>Incident start time:</b> 05:15 UTC May 29, 2026
INC0157230
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
<b>Current status:</b> 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.
<b>Customer experience:</b> 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.
<b>Incident ...
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 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.
INC0157155
majorSource not attested
Last archived state: resolved
View archived record details
investigating
<b>Current status:</b> We're continuing to investigate and troubleshoot to determine the source of the issue. We'll provide another update within 60 minutes.
<b>Customer experience:</b> Customers hosted in the specified regions may experience delays or failures when replicating data between accounts or regions.
<b>Incident start time:</b> 21:13 UTC May 13, 2026
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 experience delays or failures when replicating data between accounts or regions.
Azure - West US 2 (Washington): INC0156645
minorSource 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 region may have observed stale or delayed data in account usage views and organization usage views.
<b>Incident start time:</b> 12:03 UTC May 04, 2026
<b>Incident end time:</b> 08:54 UTC May 05, 2026
<b>Preliminary root cause:</b> We identified an issue affec...
identified
<b>Current status:</b> 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.
<b>Customer experience:</b> Customers hosted ...
investigating
<b>Current status:</b> 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. We’ll provide another update within four hours.
<b>Customer experience:</b> Customers hosted in the specified region may o...
investigating
<b>Current status:</b> 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.
<b>Customer experience:</b> 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.
<b>Work...
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 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.
<b>Workaround:</b> There are currently no available workarounds for this issue.
<b>Incident start time:</b> 16:50 UTC May 04, 2026
April 2026
Azure - UK South (London): INC0156355
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 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.
<b>Incident start time:</b>...
investigating
<b>Current status:</b> We're continuing to investigate the issue with Snowflake Data Cloud. We'll provide another update within 30 minutes.
<b>Customer experience:</b> Customers hosted in the specified regions may experience errors or connectivity issues when using Snowflake Openflow.
<b>Incident start time:</b> 02:05 UTC April 29, 2026
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 experience errors or connectivity issues when using Snowflake Openflow.
<b>Incident start time:</b> 02:05 UTC April 29, 2026
GCP - US Central 1 (Iowa): INC0155608
majorSource 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 Snowflake services and features using Snowsight.
<b>Incident start time:</b> 12:25 UTC April 16, 2026
<b>Incident end time:</b> 13:45 UTC April 16, 2026
<b>Preliminary root cause:</b> Some application instances ent...
Azure - East US 2 (Virginia): INC0155020
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
<b>Current status:</b> 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.
<b>Customer experience:</b> Customers hosted in the specified regions may have been unable to access or use multip...
identified
<b>Current status:</b> 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 specifi...
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 access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data.
March 2026
INC0154408
majorSource not attested
Last archived state: resolved
View archived record details
identified
<b>Current status:</b> 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.
<b>Customer experience:</b> 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.
<b>ETA:</b> The affected functional...
identified
<b>Current status:</b> 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 ro...
identified
<b>Current status:</b> 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.
<b>Customer experience:</b> 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.
<b>ETA:</b> Our current estimate is that service will be restored within 12 ...
