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: Data Loading and Unloading

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

INC20000277

minor postmortem · started · resolved

13 updates

  1. 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 execute scheduled or manual tasks. Tasks may be stuck in a pending state or fail to initiate, and affected users may see an "Unexpected exception during task dispatch" message or similar error messages.

  2. investigating

    Current status: Our investigation has identified that tasks appear to be failing due to an a potential issue with a backend record lookup on the metadata database layer, and we're working to determine what's causing these records to return null and result in task failures. We'll provide another update within 1 hour. Customer experience: Customers hosted in the specified region may experience failures when executing scheduled or manual tasks. Tasks may be marked as failed even though the underlying query completed successfully, or may fail to initiate. Affected users may see an "Unexpected exception during task completion" message or similar error messages. Incident start time: 10:58 UTC October 13, 2026

  3. investigating

    Current status: We've determined that a directory issue within the components of the metadata store responsible for facilitating the impacted tasks is preventing some task records from being read consistently, which is causing the task failures. We're working to identify the origin of the directory issue to assist us in restoring normal task execution. We'll provide another update within 1 hour. Customer experience: Customers hosted in the specified region may experience intermittent issues with scheduled or manual tasks. Most tasks complete as expected, but some may be marked as failed even though they ran successfully. A small number of tasks may remain in a pending state or fail to start, and affected users may see an "Unexpected exception during task dispatch" message or similar error messages. Incident start time: 10:58 UTC October 13, 2026

  4. investigating

    Current status: Our investigation indicates that the directory issue is limited to the records the metadata store keeps for task execution. We're developing a fix to restore the impacted metadata and resolve the impact; however, due to the complexity of the issue, we expect this will take an extended amount of time. Once complete, we'll proceed with deploying the fix as a potential mitigation. We'll provide another update within 2 hours. Customer experience: Customers hosted in the specified region may experience intermittent issues with scheduled or manual tasks. Most tasks complete as expected, but some may be marked as failed even though they ran successfully. A small number of tasks may remain in a pending state or fail to start, and affected users may see an "Unexpected exception during task dispatch" message or similar error messages. Incident start time: 10:58 UTC October 13, 2026

  5. investigating

    Current status: We're continuing our development of the fix to restore the impacted metadata. We'll provide another update within 2 hours. While our remediation efforts are ongoing, before rerunning a task that's reported as failed, we recommend checking query history to confirm whether the task's query completed successfully. Customer experience: Customers hosted in the specified region may experience intermittent issues with scheduled or manual tasks. Most tasks complete as expected, but some may be marked as failed even though they ran successfully. A small number of tasks may remain in a pending state or fail to start, and affected users may see an "Unexpected exception during task dispatch" message or similar error messages. Incident start time: 10:58 UTC October 13, 2026

  6. investigating

    Current status: We're validating our fix to restore the impacted metadata and preparing to begin deployment to the affected region. We'll provide another update within 2 hours. While our remediation efforts are ongoing, before rerunning a task that's reported as failed, we recommend checking query history to confirm whether the task's query completed successfully. Customer experience: Customers hosted in the specified region may experience intermittent issues with scheduled or manual tasks. Most tasks complete as expected, but some may be marked as failed even though they ran successfully. A small number of tasks may remain in a pending state or fail to start, and affected users may see an "Unexpected exception during task dispatch" message or similar error messages. Incident start time: 10:58 UTC October 13, 2026

  7. investigating

    Current status: We're continuing to develop the fix to restore the impacted task metadata. Once it's fully developed and validated, we'll begin deploying it to the affected region. While our remediation efforts are ongoing, before rerunning a task that's reported as failed, we recommend checking query history to confirm whether the task's query completed successfully. We'll provide another update within 4 hours. Customer experience: Customers hosted in the specified region may experience intermittent issues with scheduled or manual tasks. Most tasks complete as expected, but some may be marked as failed even though they ran successfully. A small number of tasks may remain in a pending state or fail to start, and affected users may see an "Unexpected exception during task dispatch" message or similar error messages. ETA: An ETA is not yet available. We'll provide one as soon as possible.

  8. investigating

    Current status: We've modified our remediation approach. After further investigation, we've determined that restarting infrastructure in the affected region is the most effective way to restore normal task execution. The infrastructure restart effort is in progress, and we've observed a decrease in task failure rates on infrastructure that has been restarted. We're monitoring to confirm normal task execution is fully restored across all the infrastructure. As a side effect of the restarts, task graph run history from before the incident start time (10:58 UTC October 13, 2026) may currently be unavailable, and history from after that time may be incomplete. We're investigating options to restore this history and we'll provide another update by 22:00 UTC on October 14. Customer experience: Prior to the mitigation: Customers hosted in the affected region may have experienced intermittent is

  9. identified

    Current status: While the infrastructure restarts in the affected region are still in progress, our monitoring indicates that the service is gradually recovering and the majority of failed tasks are now succeeding after being restarted. We're continuing to monitor the affected infrastructure to confirm that the service fully recovers as expected, and we're working on restoring the task graph run history affected by the restarts to resolve the remaining impact. We'll provide another update within 8 hours. Customer experience: Prior to the mitigation: Customers hosted in the affected region may have experienced intermittent issues with scheduled or manual tasks. Most tasks completed as expected, but some may have been marked as failed even though they ran successfully. A small number of tasks may have remained in a pending state or failed to start. Affected users may have seen an error mes

  10. identified

    Current status: The infrastructure restarts in the affected region are complete, and our monitoring indicates that the service is continuing to recover. Tasks that were scheduled before the restarts and haven't yet run afterward may be marked as failed the next time they run, even though they actually run successfully. We're preparing a fix to restore the task graph run history and resolve the remaining impact. We'll provide another update within 15 hours. Customer experience: Prior to the mitigation: Customers hosted in the affected region may have experienced intermittent issues with scheduled or manual tasks. Most tasks completed as expected, but some may have been marked as failed even though they ran successfully. A small number of tasks may have remained in a pending state or failed to start. Affected users may have seen an error message, such as "Unexpected exception during task d

  11. monitoring

    Current status: The infrastructure restarts in the affected region are complete, and our monitoring indicates that the error leading to task failure has been resolved and previously affected tasks are now consistently running successfully. While the functional impact of the issue is resolved, we're deploying a secondary fix to restore the remaining task graph run history. Based on the nature of this activity, we expect this work will take an extended amount of time. Customer experience: While the functional impact regarding task failures or tasks silently succeeding is resolved, affected customers may still see incomplete task graph run history. Specifically: - When customers open or refresh the Task Graphs tab on the Tasks page in Snowsight (Transformation » Tasks), or the Run History tab for individual tasks, they may not see task runs from before 10:58 UTC October 13, 2026. Some task

  12. resolved

    Current status: We've implemented the fix for this issue and monitored the environment to confirm that service was restored. We're continuing our deployment of a secondary fix to restore the remaining task graph run history for the affected time period. 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 affected region may have experienced intermittent issues with scheduled or manual tasks. Most tasks completed as expected, but some may have been marked as failed even though they ran successfully. A small number of tasks may have remained in a pending state or failed to start. Affected users may have seen an error message, such as "Unexpected exception during task dispatch." After the primary mitigation, the next time each task ran, it may still have been

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

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