Snowflake outage history

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.

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.

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.

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

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.

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

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.

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.

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.

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.

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.

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

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

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

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

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

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

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.

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.

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.

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.

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.

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

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.

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

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

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

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

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

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.

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.

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.

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.

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.

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.

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)

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

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.

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.

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

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.

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.

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)

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.

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.

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.

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)

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

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

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.

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.

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

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

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

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

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.

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.

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.

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)

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

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

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.

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.

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

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

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

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.

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.

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)

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

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

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

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.

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.

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)

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.

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.

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

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.

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.

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)

Current status: We've determined that a capacity constraint at our third-party cloud platform has limited the availability of compute resources in the specified region. We're actively working to identify and implement alternative compute options to reduce impact for affected customers while our third-party cloud platform works to restore availability. We are in continuous contact with our third-party cloud platform, and we'll provide another update within 24 hours. Customer experience: Customers hosted in the specified region may intermittently be unable to use Snowpark Container Services. Affected customers may experience failures or timeouts when running Snowpark Container Services workloads, such as starting or resuming Notebooks, or provisioning or resuming compute pools. Notebooks running on virtual warehouses are not affected. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: While we're focused on remediation, customers running Notebooks on virtual warehouses can delay migrating to Snowpark Container Services until this issue is resolved. Incident start time: 08:41 UTC August 09, 2026 Preliminary root cause: A capacity constraint at our third-party cloud platform is limiting the availability of compute resources in the affected region.

Current status: We're continuing to coordinate with our third-party cloud platform provider to restore the compute capacity needed for Snowpark Container Services in the specified region. In parallel, we are taking the following steps to mitigate impact: - We have implemented capacity prioritization measures to help ensure available resources are directed to Business Critical tier accounts. - We are working to expand the set of instance types available for compute pool provisioning through a software update, which is currently in an expedited release process. - We have paused non-essential maintenance operations and internal workloads in the affected region to preserve available capacity. While we are in continuous contact with the provider, we expect the provider efforts to continue into next week, as such, the next update will be on Monday August 31, end of business day. Customer experience: Customers hosted in the specified region may intermittently be unable to use Snowpark Container Services. Affected customers may experience failures, timeouts, or delays when running Snowpark Container Services workloads, such as starting or resuming Notebooks, or provisioning or resuming compute pools. Notebooks running on virtual warehouses are not affected. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: While we're focused on remediation, customers running Notebooks on virtual warehouses can delay migrating to Snowpark Container Services until this issue is resolved. Incident start time: 08:41 UTC August 09, 2026 Preliminary root cause: A third-party cloud platform experienced constrained compute capacity, which caused limited availability of compute resources in the specified region.

Current status: We have taken additional steps to preserve available compute resources in the specified region, including adjusting compute pool scaling to reduce non-essential resource consumption. We continue to prioritize available resources for Business Critical Edition accounts, and non-essential maintenance operations in the specified region remain paused. The software update to enable additional compute resources for Snowpark Container Services in the specified region is in the testing and validation stage. We continue to be in contact with our third-party cloud platform, and we'll provide another update by 00:00 UTC September 8, 2026. Customer experience: Customers hosted in the specified region may intermittently be unable to use Snowpark Container Services. Affected customers may experience failures, timeouts, or delays when running Snowpark Container Services workloads, such as starting or resuming Notebooks, or provisioning or resuming compute pools. Notebooks running on virtual warehouses are not affected. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: While we're focused on remediation, customers running Notebooks on virtual warehouses can delay migrating to Snowpark Container Services until this issue is resolved. Incident start time: 08:41 UTC August 09, 2026 Preliminary root cause: A third-party cloud platform experienced constrained compute capacity, which caused limited availability of compute resources in the specified region.

Current status: We've made additional adjustments to further reduce non-essential resource consumption and preserve available compute resources in the specified region. We're continuing to develop a software update to enable additional compute resources, and our other mitigation actions remain in place. We're also continuing to coordinate with our third-party cloud platform provider to restore the compute capacity needed for Snowpark Container Services. We'll provide another update within 7 days. Customer experience: Customers hosted in the specified region may intermittently be unable to use Snowpark Container Services. Affected customers may experience failures, timeouts, or delays when running Snowpark Container Services workloads, such as starting or resuming Notebooks, or provisioning or resuming compute pools. Notebooks running on virtual warehouses are not affected. ETA: Based on information from our third-party cloud platform provider, we expect this capacity constraint to persist for several more months. We'll provide an updated ETA as we receive more information. Workaround: While we're focused on remediation, customers running Notebooks on virtual warehouses can delay migrating to Snowpark Container Services until this issue is resolved. Incident start time: 08:41 UTC August 09, 2026 Preliminary root cause: A third-party cloud platform experienced constrained compute capacity, which caused limited availability of compute resources in the specified region.

Current status: Our third-party cloud platform provider has informed us that they expect to be able to provide additional capacity allocation by mid-October. In the meantime, we are working to preserve compute resources available to us, reduce non-essential resource consumption, and investigate any alternative methods to further reduce impact. Resource availability remains variable and correlated to overall demand, with some intermittent delays occurring during high-volume times. We'll provide another update by 23:00 UTC September 17, 2026. Customer experience: Customers hosted in the specified region may intermittently be unable to use Snowpark Container Services. Affected customers may experience failures, timeouts, or delays when running Snowpark Container Services workloads, such as starting or resuming Notebooks, or provisioning or resuming compute pools. Notebooks running on virtual warehouses are not affected. Additionally, starting from 04:00 UTC September 04, 2026, customers hosted in the specified region with workloads on second generation (Gen2) warehouses may experience delays or intermittent failures when resuming or starting virtual warehouses. This may result in longer than expected query run times or delays in completing data pipelines. Warehouses that are already running are largely unaffected. ETA: Based on information from our third-party cloud platform provider, we anticipate a solution in mid-October. Workaround: While we're focused on remediation, customers running Notebooks on virtual warehouses can delay migrating to Snowpark Container Services until this issue is resolved. For customers experiencing impact to virtual warehouses, and who have already performed a failover, we recommend remaining in the alternate region until we have received additional capacity allocation from the third-party provider. Customers who are continuing to experience impact to virtual warehouses may see additional relief by migrating workloads to first generation (Gen1) warehouses, which remain less impacted by this issue. Incident start time: 08:41 UTC August 09, 2026 Preliminary root cause: A third-party cloud platform provider is experiencing constrained compute capacity, affecting compute resource provisioning, and causing limited availability of compute resources as well as delays and intermittent failures when resuming or starting virtual warehouses in the specified region.

Current status: We've taken additional steps with our warehouse team to reduce provisioning latencies for virtual warehouses, and we've observed some improvement in provisioning latencies as a result. Resource availability remains variable and correlated to overall demand, with some intermittent delays occurring during high-volume times. We're continuing to work closely with our warehouse team to maintain available capacity and keep provisioning times low. Our third-party cloud platform provider has indicated that the additional compute capacity remains on track, and we're continuing to coordinate with them to restore the needed capacity. We'll provide another update within 7 days. Customer experience: Customers hosted in the specified region may intermittently be unable to use Snowpark Container Services. Affected customers may experience failures, timeouts, or delays when running Snowpark Container Services workloads, such as starting or resuming Notebooks, or provisioning or resuming compute pools. Notebooks running on virtual warehouses are not affected. Additionally, starting from 04:00 UTC September 04, 2026, customers hosted in the specified region with workloads on second generation (Gen2) warehouses may experience delays or intermittent failures when resuming or starting virtual warehouses. This may result in longer than expected query run times or delays in completing data pipelines. Warehouses that are already running are largely unaffected. ETA: Based on information from our third-party cloud platform provider, we expect additional compute resources to become available in the specified region by mid-October. We'll provide an updated ETA as we receive more information. Workaround: While we're focused on remediation, customers running Notebooks on virtual warehouses can delay migrating to Snowpark Container Services until this issue is resolved. For customers experiencing impact to virtual warehouses, and who have already performed a failover, we recommend remaining in the alternate region until we have received additional capacity allocation from the third-party provider. Customers who are continuing to experience impact to virtual warehouses may see additional relief by migrating workloads to first generation (Gen1) warehouses, which remain less impacted by this issue. Incident start time: 08:41 UTC August 09, 2026 Preliminary root cause: A third-party cloud platform provider is experiencing constrained compute capacity, affecting compute resource provisioning, and causing limited availability of compute resources as well as delays and intermittent failures when resuming or starting virtual warehouses in the specified region.

Current status: We've received an update from our third-party cloud provider that improvement for resource availability in this region is now projected by the end of October. In the meantime, we’re continuing our efforts to reduce virtual warehouse provisioning times, building on measures that have already shown improvement. In parallel, we’re preserving available compute resources and continuing to closely coordinate with our third-party cloud provider on resource availability updates in the specified region. Resource availability continues to vary with demand, and provisioning delays or failures may still occur. We’ll provide another update within 7 days. Customer experience: Over the past few weeks, we've seen periods of fewer failures as we continue working to preserve available compute resources. However, resource availability at our third-party cloud provider remains constrained. Customers in the specified region may still encounter failures, timeouts, or delays when running Snowpark Container Services workloads, including starting or resuming Notebooks and provisioning or resuming compute pools. Creating additional workloads in new accounts adds to demand for these limited resources. Customers setting up Snowpark Container Services services or jobs, or Openflow runtimes, in those accounts may therefore encounter more frequent provisioning failures or be unable to complete setup. Customers using second generation (Gen2) warehouses may also continue to experience delays or intermittent failures when starting or resuming their warehouses, which can extend query run times or delay completion of data pipelines. ETA: Our third-party cloud platform provider remains committed to making additional compute resources available, which are now projected to be ready by late-October. We'll provide an updated ETA if that timeline changes. Workaround: Customers running Notebooks on virtual warehouses can delay migrating to Snowpark Container Services until this issue is resolved. Customers experiencing virtual warehouse resume delays can migrate affected warehouses to first generation (Gen1) using ALTER WAREHOUSE SET GENERATION = '1';. Gen1 warehouses are not affected by this capacity constraint. This is a short-term mitigation; Gen1 capacity is limited and performance characteristics may differ. There are currently no general workarounds available for Snowpark Container Services compute pool impact. Customers with specific compute pool failures should contact Snowflake Support for case-by-case assistance. Incident start time: 08:41 UTC August 09, 2026 Preliminary root cause: A third-party cloud platform experienced constrained compute capacity, causing limited availability of compute resources for Snowpark Container Services and delays or failures when provisioning or resuming virtual warehouses in the specified region.

Current status: Since our last update, we have seen periods of improved provisioning performance while preserving available compute resources and coordinating closely with our third-party cloud provider. Resource availability remains constrained and variable, and provisioning delays or failures may still occur. The provider continues to project improved resource availability in the specified region by the end of October. We will provide another update within 7 days, or sooner if there is a material change. Customer experience: Customers in the specified region may still encounter delays, timeouts, or failures when running Snowpark Container Services workloads, including starting or resuming Notebooks, provisioning or resuming compute pools, and setting up OpenFlow runtimes. Virtual Warehouses: Customers using second generation (Gen2) warehouses may experience delays or intermittent failures when starting or resuming their warehouses, which can extend query run times or delay completion of data pipelines. Warehouses that are already running are generally less affected. ETA: Based on information from our third-party cloud platform provider, we currently expect additional compute resources to become available in the specified region by late October, although the benefit may vary by workload. We'll provide an updated ETA if that timeline changes. Workaround: While we remain focused on reducing provisioning times and building on measures that have already shown improvement, we recommend the following actions, where feasible for affected customers. -Delay migrating warehouse-based Notebooks to SPCS where possible. -For customers experiencing Gen2 warehouse start or resume delays, and where appropriate for their workload, moving the affected warehouse to Gen1 may provide short-term relief. Gen1 warehouses are not affected by this capacity constraint, but Gen1 capacity is limited and performance characteristics may differ. -Contact Snowflake Support for case-by-case assistance with SPCS compute-pool failures. Incident start time: 08:41 UTC August 09, 2026 Preliminary root cause: A third-party cloud platform is experiencing constrained compute capacity in the specified region, limiting the availability of compute resources for Snowpark Container Services and causing delays or failures when provisioning or resuming virtual warehouses.

Current status: Since our last update, capacity availability and provisioning performance for virtual warehouses have materially improved. Additional capacity has become available in the region, and Snowflake has increased the resources reserved for customer workloads. We are continuing to monitor warehouse capacity and provisioning performance through periods of peak demand. Snowpark Container Services remains subject to capacity constraints. We continue to preserve available resources, coordinate with our third-party cloud provider, and work on additional capacity options. We are not yet declaring the broader incident resolved because SPCS workloads that require new capacity may still be affected. We will provide another update within 7 days, or sooner if there is a material change. Customer experience: Customers using virtual warehouses should see improved availability when starting or resuming warehouses. Residual delays or intermittent failures may still occur while we validate the improvement under sustained demand. Customers with continued warehouse reliability issues should contact Snowflake Support for case-by-case assistance. Customers using Snowpark Container Services may still encounter delays, timeouts, or failures when starting or resuming Notebooks, provisioning or resuming compute pools, or setting up OpenFlow runtimes. The remaining risk is concentrated in workloads that require new capacity; existing workloads continue to run normally. ETA: We continue to expect additional compute resources to become available in the specified region by late October. Warehouse capacity is currently in an improved state, and we will continue monitoring before declaring the warehouse impact resolved. For Snowpark Container Services, the timing of meaningful customer impact improvement remains dependent on the availability of those resources and service readiness to use them. We will provide an updated ETA if the timeline changes. Workaround: For virtual warehouses, we are no longer recommending a broad migration to Gen1 as a workaround for this incident. Customers who previously moved affected warehouses to Gen1 may work with Snowflake Support or their account team to evaluate returning to Gen2 based on current capacity, workload requirements, and observed reliability. Gen1 remains a possible short-term mitigation for customers who continue to experience verified Gen2 reliability issues, but performance and cost characteristics may differ. Customers running warehouse-based Notebooks may continue to defer migration to Snowpark Container Services where feasible. There is currently no general workaround for Snowpark Container Services compute pool impact; customers experiencing specific failures should contact Snowflake Support. Incident start time: 08:41 UTC August 09, 2026 Preliminary root cause: A third-party cloud platform is experiencing constrained compute capacity in the specified region, limiting the availability of compute resources for Snowpark Container Services and causing delays or failures when provisioning or resuming virtual warehouses.

Current status: Since our last update, we have seen improvement in Snowpark Container Services availability. Additional capacity became available in the specified region and has been reserved for customer workloads. Virtual warehouse capacity and provisioning performance also remain improved. We continue to monitor both services through periods of peak demand and are coordinating with our third-party cloud provider on additional capacity. While we have seen significant improvement across all affected services, workloads that require additional new capacity may still be affected, so we are continuing to monitor resource availability until the issue is fully resolved. We will provide another update within 7 days, or sooner if there is a material change. Customer experience: Customers using Snowpark Container Services should see improved ability to start or resume current supported workloads. However, delays, timeouts, or failures may still occur for workloads that require additional new capacity, including starting or resuming Notebooks, provisioning or resuming compute pools, or setting up OpenFlow runtimes. Existing workloads generally continue to run normally. Customers using virtual warehouses should continue to see improved availability when starting or resuming warehouses. Residual delays or intermittent failures may still occur while we validate the improvement under sustained demand. Customers with continued warehouse reliability issues should contact Snowflake Support for case-by-case assistance. ETA: We continue to expect additional compute resources to become available in the specified region by late October. The capacity currently available has improved service conditions, but the remaining risk will not be considered resolved until resource availability is sustained and customer impact remains mitigated. We will provide an updated ETA if the timeline changes. Workaround: For virtual warehouses, we are no longer recommending a broad migration to Gen1 as a workaround for this incident. Customers who previously moved affected warehouses to Gen1 may work with Snowflake Support or their account team to evaluate returning to Gen2 based on current capacity, workload requirements, and observed reliability. Gen1 remains a possible short-term mitigation for customers who continue to experience verified Gen2 reliability issues, but performance and cost characteristics may differ. Customers running warehouse-based Notebooks may continue to defer migration to Snowpark Container Services where feasible. There is currently no general workaround for Snowpark Container Services compute pool impact; customers experiencing specific failures should contact Snowflake Support. Incident start time: 08:41 UTC August 09, 2026 Preliminary root cause: A third-party cloud platform is experiencing constrained compute capacity in the specified region, limiting the availability of compute resources for Snowpark Container Services and causing delays or failures when provisioning or resuming virtual warehouses.

Current status: Virtual warehouse capacity and provisioning have remained stable, and we do not expect further broad risk to customer workloads, but we will continue monitoring through periods of peak demand. Snowpark Container Services (SPCS) remains subject to capacity constraints. We continue to preserve available resources, coordinate with our third-party cloud provider, and work on additional capacity options. We have seen improvement, but workloads that require additional new capacity may still be affected. We continue to target late October before considering the SPCS impact mitigated, subject to sustained resource availability and service readiness. We will provide another update within seven days, or sooner if there is a significant change. Customer experience: Customers using virtual warehouses should no longer experience the broader provisioning impact associated with this incident. Customers with continuing or customer-specific reliability issues should contact Snowflake Support for assistance. Customers using Snowpark Container Services may still encounter delays, timeouts, or failures when starting or resuming Notebooks, provisioning or resuming compute pools, or setting up OpenFlow runtimes. The remaining risk is concentrated in workloads that require additional new capacity; existing workloads generally continue to run normally. ETA: We have seen sustained stability in virtual warehouse capacity and provisioning since October 7, 2026. For Snowpark Container Services, we continue to target late October for mitigation as additional capacity and service readiness are validated. We will provide an updated ETA if that timeline changes. Workaround: For virtual warehouses, we are no longer recommending a broad migration to Gen1 as a workaround for this incident. Customers who previously moved affected warehouses to Gen1 may work with Snowflake Support or their account team to evaluate returning to Gen2. There is currently no general workaround for Snowpark Container Services compute pool impact; customers experiencing specific failures should contact Snowflake Support. Impact start time: 08:41 UTC August 09, 2026 Preliminary root cause: A third-party cloud platform is experiencing constrained compute capacity in the specified region, limiting the availability of compute resources for Snowpark Container Services and causing delays or failures when provisioning or resuming virtual warehouses.

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.

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

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.

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.

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)

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

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.

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.

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)

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

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

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

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.

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.

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)

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

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

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.

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.

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)