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
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 22 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 “INC20000319”. 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
INC20000319
minor resolved · started · resolved
12 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 regions may experience delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that are already running may be unaffected. Additionally, serverless tasks may take longer than expected to run. Impact start time: 03:00 UTC October 29, 2026
- investigating
Current status: We've increased virtual warehouse resources in the specified regions to reduce the impact while we work to identify the cause. We'll provide an update within 60 minutes. 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. Additionally, serverless tasks may take longer than expected to begin. Workaround: There are currently no available workarounds for this issue. Impact start time: 03:00 UTC October 29, 2026
- investigating
Current status: We've determined that an issue with a third-party cloud platform provider is affecting our ability to provision virtual warehouse resources in the specified regions. The provider is deploying a fix, and we're working with them to restore service. We'll provide another update within 60 minutes. 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. Additionally, serverless tasks may take longer than expected to begin. ETA: Based on information from our third-party cloud platform provider, we expect their fix to be in place within two hours. We'll provide an updated ETA as we receive more information. Workaround: There are currently no available workarounds for this issue. Impact start time: 03:00 UTC October 29
- identified
Current status: We've confirmed that an issue with a third-party cloud platform provider is affecting our ability to provision virtual warehouse resources in the specified regions. The provider is in the process of deploying a fix, and we are starting to see initial signs of recovery across a subset of regions. We continue to work with them as they progress the fix across all impacted regions and will provide another update within 60 minutes. 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. Additionally, serverless tasks may take longer than expected to begin. ETA: Based on information from our third-party cloud platform provider, we expect their fix to be in place within 90 minutes. Workaround: There are currently no a
- identified
Current status: We've confirmed that an issue with a third-party cloud platform provider is affecting our ability to provision virtual warehouse resources in the specified regions. The provider remains in the process of deploying a fix across impacted regions and we're starting to see indications of recovery across our EMEA regions. We continue to work with them as they progress their recovery actions and will provide another update within 60 minutes. 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. Additionally, serverless tasks may take longer than expected to begin. ETA: Based on information from our third-party cloud platform provider, we still expect their fix to be in place within 90 minutes. Workaround: There are
- identified
Current status: We've confirmed that an issue with a third-party cloud platform provider is affecting our ability to provision virtual warehouse resources in the specified regions. The provider remains in the process of deploying a fix across impacted regions and, although they have revised their timeframe to recovery, we expect the majority of customer impact to now be mitigated. We remain in contact with them as they progress their recovery actions and will provide another update within 2 hours. 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. Additionally, serverless tasks may take longer than expected to begin. ETA: Based on information from our third-party cloud platform provider, we expect their fix to be in place
- identified
Current status: We've confirmed that an issue with a third-party cloud platform provider is affecting our ability to provision virtual warehouse resources in the specified regions. Although the provider continues to take recovery actions impacted regions, our telemetry indicates that the majority of customer impact remains mitigated. We're in contact with the provider as they actively work towards recovery and will provide another update within 3 hours. 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. Additionally, serverless tasks may take longer than expected to begin. ETA: Based on information from our third-party cloud platform provider, we can't provide an ETA for recovery but expect the majority of customer impact
- identified
Current status: We've confirmed that an issue with a third-party cloud platform provider is affecting our ability to provision virtual warehouse resources in the specified regions. The provider is actively progressing their recovery actions and our telemetry continues to indicate that the majority of customer impact is mitigated. We're in contact with the provider as they actively work towards recovery and will provide another update within 3 hours. 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. Additionally, serverless tasks may take longer than expected to begin. ETA: Based on information from our third-party cloud platform provider, we can't provide an ETA for recovery but expect the majority of customer impact to
- identified
Current status: Our telemetry continues to indicate that the majority of customer impact is no longer occurring. We're continuing to coordinate with the third-party cloud platform provider responsible for managing the affected service environment as they actively work towards full recovery and will provide another update within 4 hours. Customer experience: Customers hosted in the specified regions may have experienced delays or intermittent failures when resuming or managing virtual warehouses, with the majority of impact occurring between 03:00 and 08:40 UTC October 29, 2026. Existing warehouses that were already running may have been unaffected. Additionally, serverless tasks may have taken longer than expected to begin. Following our mitigation actions, we aren't currently observing any ongoing customer impact. ETA: Based on information from our third-party cloud platform provider, w
- identified
Current status: Our telemetry continues to indicate that the majority of customer impact is no longer occurring. The third-party cloud platform provider responsible for managing the affected service environment is finalizing their fix for the issue, and we're monitoring our telemetry as the operation completes to confirm that the change has completely resolved the underlying issue affecting the provisioning request workflow. We will provide another update within 4 hours. 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. Additionally, serverless tasks may have taken longer than expected to begin. Following our mitigation actions, we aren't currently observing any ongoing customer impact. ETA: Based on inform
- monitoring
Current status: Our third-party cloud platform provider has completed their fix for the underlying issue at 20:45 UTC October 29, 2026. Our earlier mitigation actions had already addressed the majority of customer impact as of 08:40 UTC October 29, 2026. With the provider's fix in place, we've reversed those temporary mitigation actions and confirmed that we are back to pre-incident configurations at 23:05 UTC October 29, 2026. 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. Additionally, serverless tasks may have taken longer than expected to begin. Following our mitigation actions, we aren't currently
- resolved
Current status: We've coordinated with our third-party cloud platform to implement the fix for this issue, and we've monitored the environment to confirm that service was 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 regions may have experienced delays or intermittent failures when resuming or managing virtual warehouses, with the majority of impact occurring between 03:00 and 08:40 UTC October 29, 2026. Existing warehouses that were already running may have been unaffected. Additionally, serverless tasks may have taken longer than expected to begin. Impact start time: 03:00 UTC October 29, 2026 Impact end time: 08:40 UTC October 29, 2026 Preliminary root cause: A third-party cloud platform provider experienced an issue that slowed
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.