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, Virtual Warehouses, Data Loading and Unloading

The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started30 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 “INC20000301”. 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

INC20000301

critical postmortem · started · resolved

10 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 regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, use Snowsight, or ingest files using Snowpipe.

  2. investigating

    Current status: We're investigating the core systems that process requests in the impacted region to assist us in isolating the source of the impact and identifying a path to resolution. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, use Snowsight, execute queries, or ingest files using Snowpipe.

  3. investigating

    Current status: We're continuing to investigate the core systems that process requests in the impacted region to assist us in isolating the root cause of this issue. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, use Snowsight, execute queries, or ingest files using Snowpipe. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, customers using replication may review their failover procedures and determine whether failover is warranted based on the impact to their organization.

  4. investigating

    Current status: We've identified a configuration issue within the core systems which process requests in the impacted region that we suspect is contributing to impact, and we're further investigating this issue to confirm our findings and identify a method to restore service. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, use Snowsight, execute queries, resume virtual warehouses, or ingest files using Snowpipe or Snowpipe Streaming. Scheduled tasks and other automated workloads may also fail to run or may not start as expected. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, customers using replication may review their failover procedures and determine whether failove

  5. investigating

    Current status: We've completed a configuration change to address the issue that we suspect caused the impact while we continue to investigate other potential factors. We're also monitoring the region for signs of recovery and are continuing to work on restoring full service. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, use Snowsight, execute queries, resume virtual warehouses, or ingest files using Snowpipe or Snowpipe Streaming. Scheduled tasks and other automated workloads may also fail to run or may not start as expected. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, customers using replication may review their failover procedures and determine whether failove

  6. identified

    Current status: We're continuing to monitor the affected region, and we're seeing early signs of recovery. Affected services are recovering gradually, and we're working to confirm full restoration. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, use Snowsight, execute queries, resume virtual warehouses, or ingest files using Snowpipe or Snowpipe Streaming. Scheduled tasks and other automated workloads may also fail to run or may not start as expected. ETA: Our current estimate is that service will be restored within 1 hour. Impact start time: 18:00 UTC October 21, 2026

  7. identified

    Current status: Services in the specified region are recovering, and our monitoring indicates that most core services, including sign-in, Snowsight, query execution, and data ingestion, are returning to normal operation. We're continuing to monitor to confirm full recovery across all services. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, use Snowsight, execute queries, resume virtual warehouses, or ingest files using Snowpipe or Snowpipe Streaming. Scheduled tasks and other automated workloads may also fail to run or may not start as expected. Impact start time: 18:00 UTC October 21, 2026 Preliminary root cause: A recent configuration change in the affected region caused service infrastructure to stop proce

  8. monitoring

    Current status: Our monitoring indicates that the previously affected services have returned to normal operation. 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 access or use multiple Snowflake services and features. Affected users may have been unable to sign in, use Snowsight, execute queries, resume virtual warehouses, or ingest files using Snowpipe or Snowpipe Streaming. Scheduled tasks and other automated workloads may also have failed to run or may not start as expected. Impact start time: 18:00 UTC October 21, 2026 Impact end time: 21:25 UTC October 21, 2026 Preliminary root cause: A configuration change applied to the cloud services layer in the specified region interacted with existing settings in a way that caused a significant number of

  9. 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 access or use multiple Snowflake services and features. Affected users may have been unable to sign in, use Snowsight, execute queries, resume virtual warehouses, or ingest files using Snowpipe or Snowpipe Streaming. Scheduled tasks and other automated workloads may also have failed to run or may not start as expected. Impact start time: 17:50 UTC October 21, 2026 Impact end time: 21:25 UTC October 21, 2026 Preliminary root cause: A configuration change applied to the cloud services layer in the specified region interacted with existing settin

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

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