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.
August 2026
INC20000175
criticalSource not attested
Last archived state: resolved
View archived record details
Databases, Tables, and ViewsApplications
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 30 minutes.
Customer experience: Customers hosted in the specified region may have been unable to access Snowflake services due to infrastructure connectivity issues. All other Snowflake features in other regions were not impacted.
Workaround: There were no available workarounds for this issue...
investigating
Current status: We're investigating an issue with Snowflake Data Cloud in the Southeast Asia region. We'll provide an update within 30 minutes.
Customer experience: Customers hosted in the Southeast Asia region may be unable to access Snowflake services due to infrastructure connectivity issues. All other Snowflake features in other regions 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 r...
INC20000173
majorSource not attested
Last archived state: resolved
View archived record details
Applications
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 remain logged in to Snowsight, experiencing immediate logout after successful authentication.
Workaround: There were no available workarounds for this issue.
Incident start time: 14:47 UTC August 24, 2026
Incident end time: 17:21 UTC August 24...
identified
Current status: We're in the process of implementing a fix for this issue. We'll provide an update within the next 60 minutes.
Customer experience: Customers hosted in the specified region may be unable to remain logged in to Snowsight, experiencing immediate logout after successful authentication.
An ETA is not yet available. We'll provide one as soon as possible.
Workaround: There are no available workarounds for this issue.
Incident start time: 15:00 UTC August 24, 2026
identified
Current status: We've identified an issue with a system configuration that is causing authentication problems in Snowsight, and we're developing and implementing a fix to restore service. We'll provide an update within 30 minutes.
Customer experience: Customers hosted in the specified region may be unable to remain logged in to Snowsight, experiencing immediate logout after successful authentication.
ETA: An ETA is not yet available. We'll provide one as soon as possible.
Workaround: There...
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 access or use Snowflake services and features using Snowsight.
Workaround: There are currently no available workarounds for this issue.
Incident start time: 15:00 UTC August 24, 2026
INC20000168
majorSource not attested
Last archived state: resolved
View archived record details
Security and Privacy Features
monitoring
Current status: We've coordinated with our third-party cloud platform, which has implemented a mitigation for this issue. We will continue to monitor the environment until we're confident that all services are functioning properly.
Customer experience: Customers hosted in the specified regions may have been unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. Other connection methods were unaffected.
Incident start time: 13:25 UTC August 20, 2026
Incident ...
identified
Current status: We're investigating an issue with Snowflake Data Cloud. We've engaged the associated Cloud Service Provider to investigate and troubleshoot this issue further. We'll provide an update within 30 minutes.
Customer experience: Customers hosted in the specified regions may have been unable to connect to Snowflake via private connectivity solutions, such as PrivateLink.
ETA: An ETA is not yet available. We'll provide one as soon as possible.
Incident start time: 13:25 UTC August...
investigating
Current status: We're investigating an issue with Snowflake Data Cloud. We've engaged the associated Cloud Service Provider to investigate and troubleshoot this issue further. We'll provide an update within 60 minutes.
Customer experience: Customers hosted in the specified regions may have been unable to connect to Snowflake via private connectivity solutions, such as PrivateLink.
ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that aff...
INC20000163
majorSource not attested
Last archived state: resolved
View archived record details
AI and ML
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 use Cortex Code in Snowsight and may have seen the following error message: "Internal Server error: You may need to start a new chat." All other Snowflake features are not impacted.
Incident start...
identified
Current status: We've identified an issue with container scheduling in our compute infrastructure that is affecting AI and ML functionality, and we're implementing a fix to restore service. We'll provide another update within 30 minutes.
Customer experience: Customers hosted in the specified region may be unable to use Cortex Code in Snowsight and may see the following error message: "Internal Server error: You may need to start a new chat." All other Snowflake features are not impacted.
ET...
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 issues with AI and ML functionality. Specifically, when using Cortex Code in Snowsight, customer may see the following: “Internal Server error: You may need to start a new chat.”. All other Snowflake features are not impacted.
ETA: An ETA is not yet available. We'll provide one as soon as possible. In...
INC20000158
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 Snowsight and may have seen "503 Service Unavailable" errors.
Incident start time: 17:05 UTC August 14, 2026
Incident end time: 18:12 UTC August 14, 2026
Preliminary root cause: A routine system configuration change intended to o...
identified
Current status: We've identified a system configuration issue affecting Snowsight, and we're implementing a fix to restore service. We'll provide another update within 30 minutes.
Customer experience: Customers hosted in the specified region may be unable to access or use Snowsight and may observe "503 Service Unavailable" errors.
ETA: Our current estimate is that service will be restored within 30 minutes.
Workaround: There are currently no available workarounds for this issue.
Incident ...
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 multiple core Snowflake services and features using Snowsight. Affected users may be unable to sign in and may observe "503 Service Unavailable" errors.
Incident start time: 17:05 UTC August 14, 2026
INC20000157
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Current status: We've identified an issue that caused elevated error rates for Snowsight availability, and we've validated that service health has returned to normal following action by automated recovery systems. We'll continue to monitor the environment until we're confident all services are functioning properly.
Customer experience: Customers hosted in the specified region may have experienced intermittent authentication failures and "service unavailable" errors between approximately 14:2...
INC20000139
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Current status: We've completed implementing our fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. We'll provide another update within 60 minutes.
Customer experience: Customers hosted in the specified region may have been intermittently unable to use CoCo services through Snowsight. Users may have received an "Internal Server Error" when interacting with the service. All other Snowflake features were not impacted.
...
identified
Current status: We've identified an issue with the underlying infrastructure supporting CoCo services, and we're implementing a fix to restore service. We'll provide another update within 30 minutes.
Customer experience: Customers hosted in the specified region may be unable to use CoCo services through Snowsight. Users may receive an "Internal Server Error" when interacting with the service. All other Snowflake features are not impacted.
ETA: Our current estimate is that service will be re...
investigating
Current status: We're continuing to investigate the issue with Snowflake Data Cloud. We're investigating a portion of infrastructure that appears unhealthy to develop a mitigation plan. We'll provide another update within 1 hour.
Customer experience: Customers hosted in the specified regions may be experiencing issues using CoCo through Snowsight. Users may receive an "Internal Server Error," when interacting with the service.
INC20000129
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
Current status: We've confirmed that our service has remained stable since 16:35 UTC, following our mitigation action; however, we're continuing to monitor the environment to confirm that the affected functionality continues to work as expected.
Customer experience: Customers hosted in the specified region may have been unable to start, resume, or manage virtual warehouses. Virtual warehouses may have appeared as stuck in the associated state. Existing warehouses that were already running ma...
monitoring
Current status: We have identified that the previously affected Cloud Services component became unhealthy again, which is preventing virtual warehouses from starting or resuming. We've implemented an additional fix and we're continuing to monitor to confirm that we have fully recovered. We'll provide another update within 60 minutes.
Customer experience: Customers hosted in the specified region may be unable to start, resume, or manage virtual warehouses. Virtual warehouses may appear as stu...
investigating
Current status: While we observed a period of recovery, our telemetry identified a recurrence of impact. We are implementing a mitigation to restore warehouse functionality, and we’ll provide another update within 30 minutes.
Customer experience: Customers hosted in the specified region may be unable to start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that were already running may be unaffected. Customers may a...
monitoring
Current status: We have identified an unhealthy Cloud Services component that is preventing virtual warehouses from starting or resuming. We are implementing a fix and will continue to monitor to confirm that we have fully recovered. We'll provide another update within 30 minutes.
Customer experience: Customers hosted in the specified regions may be unable to start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that ...
investigating
Current status: We have so far not identified any recent changes directly contributing to this problem and are currently focused on investigating performance issues affecting the system that controls virtual warehouse management. We'll provide another update within 30 minutes.
Customer experience: Customers hosted in the specified regions may be unable to start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that are ...
investigating
Current status: We're continuing to investigate the issue with Snowflake Data Cloud, and we're analyzing recent changes and telemetry to determine a mitigation plan. We'll provide another update within 30 minutes.
Customer experience: Customers hosted in the specified regions may be unable to start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that are already running may be unaffected.
ETA: An ETA is not yet avail...
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 start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that are already running may be unaffected.
Incident start time: 13:35 UTC August 03, 2026
INC20000128
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 experienced intermittent Snowsight login failures, elevated page load times, or session timeouts when accessing the web interface. Affected users may encounter errors such as "Failed to fetch" and "Execution failed", or HTTP 503 Service Unavailable messages. T...
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 experienced intermittent Snowsight login failures, elevated page load times, or session timeouts when accessing the web interface. Affected users may encounter errors such as "Failed to fetch" and "Execution failed", or HTTP 503 Service Unavailable messages. T...
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 region may experience intermittent Snowsight login failures, elevated page load times, or session timeouts when accessing the web interface. Affected users may encounter errors such as "Failed to fetch" and "Execution failed", or HTTP 503 Service Unavailable messages. The is...
investigating
Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes.
Customer experience: Customers hosted in the specified regions may experience intermittent Snowsight login failures, elevated page load times, or session timeouts when accessing the web interface. Affected users may encounter errors such as "Failed to fetch" and "Execution failed", or HTTP 503 Service Unavailable messages. The issue is intermittent and does not affect all users ...
July 2026
INC20000115
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
Current status: We've reverted a recent configuration change and confirmed that service has been restored. We'll continue to monitor the environment until we're confident all services are functioning properly.
Customer experience: Customers hosted in the specified regions may have been unable to log in to Snowsight. Affected users may have encountered HTTP 404 errors or "Incoming request with IP/Token is not allowed to access Snowflake" errors when attempting to access Snowsight via private ...
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 30 minutes.
Customer experience: Customers hosted in the specified regions may be unable to log in to Snowsight. Affected users may encounter HTTP 404 errors or "Incoming request with IP/Token is not allowed to access Snowflake" errors when attempting to access Snowsight via private endpoints.
ETA: Our current estimate is that service ...
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 log in to Snowsight. Affected users may encounter HTTP 404 errors or "Incoming request with IP/Token is not allowed to access Snowflake" errors when attempting to access Snowsight via private endpoints.
