Snowflake Outage History

Started Oct 30, 2026, 08:38 PM UTC· resolved Oct 31, 2026, 12:04 AM UTC

1. investigating Oct 30, 2026, 08:38 PM UTC

   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 Snowpark Container Services aren't affected by this issue.

2. identified Oct 30, 2026, 09:28 PM UTC

   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 update within 1 hour. Customer experience: Customers hosted in the specified regions may be unable to access or manage their Openflow runtimes deployed in Snowpark Container Services, including the Openflow canvas. Existing data flows are not affected and continue to process data. Other features that leverage Snowpark Container Services are also not affected by this issue. Impact start time: 17:34 UTC October 30, 2026

3. identified Oct 30, 2026, 10:15 PM UTC

   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 their environment. We'll provide another update within 4 hours. Customer experience: Customers hosted in the specified regions may be unable to access or manage their Openflow runtimes deployed in Snowpark Container Services. Runtimes may show as active, but opening the Openflow canvas may fail with errors saying the runtime is unavailable or that the connection was refused. Most existing data flows continue to process data, and other features that leverage Snowpark Container Services aren't affected by this issue. ETA: Our current estimate is that service will be restored within 4 hours. Impact start time: 17:34 UTC October 30, 2026

4. monitoring Oct 30, 2026, 11:20 PM UTC

   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 to access or manage their Openflow runtimes deployed in Snowpark Container Services. Runtimes may have shown as active, but opening the Openflow canvas may have failed with errors saying the runtime was unavailable or that the connection was refused. Impact start time: 17:34 UTC October 30, 2026 Impact end time: 22:55 UTC October 30, 2026 Preliminary root cause: A subset of infrastructure responsible for secure communication with Openflow runtimes experienced a certificate issue, which prevented connections to the affected Openflow runtimes

5. resolved Oct 31, 2026, 12:04 AM UTC

   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 regions may have been unable to access or manage their Openflow runtimes deployed in Snowpark Container Services. Runtimes may have shown as active, but opening the Openflow canvas may have failed with errors saying the runtime was unavailable or that the connection was refused. Impact start time: 17:34 UTC October 30, 2026 Impact end time: 22:55 UTC October 30, 2026 Preliminary root cause: A subset of infrastructure responsible for secure communication with Openflow runtimes experienced a certificate issue, which prevented connections to the affected Openflow runtimes A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.

Read the full incident report →

Started Oct 29, 2026, 04:29 AM UTC· resolved Oct 30, 2026, 01:57 AM UTC

1. investigating Oct 29, 2026, 04:29 AM UTC

   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. Existing warehouses that are already running may be unaffected. Additionally, serverless tasks may take longer than expected to run. Impact start time: 03:00 UTC October 29, 2026

2. investigating Oct 29, 2026, 05:28 AM UTC

   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 intermittent failures when resuming or managing virtual warehouses. Existing warehouses that are already running may be unaffected. Additionally, serverless tasks may take longer than expected to begin. Workaround: There are currently no available workarounds for this issue. Impact start time: 03:00 UTC October 29, 2026

3. investigating Oct 29, 2026, 06:04 AM UTC

   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 another update within 60 minutes. Customer experience: Customers hosted in the specified regions may experience delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that are already running may be unaffected. Additionally, serverless tasks may take longer than expected to begin. ETA: Based on information from our third-party cloud platform provider, we expect their fix to be in place within two hours. We'll provide an updated ETA as we receive more information. Workaround: There are currently no available workarounds for this issue. Impact start time: 03:00 UTC October 29, 2026 Preliminary root cause: A third-party cloud platform provider experienced an issue that slowed responses to resource provisioning requests, which delayed virtual warehouse resumes.

4. identified Oct 29, 2026, 07:04 AM UTC

   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 recovery across a subset of regions. We continue to work with them as they progress the fix across all impacted regions and will provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may experience delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that are already running may be unaffected. Additionally, serverless tasks may take longer than expected to begin. ETA: Based on information from our third-party cloud platform provider, we expect their fix to be in place within 90 minutes. Workaround: There are currently no available workarounds for this issue. Impact start time: 03:00 UTC October 29, 2026 Preliminary root cause: A third-party cloud platform provider experienced an issue that slowed responses to resource provisioning requests, which delayed virtual warehouse resumes.

5. identified Oct 29, 2026, 08:04 AM UTC

   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 to see indications of recovery across our EMEA regions. We continue to work with them as they progress their recovery actions and will provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may experience delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that are already running may be unaffected. Additionally, serverless tasks may take longer than expected to begin. ETA: Based on information from our third-party cloud platform provider, we still expect their fix to be in place within 90 minutes. Workaround: There are currently no available workarounds for this issue. Impact start time: 03:00 UTC October 29, 2026 Preliminary root cause: A third-party cloud platform provider experienced an issue that slowed responses to resource provisioning requests, which delayed virtual warehouse resumes.

6. identified Oct 29, 2026, 09:04 AM UTC

   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 have revised their timeframe to recovery, we expect the majority of customer impact to now be mitigated. We remain in contact with them as they progress their recovery actions and will provide another update within 2 hours. Customer experience: Customers hosted in the specified regions may experience delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that are already running may be unaffected. Additionally, serverless tasks may take longer than expected to begin. ETA: Based on information from our third-party cloud platform provider, we expect their fix to be in place within 2 hours. Workaround: There are currently no available workarounds for this issue. Impact start time: 03:00 UTC October 29, 2026 Preliminary root cause: A third-party cloud platform provider experienced an issue that slowed responses to resource provisioning requests, which delayed virtual warehouse resumes.

7. identified Oct 29, 2026, 10:49 AM UTC

   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 that the majority of customer impact remains mitigated. We're in contact with the provider as they actively work towards recovery and will provide another update within 3 hours. Customer experience: Customers hosted in the specified regions may experience delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that are already running may be unaffected. Additionally, serverless tasks may take longer than expected to begin. ETA: Based on information from our third-party cloud platform provider, we can't provide an ETA for recovery but expect the majority of customer impact to be mitigated. Workaround: There are currently no available workarounds for this issue. Impact start time: 03:00 UTC October 29, 2026 Preliminary root cause: A third-party cloud platform provider experienced an issue that slowed responses to resource provisioning requests, which delayed virtual warehouse resumes.

8. identified Oct 29, 2026, 01:48 PM UTC

   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 indicate that the majority of customer impact is mitigated. We're in contact with the provider as they actively work towards recovery and will provide another update within 3 hours. Customer experience: Customers hosted in the specified regions may experience delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that are already running may be unaffected. Additionally, serverless tasks may take longer than expected to begin. ETA: Based on information from our third-party cloud platform provider, we can't provide an ETA for recovery but expect the majority of customer impact to be mitigated. Workaround: There are currently no available workarounds for this issue. Impact start time: 03:00 UTC October 29, 2026 Preliminary root cause: A third-party cloud platform provider experienced an issue that slowed responses to resource provisioning requests, which delayed virtual warehouse resumes.

9. identified Oct 29, 2026, 04:53 PM UTC

   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 full recovery and will provide another update within 4 hours. Customer experience: Customers hosted in the specified regions may have experienced delays or intermittent failures when resuming or managing virtual warehouses, with the majority of impact occurring between 03:00 and 08:40 UTC October 29, 2026. Existing warehouses that were already running may have been unaffected. Additionally, serverless tasks may have taken longer than expected to begin. Following our mitigation actions, we aren't currently observing any ongoing customer impact. ETA: Based on information from our third-party cloud platform provider, we can't provide an ETA for recovery but expect the majority of customer impact to be mitigated. Impact start time: 03:00 UTC October 29, 2026 Preliminary root cause: A third-party cloud platform provider experienced an issue that slowed responses to resource provisioning requests, which delayed virtual warehouse resumes.

10. identified Oct 29, 2026, 09:37 PM UTC

    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 telemetry as the operation completes to confirm that the change has completely resolved the underlying issue affecting the provisioning request workflow. We will provide another update within 4 hours. Customer experience: Customers hosted in the specified regions may have experienced delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that were already running may have been unaffected. Additionally, serverless tasks may have taken longer than expected to begin. Following our mitigation actions, we aren't currently observing any ongoing customer impact. ETA: Based on information from our third-party cloud platform provider, we can't provide an ETA for recovery but expect the majority of customer impact to be mitigated. Impact start time: 03:00 UTC October 29, 2026 Impact end time: 08:40 UTC October 29, 2026 Preliminary root cause: A third-party cloud platform provider experienced an issue that slowed responses to resource provisioning requests, which delayed virtual warehouse resumes.

11. monitoring Oct 30, 2026, 12:47 AM UTC

    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 in place, we've reversed those temporary mitigation actions and confirmed that we are back to pre-incident configurations at 23:05 UTC October 29, 2026. 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 experienced delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that were already running may have been unaffected. Additionally, serverless tasks may have taken longer than expected to begin. Following our mitigation actions, we aren't currently observing any ongoing customer impact. Impact start time: 03:00 UTC October 29, 2026 Impact end time: 08:40 UTC October 29, 2026 Preliminary root cause: A third-party cloud platform provider experienced an issue that slowed responses to resource provisioning requests, which delayed virtual warehouse resumes.

12. resolved Oct 30, 2026, 01:57 AM UTC

    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 Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified regions may have experienced delays or intermittent failures when resuming or managing virtual warehouses, with the majority of impact occurring between 03:00 and 08:40 UTC October 29, 2026. Existing warehouses that were already running may have been unaffected. Additionally, serverless tasks may have taken longer than expected to begin. Impact start time: 03:00 UTC October 29, 2026 Impact end time: 08:40 UTC October 29, 2026 Preliminary root cause: A third-party cloud platform provider experienced an issue that slowed responses to resource provisioning requests, which delayed virtual warehouse resumes. A root cause analysis (RCA) will be conducted and a summary will be made available within 10 business days.

Read the full incident report →

Started Oct 21, 2026, 06:26 PM UTC· resolved Oct 21, 2026, 11:29 PM UTC

1. investigating Oct 21, 2026, 06:26 PM UTC

   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 Oct 21, 2026, 06:58 PM UTC

   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 Oct 21, 2026, 07:34 PM UTC

   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 Oct 21, 2026, 08:04 PM UTC

   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 failover is warranted based on the impact to their organization. Impact start time: 18:00 UTC October 21, 2026

5. investigating Oct 21, 2026, 08:40 PM UTC

   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 failover is warranted based on the impact to their organization.

6. identified Oct 21, 2026, 09:04 PM UTC

   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 Oct 21, 2026, 09:35 PM UTC

   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 processing requests, resulting in a service disruption.

8. monitoring Oct 21, 2026, 10:22 PM UTC

   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 instances to be taken out of service. This led to cascading failures across sign-in, query execution, data ingestion, and other dependent services.

9. resolved Oct 21, 2026, 11:29 PM UTC

   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 settings in a way that caused a significant number of instances to be taken out of service. This led to cascading failures across sign-in, query execution, data ingestion, and other dependent services. A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.

10. postmortem Oct 28, 2026, 09:13 PM UTC

    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)

Read the full incident report →

Started Oct 21, 2026, 07:45 AM UTC· resolved Oct 21, 2026, 08:36 AM UTC

1. monitoring Oct 21, 2026, 07:45 AM UTC

   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 environment to confirm that all services are functioning properly. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may have experienced intermittent failures when using Snowsight. Symptoms may have included slow page loads or brief errors when accessing Snowsight. Retrying the operation may have succeeded in most cases, as the issue was intermittent in nature. Impact start time: 06:18 UTC October 21, 2026 Impact end time: 07:06 UTC October 21, 2026 Preliminary root cause: A subset of infrastructure responsible for routing incoming traffic in the affected region became unavailable, resulting in intermittent failures when loading Snowsight.

2. resolved Oct 21, 2026, 08:36 AM UTC

   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 specified regions may have experienced intermittent failures when using Snowsight. Symptoms may have included slow page loads or brief errors when accessing Snowsight. Retrying the operation may have succeeded in most cases, as the issue was intermittent in nature. Impact start time: 06:18 UTC October 21, 2026 Impact end time: 07:06 UTC October 21, 2026 Preliminary root cause: A subset of infrastructure responsible for routing incoming traffic in the affected region became unavailable, resulting in intermittent failures when loading Snowsight. A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.

3. postmortem Oct 28, 2026, 01:47 PM UTC

   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)

Read the full incident report →

Started Oct 20, 2026, 06:34 AM UTC· resolved Oct 20, 2026, 03:26 PM UTC

1. investigating Oct 20, 2026, 06:34 AM UTC

   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 Oct 20, 2026, 07:22 AM UTC

   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. Workaround: There are currently no available workarounds for this issue. Incident start time: 06:01 UTC October 20, 2026

3. identified Oct 20, 2026, 07:49 AM UTC

   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 available yet. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 06:01 UTC October 20, 2026

4. identified Oct 20, 2026, 09:39 AM UTC

   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 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. Workaround: There are currently no available workarounds for this issue. Incident start time: 06:01 UTC October 20, 2026

5. identified Oct 20, 2026, 12:30 PM UTC

   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, loading data, or using applications. ETA: Our current estimate is that the availability zone will be restored within 2 hours. Workaround: There are currently no available workarounds for this issue. Incident start time: 06:01 UTC October 20, 2026

6. identified Oct 20, 2026, 02:34 PM UTC

   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 Oct 20, 2026, 03:26 PM UTC

   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 on it failed until workloads moved to the remaining availability zones. To limit further impact, we stopped placing new workloads in the affected zone and paused routine software updates in the region until the provider restored the zone. A root cause analysis (RCA) will be conducted and a summary will be made available within 10 business days.

8. postmortem Nov 03, 2026, 04:23 PM UTC

   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)

Read the full incident report →

Started Oct 19, 2026, 12:26 AM UTC· resolved Oct 19, 2026, 01:11 AM UTC

1. monitoring Oct 19, 2026, 12:26 AM UTC

   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 until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified regions who connect to Snowflake using private connectivity may have experienced intermittent failures when establishing new connections. Affected users may have seen some connection attempts fail while other attempts succeeded. Customers that are already connected were not impacted. Incident start time: 23:07 UTC October 18, 2026 Incident end time: 23:37 UTC October 18, 2026 Preliminary root cause: A third-party cloud platform experienced a network connectivity issue, which caused private connectivity connection failures in the affected region.

2. resolved Oct 19, 2026, 01:11 AM UTC

   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 who connect to Snowflake using private connectivity may have experienced intermittent failures when establishing new connections. Affected users may have seen some connection attempts fail while other attempts succeeded. Customers that are already connected were not impacted. Incident start time: 23:07 UTC October 18, 2026 Incident end time: 23:37 UTC October 18, 2026 Preliminary root cause: A third-party cloud platform experienced a network connectivity issue, which caused private connectivity connection failures in the affected region. A root cause analysis (RCA) will be conducted and a summary will be made available within 10 business days.

Read the full incident report →

Started Oct 16, 2026, 01:14 AM UTC· resolved Oct 16, 2026, 01:43 AM UTC

1. monitoring Oct 16, 2026, 01:14 AM UTC

   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 Snowsight performance have returned to normal. 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 experienced intermittent delays when loading Snowsight or running queries, and some queries may have failed. Workaround: There were no available workarounds for this issue. Incident start time: 23:50 UTC October 15, 2026 Incident end time: 00:40 UTC October 16, 2026 Preliminary root cause: A routine software update caused a large number of background setup operations to run at the same time, which exhausted the resources of a subset of infrastructure responsible for processing queries in the affected region, resulting in intermittent delays and query failures.

2. resolved Oct 16, 2026, 01:43 AM UTC

   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 specified regions may have experienced intermittent delays when loading Snowsight or running queries, and some queries may have failed. Workaround: There were no available workarounds for this issue. Incident start time: 23:50 UTC October 15, 2026 Incident end time: 00:40 UTC October 16, 2026 Preliminary root cause: A routine software update caused a large number of background setup operations to run at the same time, which exhausted the resources of a subset of infrastructure responsible for processing queries in the affected region, resulting in intermittent delays and query failures. A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.

3. postmortem Oct 23, 2026, 04:47 PM UTC

   [https://community.snowflake.com/s/article/INC20000287](https://community.snowflake.com/s/article/INC20000287)

Read the full incident report →

Started Oct 13, 2026, 03:53 PM UTC· resolved Oct 15, 2026, 09:51 PM UTC

1. investigating Oct 13, 2026, 03:53 PM UTC

   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 Oct 13, 2026, 04:40 PM UTC

   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 Oct 13, 2026, 05:38 PM UTC

   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 Oct 13, 2026, 06:36 PM UTC

   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 Oct 13, 2026, 08:06 PM UTC

   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 Oct 13, 2026, 09:47 PM UTC

   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 Oct 13, 2026, 11:54 PM UTC

   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. Incident start time: 10:58 UTC October 13, 2026 Preliminary root cause: A subset of infrastructure in the region experienced an issue that left the task metadata inconsistent. As a result, some tasks were reported as failed even though they completed successfully, while others remained pending or failed to start.

8. investigating Oct 14, 2026, 03:19 AM UTC

   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 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 mitigation: The next time each task runs, it may still be marked as failed with an internal error message even though its query ran successfully. This may happen up to one additional time per task. Customers may also 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 runs from after that time may not appear. - The INFORMATION_SCHEMA.COMPLETE_TASK_GRAPHS function may not include some recently completed runs. - The INFORMATION_SCHEMA.CURRENT_TASK_GRAPHS function may show extra rows for previously scheduled runs that are no longer running. - The SNOWFLAKE.ACCOUNT_USAGE.COMPLETE_TASK_GRAPHS view will continue to show history from before 10:58 UTC October 13, 2026, but some runs after that time may not appear. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: Before rerunning a task that was reported as failed, we recommend using the QUERY_HISTORY function or the SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY view to confirm whether the queries run by the task actually succeeded or failed. Incident start time: 10:58 UTC October 13, 2026 Preliminary root cause: A subset of infrastructure in the region experienced an issue that left the task metadata inconsistent. As a result, some tasks were reported as failed even though they completed successfully, while others remained pending or failed to start.

9. identified Oct 14, 2026, 09:47 PM UTC

   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 message, such as "Unexpected exception during task dispatch." After the mitigation: The next time each task runs, it may still be marked as failed with an internal error message even though its query ran successfully. This may happen up to one additional time per task. Customers may also 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 runs from after that time may not appear. - The INFORMATION_SCHEMA.COMPLETE_TASK_GRAPHS function may not include some recently completed runs. - The INFORMATION_SCHEMA.CURRENT_TASK_GRAPHS function may show extra rows for previously scheduled runs that are no longer running. - The SNOWFLAKE.ACCOUNT_USAGE.COMPLETE_TASK_GRAPHS view will continue to show history from before 10:58 UTC October 13, 2026, but some runs after that time may not appear. Workaround: Before rerunning a task that was reported as failed, we recommend using the QUERY_HISTORY function or the SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY view to confirm whether the queries run by the task actually succeeded or failed. If the queries failed, we recommend rerunning the task to bypass the impact. Incident start time: 10:58 UTC October 13, 2026 Preliminary root cause: A subset of infrastructure in the region experienced an issue that left the task metadata inconsistent. As a result, some tasks were reported as failed even though they completed successfully, while others remained pending or failed to start.

10. identified Oct 15, 2026, 04:57 AM UTC

    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 dispatch." After the mitigation: Tasks that haven't run since the infrastructure restarts may be marked as failed with an internal error message the next time they run, even though their queries run successfully. This may happen up to one additional time per task. Customers may also 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 runs from after that time may not appear. - The INFORMATION_SCHEMA.COMPLETE_TASK_GRAPHS function may not include some recently completed runs. - The INFORMATION_SCHEMA.CURRENT_TASK_GRAPHS function may show extra rows for previously scheduled runs that are no longer running. - The SNOWFLAKE.ACCOUNT_USAGE.COMPLETE_TASK_GRAPHS view will continue to show history from before 10:58 UTC October 13, 2026, but some runs after that time may not appear. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: Before rerunning a task that was reported as failed, we recommend using the QUERY_HISTORY function or the SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY view to confirm whether the queries run by the task actually succeeded or failed. If the queries failed, we recommend rerunning the task to bypass the impact. Incident start time: 10:58 UTC October 13, 2026 Preliminary root cause: A subset of infrastructure in the region experienced an issue that left the task metadata inconsistent. As a result, some tasks were reported as failed even though they completed successfully, while others remained pending or failed to start.

11. monitoring Oct 15, 2026, 09:03 PM UTC

    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 runs from after that time may not appear. - The INFORMATION_SCHEMA.COMPLETE_TASK_GRAPHS function may not include some recently completed runs. - The INFORMATION_SCHEMA.CURRENT_TASK_GRAPHS function may show extra rows for previously scheduled runs that are no longer running. - The SNOWFLAKE.ACCOUNT_USAGE.COMPLETE_TASK_GRAPHS view will continue to show history from before 10:58 UTC October 13, 2026, but some runs after that time may not appear. Incident start time: 10:58 UTC October 13, 2026 Incident end time: 17:35 UTC October 15, 2026 Preliminary root cause: Our investigation identified a metadata mismatch within the metadata database layer. As a result, some tasks were reported as failed even though they completed successfully, while others remained pending or failed to start.

12. resolved Oct 15, 2026, 09:51 PM UTC

    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 marked as failed with an internal error message even though its query ran successfully. This may have happened up to one additional time per task. 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 runs from after that time may not appear. - The INFORMATION_SCHEMA.COMPLETE_TASK_GRAPHS function may not include some recently completed runs. - The INFORMATION_SCHEMA.CURRENT_TASK_GRAPHS function may show extra rows for previously scheduled runs that are no longer running. - The SNOWFLAKE.ACCOUNT_USAGE.COMPLETE_TASK_GRAPHS view will continue to show history from before 10:58 UTC October 13, 2026, but some runs after that time may not appear. Incident start time: 10:58 UTC October 13, 2026 Incident end time: 17:35 UTC October 15, 2026 Preliminary root cause: Our investigation identified a metadata mismatch within the metadata database layer. As a result, some tasks were reported as failed even though they completed successfully, while others remained pending or failed to start. A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.

13. postmortem Oct 23, 2026, 08:17 PM UTC

    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)

Read the full incident report →

Started Oct 06, 2026, 02:44 PM UTC· resolved Oct 06, 2026, 03:57 PM UTC

1. investigating Oct 06, 2026, 02:44 PM UTC

   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 investigate the issue and will provide another update within 1 hour. Customer experience: Accounts hosted in Azure UAE North (azuaenorth) may see pages that load indefinitely. Customers in other deployments who connect from certain locations, including parts of the Middle East may see an “Origin is unreachable” error (Cloudflare error 523). This depends on where the user is connecting from, not on which region the account is hosted in. ETA: An ETA is not yet available. We'll provide one as soon as possible. because impact depends on where users connect from rather than where their account is hosted, we do not recommend failing over to another region, as it would not be expected to resolve the issue. Workaround: For customers affected by the "Origin is unreachable" error (Cloudflare error 523) when connecting from the Middle East or Israel, accessing Snowsight through a VPN that routes traffic through an exit location outside the affected area may restore access. Customers can also use programmatic access (drivers, connectors, SQL clients), which is not affected. Incident start time: 11:55 UTC October 06, 2026

2. monitoring Oct 06, 2026, 03:17 PM UTC

   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 properly. We’ll provide another update within 1 hour. Customer experience: Customers hosted in the specified regions may have seen pages that loaded indefinitely. Customers in other regions who connected from certain locations, including parts of the Middle East, may have seen an “Origin is unreachable” error. This depended on where the user was connecting from, not on which region the account was hosted in. Incident start time: 11:55 UTC October 06, 2026 Incident end time: 14:29 UTC October 06, 2026 Preliminary root cause: A network issue with a third-party edge network provider affected the routing of some Snowsight traffic between certain customer locations and the affected regions, resulting in pages that loaded indefinitely and connection errors.

3. resolved Oct 06, 2026, 03:57 PM UTC

   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 Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified regions may have seen pages that loaded indefinitely. Customers in other regions who connected from certain locations, including parts of the Middle East, may have seen an “Origin is unreachable” error. This depended on where the user was connecting from, not on which region the account was hosted in. Incident start time: 11:55 UTC October 06, 2026 Incident end time: 14:29 UTC October 06, 2026 Preliminary root cause: A network issue with a third-party edge network provider affected the routing of some Snowsight traffic between certain customer locations and the affected regions, resulting in pages that loaded indefinitely and connection errors. A root cause analysis (RCA) will be conducted and a summary will be made available within 10 business days.

4. postmortem Oct 21, 2026, 11:02 PM UTC

   [https://community.snowflake.com/s/article/INC20000263](https://community.snowflake.com/s/article/INC20000263)

Read the full incident report →

Started Sep 27, 2026, 02:15 AM UTC· resolved Sep 27, 2026, 03:16 AM UTC

1. monitoring Sep 27, 2026, 02:15 AM UTC

   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 services are functioning properly. Customer experience: Customers hosted in the specified regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data. Incident start time: 00:25 UTC September 27, 2026 Incident end time: 01:00 UTC September 27, 2026 Preliminary root cause: An issue with our third-party cloud platform caused impact to multiple Snowflake services and features. We have engaged with our third-party for further details.

2. resolved Sep 27, 2026, 03:16 AM UTC

   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 Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data. Incident start time: 00:25 UTC September 27, 2026 Incident end time: 01:00 UTC September 27, 2026 Preliminary root cause: An issue with our third-party cloud platform caused impact to multiple Snowflake services and features. We have engaged with our third-party for further details. A root cause analysis (RCA) will be conducted and a summary will be made available within 10 business days.

3. postmortem Oct 09, 2026, 09:55 AM UTC

   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)

Read the full incident report →

Started Sep 25, 2026, 11:00 PM UTC· resolved Sep 26, 2026, 12:20 AM UTC

1. investigating Sep 25, 2026, 11:00 PM UTC

   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, execute queries, or manage data, and may be unable to connect to Snowflake via private connectivity, such as AWS PrivateLink. Additionally, they may be unable to continuously stream data into Snowflake using Snowpipe Streaming.

2. monitoring Sep 25, 2026, 11:26 PM UTC

   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: Customers hosted in the specified regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data, and may have been unable to connect to Snowflake via private connectivity, such as AWS PrivateLink. Additionally, they may have been unable to continuously stream data into Snowflake using Snowpipe Streaming. Incident start time: 22:35 UTC September 25, 2026 Incident end time: 22:59 UTC September 25, 2026 Preliminary root cause: Our internal metadata database infrastructure in the affected region became unavailable, resulting in connectivity failures across multiple Snowflake services.

3. resolved Sep 26, 2026, 12:20 AM UTC

   Current status: We've implemented the fix for this issue and monitored the environment to confirm that service was restored. Most impact was resolved by 22:59 UTC, with the remaining backlog for scheduled and serverless task execution fully clearing by 23:43 UTC. 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 regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data, and may have been unable to connect to Snowflake via private connectivity, such as AWS PrivateLink. Additionally, they may have been unable to continuously stream data into Snowflake using Snowpipe Streaming, and customers using scheduled or serverless tasks may have experienced delayed task execution. Incident start time: 22:35 UTC September 25, 2026 Incident end time: 23:43 UTC September 25, 2026 Preliminary root cause: Our internal metadata database infrastructure in the affected region became unavailable, resulting in connectivity failures across multiple Snowflake services. A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.

4. postmortem Oct 02, 2026, 11:36 PM UTC

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

Read the full incident report →

Started Sep 14, 2026, 04:48 AM UTC· resolved Sep 14, 2026, 06:09 AM UTC

1. investigating Sep 14, 2026, 04:48 AM UTC

   Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 1 hour. Customer experience: Customers in the affected regions may experience performance degradation or issues logging into Snowflake, including delayed sign-ins, query execution failures, and errors managing data. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Workaround: There are currently no available workarounds for this issue. Incident start time: 23:35 UTC September 13, 2026

2. identified Sep 14, 2026, 05:18 AM UTC

   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: Customers hosted in the affected deployments may experience performance degradation or issues logging into Snowflake, including delayed sign-ins, and SSO login loops. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Workaround: There are currently no available workarounds for this issue. Incident start time: 23:35 UTC September 13, 2026

3. monitoring Sep 14, 2026, 05:40 AM UTC

   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: Customers hosted in the affected deployments may have experienced performance degradation or issues logging into Snowflake, including delayed sign-ins, and SSO login loops. Incident start time: 23:35 UTC September 13, 2026 Incident end time: 05:18 UTC September 14, 2026 Preliminary root cause: An update intended to improve authentication handling caused a subset of single sign-on (SSO) sign-in attempts across multiple regions to fail or loop, preventing affected users from logging in to Snowflake.

4. resolved Sep 14, 2026, 06:09 AM UTC

   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 affected deployments may have experienced performance degradation or issues logging into Snowflake, including delayed sign-ins, and SSO login loops. Incident start time: 22:22 UTC September 13, 2026 Incident end time: 05:18 UTC September 14, 2026 Preliminary root cause: An update intended to improve authentication handling caused a subset of single sign-on (SSO) sign-in attempts across multiple regions to fail or loop, preventing affected users from logging in to Snowflake. A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.

Read the full incident report →

Started Sep 11, 2026, 07:18 AM UTC· resolved Sep 11, 2026, 01:19 PM UTC

1. investigating Sep 11, 2026, 07:18 AM UTC

   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, execute queries, or manage data. Incident start time: 05:00 UTC September 11, 2026

2. investigating Sep 11, 2026, 07:44 AM UTC

   Current status: We're continuing to investigate the issue with Snowflake Data Cloud. We'll provide another 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, execute queries, or manage data. ETA: An ETA is not yet available. We'll provide one as soon as possible. Incident start time: 05:00 UTC September 11, 2026

3. investigating Sep 11, 2026, 08:12 AM UTC

   Current status: We're continuing to investigate the issue with Snowflake Data Cloud. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified region may be unable to sign in to Snowsight, and may receive an error message such as "Something went wrong." This issue is intermittent and does not affect all users; affected users may also experience issues executing queries or managing data. ETA: An ETA is not yet available. We'll provide one as soon as possible. Incident start time: 05:00 UTC September 11, 2026

4. identified Sep 11, 2026, 09:08 AM UTC

   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 60 minutes. Customer experience: Customers hosted in the specified region may be unable to sign in to Snowsight, and may receive an error message such as "Something went wrong." This issue is intermittent and does not affect all users; affected users may also experience issues executing queries or managing data. ETA: An ETA is not yet available. We'll provide one as soon as possible. Incident start time: 05:00 UTC September 11, 2026

5. monitoring Sep 11, 2026, 09:27 AM UTC

   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: Customers hosted in the specified region may have been unable to sign in to Snowsight, and may have receive an error message such as "Something went wrong." This issue was intermittent and did not affect all users; affected users may also have experienced issues executing queries or managing data. Incident start time: 05:00 UTC September 11, 2026 Incident end time: 08:45 UTC September 11, 2026 Preliminary root cause: A configuration update to infrastructure components responsible for authorizing incoming network traffic caused the components to restrict this traffic.

6. monitoring Sep 11, 2026, 11:24 AM UTC

   Current status: We've identified additional impact in the AWS - Asia Pacific (Tokyo) region, in which we've applied the same fix for this issue. 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 to sign in to Snowsight, and may have receive an error message such as "Something went wrong." This issue was intermittent and did not affect all users; affected users may also have experienced issues executing queries or managing data. Incident start time: 05:00 UTC September 11, 2026 Incident end time: 11:15 UTC September 11, 2026 Preliminary root cause: A configuration update to infrastructure components responsible for authorizing incoming network traffic caused the components to restrict this traffic.

7. resolved Sep 11, 2026, 01:19 PM UTC

   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 regions may have been unable to sign in to Snowsight, and may have receive an error message such as "Something went wrong." This issue was intermittent and did not affect all users; affected users may also have experienced issues executing queries or managing data. Incident start time: 05:00 UTC September 11, 2026 Incident end time: 11:15 UTC September 11, 2026 Preliminary root cause: A configuration update to infrastructure components responsible for authorizing incoming network traffic caused the components to restrict this traffic. A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.

8. postmortem Sep 18, 2026, 02:28 PM UTC

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

Read the full incident report →

Started Sep 09, 2026, 09:53 PM UTC· resolved Sep 09, 2026, 11:51 PM UTC

1. investigating Sep 09, 2026, 09:53 PM UTC

   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, execute queries, or manage data. Incident start time: 21:26 UTC September 09, 2026

2. identified Sep 09, 2026, 10:08 PM UTC

   Current status: We've identified the source of the issue, and we're implementing a fix to restore service. We'll provide another 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, execute queries, or manage data. ETA: Our current estimate is that service will be restored within 15-30 minutes. Incident start time: 21:26 UTC September 09, 2026

3. monitoring Sep 09, 2026, 10:48 PM UTC

   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: Customers hosted in the specified regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data. Workaround: There were no available workarounds for this issue. Incident start time: 21:26 UTC September 09, 2026 Incident end time: 21:55 UTC September 09, 2026 Preliminary root cause: A subset of our metadata database infrastructure became unavailable, resulting in failures across multiple Snowflake services.

4. resolved Sep 09, 2026, 11:51 PM UTC

   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 regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data. Workaround: There were no available workarounds for this issue. Incident start time: 21:26 UTC September 09, 2026 Incident end time: 21:55 UTC September 09, 2026 Preliminary root cause: A subset of our metadata database infrastructure became unavailable, resulting in failures across multiple Snowflake services. A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.

Read the full incident report →

Started Sep 04, 2026, 07:34 AM UTC· resolved Sep 04, 2026, 10:10 AM UTC

1. investigating Sep 04, 2026, 07:34 AM UTC

   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 Snowflake services and features using Snowsight. 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. Incident start time: 07:00 UTC September 04, 2026

2. investigating Sep 04, 2026, 08:05 AM UTC

   Current status: We're continuing to investigate the issue with Snowflake Data Cloud. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Workaround: There are currently no available workarounds for this issue. Incident start time: 07:00 UTC September 04, 2026

3. investigating Sep 04, 2026, 08:35 AM UTC

   Current status: We're continuing to actively investigate the issue with Snowflake Data Cloud. The specific focus at this time is on infrastructure components responsible for authorizing incoming traffic. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Workaround: There are currently no available workarounds for this issue. Incident start time: 07:00 UTC September 04, 2026

4. monitoring Sep 04, 2026, 09:04 AM UTC

   Current status: We've implemented the fix for this issue by rolling back a configuration update to the underlying infrastructure. Our telemetry and internal validations indicate that service has been restored. 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 to access or use Snowflake services and features using Snowsight. Workaround: There were no available workarounds for this issue. Incident start time: 07:00 UTC September 04, 2026 Incident end time: 08:30 UTC September 04, 2026 Preliminary root cause: A configuration update to infrastructure components responsible for authorizing incoming network traffic caused the components to restrict this traffic.

5. resolved Sep 04, 2026, 10:10 AM UTC

   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 regions may have been unable to access or use Snowflake services and features using Snowsight. Workaround: There were no available workarounds for this issue. Incident start time: 07:00 UTC September 04, 2026 Incident end time: 08:30 UTC September 04, 2026 Preliminary root cause: A configuration update to infrastructure components responsible for authorizing incoming network traffic caused the components to restrict this traffic. A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.

6. postmortem Sep 14, 2026, 10:14 PM UTC

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

Read the full incident report →

Started Sep 01, 2026, 09:58 AM UTC· resolved Sep 01, 2026, 01:50 PM UTC

1. investigating Sep 01, 2026, 09:58 AM UTC

   Current status: We're investigating an issue affecting sign-ins to Snowflake Cowork. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to sign in to Snowflake Cowork, and may see a message indicating that sign-in was unsuccessful. All other Snowflake features are not impacted. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Workaround: There are currently no available workarounds for this issue. Incident start time: 00:00 UTC September 01, 2026

2. identified Sep 01, 2026, 10:32 AM UTC

   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: Customers hosted in the specified regions may be unable to sign in to Snowflake Cowork, and may see a message indicating that sign-in was unsuccessful. All other Snowflake features are not impacted. 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. Incident start time: 00:00 UTC September 01, 2026

3. identified Sep 01, 2026, 11:36 AM UTC

   Current status: We've identified the source of the issue, and are continuing the deployment of the fix to restore service. The majority of our customers should now be able to sign back into Snowflake Cowork. We'll provide another update within 1 hour. Customer experience: Customers hosted in the specified regions may be unable to sign in to Snowflake Cowork, and may see a message indicating that sign-in was unsuccessful. All other Snowflake features are not impacted. 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. Incident start time: 00:00 UTC September 01, 2026

4. monitoring Sep 01, 2026, 12:44 PM UTC

   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: Customers hosted in the specified regions may have been unable to sign in to Snowflake Cowork, and may have seen a message indicating that sign-in was unsuccessful. All other Snowflake features were not impacted. Workaround: There were no available workarounds for this issue. Incident start time: 00:00 UTC September 01, 2026 Incident end time: 11:55 UTC September 01, 2026 Preliminary root cause: An update to the underlying database objects responsible for managing CoWork sign-on mechanisms experienced a configuration error which resulted in the symptoms observed.

5. resolved Sep 01, 2026, 01:50 PM UTC

   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 regions may have been unable to sign in to Snowflake Cowork, and may have seen a message indicating that sign-in was unsuccessful. All other Snowflake features were not impacted. Workaround: There were no available workarounds for this issue. Incident start time: 00:00 UTC September 01, 2026 Incident end time: 11:55 UTC September 01, 2026 Preliminary root cause: An update to the underlying database objects responsible for managing CoWork sign-on mechanisms experienced a configuration error which resulted in the symptoms observed. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

6. postmortem Sep 09, 2026, 11:25 AM UTC

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

Read the full incident report →

Started Aug 31, 2026, 05:20 PM UTC· resolved Aug 31, 2026, 07:44 PM UTC

1. investigating Aug 31, 2026, 05:20 PM UTC

   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, execute queries, or manage data.

2. identified Aug 31, 2026, 05:31 PM UTC

   Current status: We identified and have since reverted a problematic change as a potential mitigation. Initial telemetry indicates that the service is recovering. We will continue to monitor to confirm recovery. 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, execute queries, or manage data. ETA: Customers should be starting to see recovery, and our current estimate is that service will be restored within 1 hour.

3. identified Aug 31, 2026, 05:59 PM UTC

   Current status: We are continuing to monitor service recovery, and have confirmed that the majority of service impact has been resolved as of 17:25 UTC with some residual impact to Snowsight access and Snowpipe Streaming. 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, execute queries, or manage data. ETA: Most services have returned to a healthy state. We expect any residual impact to Snowsight access and Snowpipe Streaming to be resolved within the next hour. Incident start time: 16:58 UTC August 31, 2026

4. monitoring Aug 31, 2026, 06:45 PM UTC

   Current status: We've implemented a fix to address the residual impact, and 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 core Snowflake services and features, including signing in to Snowsight, executing queries, loading and unloading data, and using Snowpark Container Services. Some customers may have also experienced delays with Snowpipe Streaming ingestion and elevated error rates when accessing Snowsight. The majority of impact was resolved at 17:25 UTC; however, some customers may have continued to experience some residual errors or increased latency until approximately 18:10 UTC. Incident start time: 16:58 UTC August 31, 2026 Incident end time: 18:10 UTC August 31, 2026 Preliminary root cause: A recent change on the affected infrastructure inadvertently resulted in an increase in resource contention and subsequent impact to multiple Snowflake services and features.

5. resolved Aug 31, 2026, 07:44 PM UTC

   Current status: 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 Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified region may have been unable to access or use multiple core Snowflake services and features, including signing in to Snowsight, executing queries, loading and unloading data, and using Snowpark Container Services. Some customers may have also experienced delays with Snowpipe Streaming ingestion and elevated error rates when accessing Snowsight. The majority of impact was resolved at 17:25 UTC; however, some customers may have continued to experience some residual errors or increased latency until approximately 18:10 UTC. Incident start time: 16:58 UTC August 31, 2026 Incident end time: 18:10 UTC August 31, 2026 Preliminary root cause: A recent configuration change degraded backend processing due to a compatibility issue with how the affected systems handled requests. As a result, the infrastructure experienced resource contention and subsequent impact to multiple Snowflake services and features. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

6. postmortem Sep 09, 2026, 05:27 PM UTC

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

Read the full incident report →

Started Aug 27, 2026, 07:05 PM UTC· resolved Aug 27, 2026, 08:26 PM UTC

1. investigating Aug 27, 2026, 07:05 PM UTC

   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 connectivity issues when attempting to connect to Snowflake via private connectivity solutions, such as PrivateLink. Users may encounter connection errors or timeouts.

2. identified Aug 27, 2026, 07:22 PM UTC

   Current status: We've identified the source of the issue, and we're implementing a fix to restore service. We'll provide another update within 1 hour. Customer experience: Customers hosted in the specified regions may experience connectivity issues when attempting to connect to Snowflake via private connectivity solutions, such as PrivateLink. Users may encounter connection errors or timeouts. ETA: Our current estimate is that service will be fully restored within 1 hour. Incident start time: 18:21 UTC August 27, 2026

3. monitoring Aug 27, 2026, 07:54 PM UTC

   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: Customers hosted in the specified regions may have experienced connectivity issues when attempting to connect to Snowflake via private connectivity solutions, such as PrivateLink. Affected users may have encountered connection errors or timeouts. Incident start time: 18:21 UTC August 27, 2026 Incident end time: 19:34 UTC August 27, 2026 Preliminary root cause: A recent change intended to improve load balancer infrastructure health checks inadvertently introduced a configuration issue, which affected how private connectivity traffic was processed and resulted in connection failures. Once identified, we cycled the unhealthy infrastructure, restoring service.

4. resolved Aug 27, 2026, 08:26 PM UTC

   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 regions may have experienced connectivity issues when attempting to connect to Snowflake via private connectivity solutions, such as PrivateLink. Affected users may have encountered connection errors or timeouts. Incident start time: 18:21 UTC August 27, 2026 Incident end time: 19:34 UTC August 27, 2026 Preliminary root cause: A recent change intended to improve load balancer infrastructure health checks inadvertently introduced a configuration issue, which affected how private connectivity traffic was processed and resulted in connection failures. Once identified, we cycled the unhealthy infrastructure, restoring service. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

5. postmortem Sep 03, 2026, 09:03 PM UTC

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

Read the full incident report →

Started Aug 25, 2026, 03:53 AM UTC· resolved Aug 25, 2026, 04:35 AM UTC

1. investigating Aug 25, 2026, 03:53 AM UTC

   Current status: We're investigating an issue with Snowflake Data Cloud in the Southeast Asia region. We'll provide an update within 30 minutes. Customer experience: Customers hosted in the Southeast Asia region may be unable to access Snowflake services due to infrastructure connectivity issues. All other Snowflake features in other regions are not impacted. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Workaround: There are currently no available workarounds for this issue. Incident start time: 03:09 UTC August 25, 2026

2. monitoring Aug 25, 2026, 04:10 AM UTC

   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. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may have been unable to access Snowflake services due to infrastructure connectivity issues. All other Snowflake features in other regions were not impacted. Workaround: There were no available workarounds for this issue. Incident start time: 03:09 UTC August 25, 2026 Incident end time: 04:05 UTC August 25, 2026 Preliminary root cause: A third-party cloud platform experienced a virtual machine service issue, which caused infrastructure connectivity problems affecting Snowflake services in the region.

3. resolved Aug 25, 2026, 04:35 AM UTC

   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 Snowflake services due to infrastructure connectivity issues. All other Snowflake features in other regions were not impacted. Workaround: There were no available workarounds for this issue. Incident start time: 03:09 UTC August 25, 2026 Incident end time: 04:05 UTC August 25, 2026 Preliminary root cause: A third-party cloud platform experienced a virtual machine service issue, which caused infrastructure connectivity problems affecting Snowflake services in the region. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

4. postmortem Sep 03, 2026, 01:17 AM UTC

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

Read the full incident report →

Started Aug 24, 2026, 04:22 PM UTC· resolved Aug 24, 2026, 06:03 PM UTC

1. investigating Aug 24, 2026, 04:22 PM UTC

   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 access or use Snowflake services and features using Snowsight. Workaround: There are currently no available workarounds for this issue. Incident start time: 15:00 UTC August 24, 2026

2. identified Aug 24, 2026, 04:53 PM UTC

   Current status: We've identified an issue with a system configuration that is causing authentication problems in Snowsight, and we're developing and implementing a fix to restore service. We'll provide an update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to remain logged in to Snowsight, experiencing immediate logout after successful authentication. 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. Incident start time: 15:00 UTC August 24, 2026

3. identified Aug 24, 2026, 05:17 PM UTC

   Current status: We're in the process of implementing a fix for this issue. We'll provide an update within the next 60 minutes. Customer experience: Customers hosted in the specified region may be unable to remain logged in to Snowsight, experiencing immediate logout after successful authentication. An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are no available workarounds for this issue. Incident start time: 15:00 UTC August 24, 2026

4. monitoring Aug 24, 2026, 05:37 PM UTC

   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: Customers hosted in the specified region may have been unable to remain logged in to Snowsight, experiencing immediate logout after successful authentication. Workaround: There were no available workarounds for this issue. Incident start time: 14:47 UTC August 24, 2026 Incident end time: 17:21 UTC August 24, 2026 Preliminary root cause: A system configuration change caused an outdated application version to be deployed, resulting in authentication session failures. Once identified, the configuration was corrected to restore the proper application version.

5. resolved Aug 24, 2026, 06:03 PM UTC

   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 remain logged in to Snowsight, experiencing immediate logout after successful authentication. Incident start time: 14:47 UTC August 24, 2026 Incident end time: 17:21 UTC August 24, 2026 Preliminary root cause: A system configuration change caused an outdated application version to be deployed, resulting in authentication session failures. Once identified, the configuration was corrected to restore the proper application version. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

6. postmortem Aug 31, 2026, 10:54 PM UTC

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

Read the full incident report →

Started Aug 20, 2026, 01:47 PM UTC· resolved Aug 20, 2026, 03:43 PM UTC

1. investigating Aug 20, 2026, 01:47 PM UTC

   Current status: We're investigating an issue with Snowflake Data Cloud. We've engaged the associated Cloud Service Provider to investigate and troubleshoot this issue further. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may have been unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Workaround: There are currently no available workarounds for this issue. Incident start time: 13:25 UTC August 20, 2026

2. identified Aug 20, 2026, 02:19 PM UTC

   Current status: We're investigating an issue with Snowflake Data Cloud. We've engaged the associated Cloud Service Provider to investigate and troubleshoot this issue further. We'll provide an update within 30 minutes. Customer experience: Customers hosted in the specified regions may have been unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. ETA: An ETA is not yet available. We'll provide one as soon as possible. Incident start time: 13:25 UTC August 20, 2026

3. monitoring Aug 20, 2026, 02:39 PM UTC

   Current status: We've coordinated with our third-party cloud platform, which has implemented a mitigation for this issue. We will continue to monitor the environment until we're confident that all services are functioning properly. Customer experience: Customers hosted in the specified regions may have been unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. Other connection methods were unaffected. Incident start time: 13:25 UTC August 20, 2026 Incident end time: 14:10 UTC August 20, 2026 Preliminary root cause: A third-party cloud platform experienced a virtual networking infrastructure issue, preventing customers from connecting to Snowflake via private connectivity solutions, such as PrivateLink.

4. resolved Aug 20, 2026, 03:43 PM UTC

   Current status: The third-party cloud platform confirmed that the mitigation was complete, and its automated recovery system appears to have initiated. We independently monitored the environment and verified 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 regions may have been unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. Other connection methods were unaffected. Incident start time: 13:25 UTC August 20, 2026 Incident end time: 14:10 UTC August 20, 2026 Preliminary root cause: A third-party cloud platform experienced a virtual networking infrastructure issue, preventing customers from connecting to Snowflake via private connectivity solutions, such as PrivateLink. While we suspect that this issue may be a recurrence of a third-party cloud platform virtual networking problem, we remain closely engaged with our third-party cloud platform as they perform their own investigation into the underlying root cause of the issue. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 10 business days.

5. postmortem Sep 03, 2026, 08:06 PM UTC

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

Read the full incident report →

Started Aug 18, 2026, 12:58 PM UTC· resolved Aug 18, 2026, 02:51 PM UTC

1. investigating Aug 18, 2026, 12:58 PM UTC

   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 issues with AI and ML functionality. Specifically, when using Cortex Code in Snowsight, customer may see the following: “Internal Server error: You may need to start a new chat.”. All other Snowflake features are not impacted. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 11:10 UTC August 18, 2026

2. identified Aug 18, 2026, 01:33 PM UTC

   Current status: We've identified an issue with container scheduling in our compute infrastructure that is affecting AI and ML functionality, and we're implementing a fix to restore service. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to use Cortex Code in Snowsight and may see the following error message: "Internal Server error: You may need to start a new chat." All other Snowflake features are not impacted. ETA: Our current estimate is that service will be restored within 30 minutes. Incident start time: 11:20 UTC August 18, 2026 Preliminary root cause: Resource exhaustion in the compute infrastructure caused container scheduling failures, resulting in AI and ML functionality becoming unavailable.

3. monitoring Aug 18, 2026, 01:55 PM UTC

   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. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified region may have been unable to use Cortex Code in Snowsight and may have seen the following error message: "Internal Server error: You may need to start a new chat." All other Snowflake features are not impacted. Incident start time: 11:20 UTC August 18, 2026 Incident end time: 13:45 UTC August 18, 2026 Preliminary root cause: Resource exhaustion in the compute infrastructure caused container scheduling failures, resulting in AI and ML functionality becoming unavailable.

4. resolved Aug 18, 2026, 02:51 PM UTC

   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 regions may have experienced issues with AI and ML functionality. Specifically, when using Cortex Code in Snowsight, customers may have seen the following: “Internal Server error: You may need to start a new chat.” All other Snowflake features were not impacted. Incident start time: 11:20 UTC August 18, 2026 Incident end time: 13:45 UTC August 18, 2026 Preliminary root cause: Resource exhaustion in the compute infrastructure caused container scheduling failures, resulting in AI and ML functionality becoming unavailable. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

5. postmortem Aug 25, 2026, 10:42 PM UTC

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

Read the full incident report →

Started Aug 14, 2026, 05:29 PM UTC· resolved Aug 14, 2026, 07:35 PM UTC

1. investigating Aug 14, 2026, 05:29 PM UTC

   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 using Snowsight. Affected users may be unable to sign in and may observe "503 Service Unavailable" errors. Incident start time: 17:05 UTC August 14, 2026

2. identified Aug 14, 2026, 05:58 PM UTC

   Current status: We've identified a system configuration issue affecting Snowsight, and we're implementing a fix 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 Snowsight and may observe "503 Service Unavailable" errors. ETA: Our current estimate is that service will be restored within 30 minutes. Workaround: There are currently no available workarounds for this issue. Incident start time: 17:05 UTC August 14, 2026

3. monitoring Aug 14, 2026, 06:30 PM UTC

   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: Customers hosted in the specified region may have been unable to access or use Snowsight and may have seen "503 Service Unavailable" errors. Incident start time: 17:05 UTC August 14, 2026 Incident end time: 18:12 UTC August 14, 2026 Preliminary root cause: A routine system configuration change intended to optimize performance caused elevated latency in the metadata layer, resulting in service disruptions. Once identified, the configuration was reverted and affected service infrastructure was restarted to restore service.

4. resolved Aug 14, 2026, 07:35 PM UTC

   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 be unable to access or use Snowsight and may observe "503 Service Unavailable" errors. Incident start time: 17:05 UTC August 14, 2026 Incident end time: 18:12 UTC August 14, 2026 Preliminary root cause: A routine system configuration change intended to optimize performance caused elevated latency in the metadata layer, resulting in service disruptions. Once identified, the configuration was reverted and affected service infrastructure was restarted to restore service. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

5. postmortem Aug 21, 2026, 09:47 PM UTC

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

Read the full incident report →

Started Aug 14, 2026, 03:19 PM UTC· resolved Aug 14, 2026, 04:28 PM UTC

1. monitoring Aug 14, 2026, 03:19 PM UTC

   Current status: We've identified an issue that caused elevated error rates for Snowsight availability, and we've validated that service health has returned to normal following action by automated recovery systems. 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 experienced intermittent authentication failures and "service unavailable" errors between approximately 14:20 and 14:45 UTC. Incident start time: 14:20 UTC August 14, 2026 Incident end time: 14:45 UTC August 14, 2026 Preliminary root cause: A service infrastructure layer supporting authentication and session initiation for Snowsight entered an unhealthy state, causing login failures and service disruptions.

2. resolved Aug 14, 2026, 04:28 PM UTC

   Current status: 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 Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified region may have experienced intermittent authentication failures and "service unavailable" errors between approximately 14:20 and 14:45 UTC. Incident start time: 14:20 UTC August 14, 2026 Incident end time: 14:45 UTC August 14, 2026 Preliminary root cause: A service infrastructure layer supporting authentication and session initiation for Snowsight entered an unhealthy state, causing login failures and service disruptions. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

3. postmortem Aug 22, 2026, 02:37 AM UTC

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

Read the full incident report →

Started Aug 05, 2026, 02:41 PM UTC· resolved Aug 05, 2026, 03:49 PM UTC

1. investigating Aug 05, 2026, 02:41 PM UTC

   Current status: We're continuing to investigate the issue with Snowflake Data Cloud. We're investigating a portion of infrastructure that appears unhealthy to develop a mitigation plan. We'll provide another update within 1 hour. Customer experience: Customers hosted in the specified regions may be experiencing issues using CoCo through Snowsight. Users may receive an "Internal Server Error," when interacting with the service.

2. identified Aug 05, 2026, 03:00 PM UTC

   Current status: We've identified an issue with the underlying infrastructure supporting CoCo services, and we're implementing a fix to restore service. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to use CoCo services through Snowsight. Users may receive an "Internal Server Error" when interacting with the service. All other Snowflake features are not impacted. ETA: Our current estimate is that service will be restored within 30 minutes. Incident start time: 11:40 UTC August 05, 2026 Preliminary root cause: An underlying system component supporting CoCo services experienced failures, resulting in customer impact.

3. monitoring Aug 05, 2026, 03:14 PM UTC

   Current status: We've completed implementing our fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified region may have been intermittently unable to use CoCo services through Snowsight. Users may have received an "Internal Server Error" when interacting with the service. All other Snowflake features were not impacted. Incident start time: 11:40 UTC August 05, 2026 Incident end time: 15:00 UTC August 05, 2026 Preliminary root cause: An underlying system component supporting Cortex services experienced failures due to connectivity issues with the file system, resulting in intermittent customer impact.

4. resolved Aug 05, 2026, 03:49 PM UTC

   Current status: We've confirmed that this issue has been resolved, and we have monitored the environment to confirm that the affected functionality is now working as expected. 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 intermittently unable to use CoCo services through Snowsight. Users may have seen an "Internal Server Error" when interacting with the service. All other Snowflake features were not impacted. Incident start time: 11:40 UTC August 05, 2026 Incident end time: 15:00 UTC August 05, 2026 Preliminary root cause: An underlying system component supporting Cortex services experienced failures due to connectivity issues with the file system, resulting in intermittent customer impact. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

5. postmortem Aug 14, 2026, 06:58 AM UTC

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

Read the full incident report →