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.
July 2026
INC20000106
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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 experienci...
identified
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 extende...
identified
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 extende...
identified
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...
identified
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 incr...
investigating
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 procedure...
INC20000085
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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
Prelimi...
investigating
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 fail...
INC20000082
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
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 Sn...
identified
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 ...
investigating
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 proced...
June 2026
INC20000063
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
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 ...
identified
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
INC20000052
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
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 oper...
identified
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...
identified
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.
INC20000047
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
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 Contain...
identified
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: A...
identified
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 ...
identified
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 exper...
investigating
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 ser...
investigating
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 ...
investigating
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
investigating
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
INC20000046
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
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: The...
investigating
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 users may see HTTP 500 errors.
Incident start time: 22:38 UTC June 22, 2026
AWS - US West (Oregon): INC0159680
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
<b>Current status:</b> We've completed actions to improve processing efficiency on the affected infrastructure and are seeing relief. We anticipate some customers may continue to experience latency as processing queues are resolved. We'll continue to monitor the environment until we're 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. Affe...
investigating
<b>Current status:</b> 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.
<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 execute queries and tasks, or ma...
investigating
<b>Current status:</b> 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.
<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 execute queries and tasks, or manage data. Users may may experience delays or failures when using Snowpipe to ingest files...
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 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.
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.
INC0159144
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
<b>Current status:</b> 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.
<b>Customer experience:</b> 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 opera...
identified
<b>Current status:</b> 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.
<b>Customer experience:</b> 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 ...
identified
<b>Current status:</b> 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.
<b>Customer experience:</b> 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...
identified
<b>Current status:</b> 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.
<b>Customer experience:</b> 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-sy...
investigating
<b>Current status:</b> 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.
<b>Customer experience:</b> 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. Affecte...
INC20000034
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
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 expe...
monitoring
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 spec...
monitoring
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 ...
identified
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: Custome...
identified
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: Customer...
identified
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 ...
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.
