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: Virtual Warehouses

The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started4 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: resolved on “INC20000351”. 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

INC20000351

minor resolved · started · resolved

4 updates

  1. identified

    Current status: We've identified the source of the issue, and we're developing and implementing a fix to restore service. We'll provide another update within 1 hour. Customer experience: As our teams begin executing recovery actions, customers hosted in the specified regions may continue to experience intermittently delayed virtual warehouse resume operations, causing queued or delayed queries for workloads running on affected warehouses. 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. Impact start time: 08:07 UTC November 16, 2026

  2. identified

    Current status: We're continuing to implement our recovery actions to restore service. We'll provide another update within 1 hour. Customer experience: As our teams execute their recovery actions, customers hosted in the specified region may continue to experience intermittently delayed virtual warehouse resume operations, causing queued or delayed queries for workloads running on affected warehouses. We expect these delays to reduce as our actions progress and take effect. 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. Impact start time: 08:07 UTC November 16, 2026

  3. 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: As our teams have executed their recovery actions, customers hosted in the specified region should no longer be experiencing intermittently delayed virtual warehouse resume operations, causing queued or delayed queries for workloads running on affected warehouses. Impact start time: 08:07 UTC November 16, 2026 Impact end time: 15:00 UTC November 16, 2026 Preliminary root cause: An update intended to improve the allocation of infrastructure resources to virtual warehouse resulted in unexpected behavior and has been rolled back.

  4. 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 experienced intermittent delays on virtual warehouse resume operations, which could have caused queued or delayed queries for workloads running on affected warehouses. Impact start time: 08:07 UTC November 16, 2026 Impact end time: 15:00 UTC November 16, 2026 Preliminary root cause: Our investigation identified that a recent configuration change intended to improve resource allocation on associated virtual warehouse infrastructure resulted in customer impact. Specifically, this change inadvertently increased the volume of the requests being handled by the af

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