Snowflake reports multiple service issues

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.

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: 04: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 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: 04: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: 04:00 UTC September 01, 2026

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: 04:00 UTC September 01, 2026

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 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.

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 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 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'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'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'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.