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

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

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

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

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