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: Applications
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 88 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: postmortem on “INC20000173”. 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 “postmortem”. 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
INC20000173
major postmortem · started · resolved
6 updates
- 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
- 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 are currently no available workarounds for this issue. Incident start time: 15:00 UTC August 24, 2026
- 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
- 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, 2026 Preliminary root cause: A system configuration change caused an outdated application version to be deployed, resulting in authentication session failures. Once identified, the configuration was corrected to restore the proper application version.
- resolved
Current status: We've implemented the fix for this issue and 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 region may have been unable to remain logged in to Snowsight, experiencing immediate logout after successful authentication. Incident start time: 14:47 UTC August 24, 2026 Incident end time: 17:21 UTC August 24, 2026 Preliminary root cause: A system configuration change caused an outdated application version to be deployed, resulting in authentication session failures. Once identified, the configuration was corrected to restore the proper application version. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 bus
- postmortem
Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC20000173](https://community.snowflake.com/s/article/INC20000173)
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.