CHYP.ai · ORBIT // Cloudy_Day Security Suite

Databases & data

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 vs. reality: Vendor status and outside signals roughly agree

Regions mentioned: Databases, Tables, and Views, Data Loading and Unloading, Applications

The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started31 days
Crowd clock when user reports began rising above normalnot seenn/a
Network clock when routing anomaly data first flagged itnot seenn/a
ORBIT clock when our checker first recorded the changenot seenn/a

Evidence

  • Official page: Operational (“All Systems Operational”). evidence confidence: high
  • Vendor stage: postmortem on “INC20000294”. 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

INC20000294

critical postmortem · started · resolved

8 updates

  1. 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 region may be unable to access or use multiple Snowflake services and features, including Snowflake Postgres. Affected users may experience errors or failures when connecting to Snowflake Postgres instances, managing data, loading data, or using applications. Incident start time: 06:01 UTC October 20, 2026

  2. identified

    Current status: We've identified an issue with a third-party cloud platform that's affecting part of the infrastructure in the specified region, and we're coordinating with the provider to develop and implement a fix to restore service. We have identified an issue with one of the availability zones in the region. Workloads have automatically moved away from the affected infrastructure. We'll provide another update within 30 minutes. Customer experience: We're seeing recovery of the affected services as of 6:40 UTC. Customers hosted in the specified region may have been unable to access or use multiple Snowflake services and features, including Snowflake Postgres. Affected users may experience errors or failures when connecting to Snowflake Postgres instances, managing data, loading data, or using applications. ETA: An ETA isn't available yet. We'll provide one as soon as possible. Workar

  3. identified

    Current status: Our monitoring has shown healthy service since 06:40 UTC October 20, 2026, but the affected availability zone remains unavailable at our third-party cloud platform provider. We've stopped new workloads from being placed in that zone and paused routine software updates in the region as a precaution. We're continuing to coordinate with the provider to restore the affected infrastructure and to develop and implement a fix. We'll provide another update within 2 hours. Customer experience: We're seeing recovery of the affected services as of 6:40 UTC. Customers hosted in the specified region may have been unable to access or use multiple Snowflake services and features, including Snowflake Postgres. Affected users may have experienced errors or failures when connecting to Snowflake Postgres instances, managing data, loading data, or using applications. ETA: An ETA isn't availa

  4. identified

    Current status: Our monitoring has shown healthy service since 06:40 UTC October 20, 2026, but the affected availability zone remains unavailable at our third-party cloud platform provider. We've stopped new workloads from being placed in that zone and paused routine software updates in the region as a precaution. We're continuing to coordinate with the provider to restore the affected infrastructure and to develop and implement a fix. Additional updates are available on the Cloud Provider's status page https://status.cloud.google.com/. We'll provide another update within 3 hours. Customer experience: We're seeing recovery of the affected services as of 6:40 UTC. Customers hosted in the specified region may have been unable to access or use multiple Snowflake services and features, including Snowflake Postgres. Affected users may have experienced errors or failures when connecting to Sno

  5. identified

    Our monitoring still shows healthy service since 06:40 UTC October 20, 2026. As per updates on the Cloud Provider's status page https://status.cloud.google.com, some infrastructure in the affected availability zone at our third-party cloud platform provider has begun to come back online, but the zone isn't fully available yet. Our mitigation actions continue to keep new workloads out of the affected zone and these mitigations will remain in place until the availability zone is fully back online. We'll provide another update within 2 hours. Customer experience: We're seeing recovery of the affected services as of 6:40 UTC. Customers hosted in the specified region may have been unable to access or use multiple Snowflake services and features, including Snowflake Postgres. Affected users may have experienced errors or failures when connecting to Snowflake Postgres instances, managing data,

  6. identified

    Current status: Our Cloud Provider has confirmed via their status page https://status.cloud.google.com that the issue has been largely mitigated. We're are closely monitoring service health and are preparing to revert our previously completed precautionary changes; though at this time, customers should no longer be experiencing impact. Customer experience: Customers hosted in the specified region may have been unable to access or use multiple Snowflake services and features, including Snowflake Postgres. Affected users may have experienced errors or failures when connecting to Snowflake Postgres instances, managing data, loading data, or using applications. Incident start time: 06:01 UTC October 20, 2026 Incident end time: 14:03 UTC October 20, 2026

  7. resolved

    Current status: We've monitored the environment and confirmed 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 been unable to access or use multiple Snowflake services and features. Affected users may have experienced errors or failures when connecting to Snowsight, managing data, loading data, or using applications. Incident start time: 06:01 UTC October 20, 2026 Incident end time: 14:00 UTC October 20, 2026 Preliminary root cause: A power event at our third-party cloud platform provider made one of the availability zones in the specified region unavailable. Snowflake infrastructure running in that zone, including components that support Snowsight, became unreachable, and requests that depended o

  8. 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/INC20000294](https://community.snowflake.com/s/article/INC20000294)

Official incident page ↗

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.

Where to next