Operational Snowflake status
snowflake.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
Snowflake looks fine itself, but Amazon Web Services, a provider it may run on (inferred), reports major outage. Watch for knock-on effects.
confidence: low Vendor: operational · users: normal · routing: no data · upstream providers: major.
- Vendor status page Operational · 1 open incident
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) Amazon Web Services: Major outage
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: Virtual Warehouses, Snowpark Container Services
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 85 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: resolved on “INC20000150”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
- Amazon Web Services reports an issue. Snowflake may depend on it (inferred from public sources). Coincidence, not causation. evidence confidence: low
What we don't know: what is happening inside Snowflake's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp. Routing data shows reachability, not whether the app works.
Coincidence, not causation: signals that overlap in time are shown side by side, not as proof of cause.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data · upstream providers: major. Vendor status and outside signals roughly agree.
Who depends on whom
Snowflake may run on Amazon Web Services, Microsoft Azure, Google Cloud (inferred). We don't map other services that depend on Snowflake. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Snowflake or its upstream providers, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; and whether dependents start reporting issues.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Snowflake. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
INC20000150
minor resolved · started · resolved
14 updates
- 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
- 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 exper
- 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 a
- 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
- 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 virtua
- 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 Snowp
- 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. C
- 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 failu
- identified
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 o
- identified
Current status: Since our last update, we have seen improvement in Snowpark Container Services availability. Additional capacity became available in the specified region and has been reserved for customer workloads. Virtual warehouse capacity and provisioning performance also remain improved. We continue to monitor both services through periods of peak demand and are coordinating with our third-party cloud provider on additional capacity. While we have seen significant improvement across all affected services, workloads that require additional new capacity may still be affected, so we are continuing to monitor resource availability until the issue is fully resolved. We will provide another update within 7 days, or sooner if there is a material change. Customer experience: Customers using Snowpark Container Services should see improved ability to start or resume current supported workload
- identified
Current status: Virtual warehouse capacity and provisioning have remained stable, and we do not expect further broad risk to customer workloads, but we will continue monitoring through periods of peak demand. Snowpark Container Services (SPCS) 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 have seen improvement, but workloads that require additional new capacity may still be affected. We continue to target late October before considering the SPCS impact mitigated, subject to sustained resource availability and service readiness. We will provide another update within seven days, or sooner if there is a significant change. Customer experience: Customers using virtual warehouses should no longer experience the broader provisioning impact associated with this inc
- identified
Current status: We continue to see stable virtual warehouse performance and consider the impact mitigated. Additional information about virtual warehouse impact is available in previous updates. Snowpark Container Services continues to show improvement. We expect to receive additional capacity within the next several days and will validate service readiness as it becomes available. Until then, workloads that require new or resumed capacity may remain affected. We will provide another update within seven days, or sooner if there is a significant change. Customer experience: Customers using Snowpark Container Services may still experience delays, timeouts, or failures when starting or resuming Notebooks, provisioning or resuming compute pools, or setting up OpenFlow runtimes. Existing workloads generally continue to run normally; the remaining risk is concentrated in workloads that require
- identified
Current status: Virtual warehouse performance remains stable. For Snowpark Container Services, additional capacity has not yet become available, later than the end-of-October timeframe previously communicated. We now expect the capacity to become available by the end of next week. We will validate service readiness once it arrives and share a more substantive update. Until then, workloads that require new or resumed capacity may remain affected. We will provide another update within seven days, or sooner if there is a significant change. Customer experience: Customers using Snowpark Container Services may still experience delays, timeouts, or failures when starting or resuming Notebooks, provisioning or resuming compute pools, or setting up OpenFlow runtimes. Existing workloads generally continue to run normally; the remaining risk is concentrated in workloads that require new or resumed
- resolved
Current status: Additional compute capacity is now available in the specified region and has been reserved for customer workloads. Snowpark Container Services has resumed normal provisioning, including for new workloads. Virtual warehouse capacity and provisioning have stayed stable since October 7, 2026. We've confirmed that both services have recovered and consider this issue resolved. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers in the specified region who used Snowpark Container Services may have had delays, timeouts, or failures. These happened when starting or resuming Notebooks or Streamlit apps, provisioning or resuming compute pools, or setting up OpenFlow runtimes. Impact was intermittent and varied by instance type and availability zone. Workloads that
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.