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 | 13 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 “INC20000337”. 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
INC20000337
minor resolved · started · resolved
3 updates
- 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 region may experience delays when resuming or scaling up warehouses, and may experience intermittent delays when creating or scaling up Snowpark Container Services compute pools. Workaround: There are currently no available workarounds for this issue.
- monitoring
Current status: We've retained existing virtual warehouse resources in the specified region, and we've observed that service has recovered. We'll continue to monitor the environment, and we're working with our third-party cloud platform provider to identify the source of the issue. Customer experience: Customers hosted in the specified region may have experienced delays when resuming or scaling up warehouses, and may have experienced intermittent delays when creating or scaling up Snowpark Container Services compute pools. Impact start time: 01:50 UTC November 07, 2026 Impact end time: 03:14 UTC November 07, 2026 Preliminary root cause: An issue affected resource provisioning in the specified region.
- resolved
Current status: Our third-party cloud platform provider resolved the issue, and we've monitored the environment to confirm that service has been restored. 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 hosted in the specified region may have experienced delays when resuming or scaling up warehouses, and may have experienced intermittent delays when creating or scaling up Snowpark Container Services compute pools. Impact start time: 01:50 UTC November 07, 2026 Impact end time: 03:14 UTC November 07, 2026 Preliminary root cause: Our third-party cloud platform provider experienced an issue that affected resource provisioning. A root cause analysis (RCA) will be conducted and a summary will be made available within 10 business days.
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.