Skip to content

Which companies just had a verified incident, who lends to them and who owns them. Every claim carries its evidence level and its source. How we decide what is confirmed

US critical infrastructure monitor

Snowflake

Cloud, identity and critical software · MT (headquarters)

Monitoring
Not checked: the site's robots.txt does not allow it.: last success Nov 6 12:35 UTC
Public findings
0
Provider status posts on record
50

Cyber and operational findings

Analyst-reviewed records. The grade states how well the cause is established; event, first public observation and acknowledgement are separate dates.

No public findings for this organisation.

Provider status posts

Collected from the organisation's own public status page. These are its words; DFX adds only the wording classification.

  • INC20000321Oct 30 20:38 UTC · resolved · minor impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    1. Oct 30 20:38 UTC 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 experience errors or connectivity issues when using Snowflake Openflow. Other features that leverage...
    2. Oct 30 21:28 UTC identified: Current status: We've narrowed our investigation to an issue within the systems that manage connections to Openflow runtimes. We've applied a mitigation in a limited number of cases and are evaluating its effect. We're continuing to investigate the issue and will provide another...
    3. Oct 30 22:15 UTC identified: Current status: We've completed validating our fix and we're implementing it in the affected regions to resolve this issue. We anticipate that the operation will be complete within 4 hours, and affected customers will experience recovery at different times as the fix reaches...
    4. Oct 30 23:20 UTC monitoring: Current status: We've implemented the fix for this issue across the affected regions, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified regions may have been unable...
    5. Oct 31 00:04 UTC 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...
    View on the provider's status page
  • INC20000319Oct 29 04:29 UTC · resolved · minor impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    1. Oct 29 04:29 UTC investigating: Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may experience delays or intermittent failures when resuming or managing virtual warehouses....
    2. Oct 29 05:28 UTC investigating: Current status: We've increased virtual warehouse resources in the specified regions to reduce the impact while we work to identify the cause. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may experience delays or...
    3. Oct 29 06:04 UTC investigating: Current status: We've determined that an issue with a third-party cloud platform provider is affecting our ability to provision virtual warehouse resources in the specified regions. The provider is deploying a fix, and we're working with them to restore service. We'll provide...
    4. Oct 29 07:04 UTC identified: Current status: We've confirmed that an issue with a third-party cloud platform provider is affecting our ability to provision virtual warehouse resources in the specified regions. The provider is in the process of deploying a fix, and we are starting to see initial signs of...
    5. Oct 29 08:04 UTC identified: Current status: We've confirmed that an issue with a third-party cloud platform provider is affecting our ability to provision virtual warehouse resources in the specified regions. The provider remains in the process of deploying a fix across impacted regions and we're starting...
    6. Oct 29 09:04 UTC identified: Current status: We've confirmed that an issue with a third-party cloud platform provider is affecting our ability to provision virtual warehouse resources in the specified regions. The provider remains in the process of deploying a fix across impacted regions and, although they...
    7. Oct 29 10:49 UTC identified: Current status: We've confirmed that an issue with a third-party cloud platform provider is affecting our ability to provision virtual warehouse resources in the specified regions. Although the provider continues to take recovery actions impacted regions, our telemetry indicates...
    8. Oct 29 13:48 UTC identified: Current status: We've confirmed that an issue with a third-party cloud platform provider is affecting our ability to provision virtual warehouse resources in the specified regions. The provider is actively progressing their recovery actions and our telemetry continues to...
    9. Oct 29 16:53 UTC identified: Current status: Our telemetry continues to indicate that the majority of customer impact is no longer occurring. We're continuing to coordinate with the third-party cloud platform provider responsible for managing the affected service environment as they actively work towards...
    10. Oct 29 21:37 UTC identified: Current status: Our telemetry continues to indicate that the majority of customer impact is no longer occurring. The third-party cloud platform provider responsible for managing the affected service environment is finalizing their fix for the issue, and we're monitoring our...
    11. Oct 30 00:47 UTC monitoring: Current status: Our third-party cloud platform provider has completed their fix for the underlying issue at 20:45 UTC October 29, 2026. Our earlier mitigation actions had already addressed the majority of customer impact as of 08:40 UTC October 29, 2026. With the provider's fix...
    12. Oct 30 01:57 UTC resolved: Current status: We've coordinated with our third-party cloud platform to implement the fix for this issue, and we've monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake...
    View on the provider's status page
  • INC20000301Oct 21 18:26 UTC · postmortem · critical impact
    Service restricted or degradedSign-in disruptionInvestigation mentionedRestoration reported
    1. Oct 21 18:26 UTC 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...
    2. Oct 21 18:58 UTC 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...
    3. Oct 21 19:34 UTC 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...
    4. Oct 21 20:04 UTC 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....
    5. Oct 21 20:40 UTC 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....
    6. Oct 21 21:04 UTC 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...
    7. Oct 21 21:35 UTC 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...
    8. Oct 21 22:22 UTC 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...
    9. Oct 21 23:29 UTC 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...
    10. Oct 28 21:13 UTC 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)
    View on the provider's status page
  • INC20000299Oct 21 07:45 UTC · postmortem · minor impact
    Service restricted or degradedRestoration reported
    1. Oct 21 07:45 UTC monitoring: Current status: We identified that a subset of infrastructure responsible for routing service traffic in the affected region became intermittently unhealthy, which caused some requests to fail. We removed the affected infrastructure from service and are monitoring the...
    2. Oct 21 08:36 UTC resolved: Current status: We've monitored the environment and confirmed 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...
    3. Oct 28 13:47 UTC 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/INC20000299](https://community.snowflake.com/s/article/INC20000299)
    View on the provider's status page
  • INC20000294Oct 20 06:34 UTC · postmortem · critical impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    1. Oct 20 06:34 UTC 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...
    2. Oct 20 07:22 UTC 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...
    3. Oct 20 07:49 UTC 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...
    4. Oct 20 09:39 UTC 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...
    5. Oct 20 12:30 UTC 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...
    6. Oct 20 14:34 UTC 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...
    7. Oct 20 15:26 UTC 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...
    8. Nov 3 16:23 UTC 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)
    View on the provider's status page
  • INC20000290Oct 19 00:26 UTC · resolved · minor impact
    Restoration reported
    1. Oct 19 00:26 UTC monitoring: Current status: We identified an issue with our third-party cloud platform that affected private connectivity in the specified region. The issue has been resolved, and we're working with the provider to confirm the underlying cause. We'll continue to monitor the environment...
    2. Oct 19 01:11 UTC 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...
    View on the provider's status page
  • INC20000287Oct 16 01:14 UTC · postmortem · critical impact
    Service restricted or degradedRestoration reported
    1. Oct 16 01:14 UTC monitoring: Current status: We identified that a subset of infrastructure responsible for processing queries and Snowsight requests in the affected region experienced elevated load, which caused intermittent delays and query failures. The load has since subsided, and query processing and...
    2. Oct 16 01:43 UTC resolved: Current status: We've monitored the environment and confirmed 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...
    3. Oct 23 16:47 UTC postmortem: [https://community.snowflake.com/s/article/INC20000287](https://community.snowflake.com/s/article/INC20000287)
    View on the provider's status page
  • INC20000277Oct 13 15:53 UTC · postmortem · minor impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    1. Oct 13 15:53 UTC 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...
    2. Oct 13 16:40 UTC 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...
    3. Oct 13 17:38 UTC 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...
    4. Oct 13 18:36 UTC 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...
    5. Oct 13 20:06 UTC 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...
    6. Oct 13 21:47 UTC 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...
    7. Oct 13 23:54 UTC 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...
    8. Oct 14 03:19 UTC 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...
    9. Oct 14 21:47 UTC 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...
    10. Oct 15 04:57 UTC 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,...
    11. Oct 15 21:03 UTC 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...
    12. Oct 15 21:51 UTC 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...
    13. Oct 23 20:17 UTC 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)
    View on the provider's status page
  • INC20000263Oct 6 14:44 UTC · postmortem · major impact
    Investigation mentionedRestoration reported
    1. Oct 6 14:44 UTC investigating: Current status: We're investigating an issue affecting user connections to Snowflake. We've narrowed our investigation to network connectivity between certain customer locations and the affected regions, and we've engaged third-party providers to assist. We're continuing to...
    2. Oct 6 15:17 UTC monitoring: Current status: A third-party network provider reported that they are implementing a fix for the connectivity problems, and we have since observed signs of recovery in our health checks. We’ll continue to monitor the environment until we’re confident all services are functioning...
    3. Oct 6 15:57 UTC resolved: Current status: We've coordinated with our third-party provider who implemented a fix for this issue, and we've monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake...
    4. Oct 21 23:02 UTC postmortem: [https://community.snowflake.com/s/article/INC20000263](https://community.snowflake.com/s/article/INC20000263)
    View on the provider's status page
  • INC20000239Sep 27 02:15 UTC · postmortem · critical impact
    Sign-in disruptionRestoration reported
    1. Sep 27 02:15 UTC monitoring: Current status: We identified an issue with our third-party cloud platform that caused impact to Snowflake services. We've coordinated with our third-party cloud platform to implement the fix for this issue, and we'll continue to monitor the environment until we're confident all...
    2. Sep 27 03:16 UTC resolved: Current status: We've coordinated with our third-party cloud platform to implement the fix for this issue, and we've monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake...
    3. Oct 9 09:55 UTC 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/INC20000239](https://community.snowflake.com/s/article/INC20000239)
    View on the provider's status page
  • INC20000237Sep 25 23:00 UTC · postmortem · critical impact
    Service restricted or degradedSign-in disruptionInvestigation mentionedRestoration reported
    View on the provider's status page
  • INC20000217Sep 14 04:48 UTC · resolved · major impact
    Service restricted or degradedSign-in disruptionInvestigation mentionedRestoration reported
    View on the provider's status page
  • INC20000213Sep 11 07:18 UTC · postmortem · critical impact
    Sign-in disruptionInvestigation mentionedRestoration reported
    View on the provider's status page
  • INC20000211Sep 9 21:53 UTC · resolved · critical impact
    Service restricted or degradedSign-in disruptionInvestigation mentionedRestoration reported
    View on the provider's status page
  • INC20000199Sep 4 07:34 UTC · postmortem · critical impact
    Investigation mentionedRestoration reported
    View on the provider's status page
  • INC20000190Sep 1 09:58 UTC · postmortem · major impact
    Sign-in disruptionInvestigation mentionedRestoration reported
    View on the provider's status page
  • INC20000188Aug 31 17:20 UTC · postmortem · critical impact
    Service restricted or degradedSign-in disruptionInvestigation mentionedRestoration reported
    View on the provider's status page
  • INC20000150Aug 28 00:07 UTC · identified · minor impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    View on the provider's status page
  • INC20000182Aug 27 19:05 UTC · postmortem · major impact
    Investigation mentionedRestoration reported
    View on the provider's status page
  • INC20000175Aug 25 03:53 UTC · postmortem · critical impact
    Investigation mentionedRestoration reported
    View on the provider's status page
  • INC20000173Aug 24 16:22 UTC · postmortem · major impact
    Sign-in disruptionInvestigation mentionedRestoration reported
    View on the provider's status page
  • INC20000168Aug 20 13:47 UTC · postmortem · major impact
    Investigation mentionedRestoration reported
    View on the provider's status page
  • INC20000163Aug 18 12:58 UTC · postmortem · major impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    View on the provider's status page
  • INC20000158Aug 14 17:29 UTC · postmortem · critical impact
    Service restricted or degradedSign-in disruptionInvestigation mentionedRestoration reported
    View on the provider's status page
  • INC20000157Aug 14 15:19 UTC · postmortem · critical impact
    Service restricted or degradedSign-in disruptionRestoration reported
    View on the provider's status page