Companies / Snowflake / incidents
Snowflake: INC20000190
Snowflake reported a major incident in which customers in the listed AWS, Azure and GCP regions could be unable to sign in to Snowflake Cowork. It started at 2026-09-01 09:58 UTC and was resolved at 2026-09-01 13:50 UTC. All other Snowflake features were unaffected; Snowflake identified the source but did not specify the cause or fix.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Affected components: AI and MLGCP - US Central 1 (Iowa) - AI and MLAI and MLAWS - Asia Pacific (Singapore) - AI and MLAI and MLAzure - Central India (Pune) - AI and MLAI and MLAWS - Asia Pacific (Seoul) - AI and MLAI and MLAWS - Asia Pacific (Jakarta) - AI and MLAI and MLAzure - Southeast Asia (Singapore) - AI and MLAI and MLAzure - Central Korea (Seoul) - AI and MLAI and MLAWS - US West (Oregon) - AI and MLAI and MLAWS - US West (Commercial Gov - Oregon) - AI and MLAI and MLGCP - US East 4 (N. Virginia) - AI and MLAI and MLGCP - Europe West 2 (London) - AI and MLAI and MLAzure - West US 2 (Washington) - AI and MLAI and MLAzure - US Gov (Virginia) - AI and MLAI and MLAWS - Europe (Ireland) - AI and MLAI and MLAWS - Asia Pacific (New Zealand) - AI and MLAI and MLGCP - Europe West 3 (Frankfurt) - AI and MLAI and MLGCP - Middle East (Dammam) - AI and MLAI and MLAWS - Europe (Paris) - AI and MLAI and MLAWS - Asia Pacific (Thailand) - AI and MLAI and MLAWS - Europe (Frankfurt) - AI and MLAI and MLAWS - GovCloud (US-West) - AI and MLAI and MLAzure - East US (Virginia) - AI and MLAI and MLAzure - East US 2 (Virginia) - AI and MLAI and MLAzure - UK South (London) - AI and MLAI and MLAWS - GovCloud (US-East) - AI and MLAI and MLAWS - US East (N. Virginia) - AI and MLAI and MLAWS - Europe (Zürich) - AI and MLAI and MLAzure - South Central US (Texas) - AI and MLAI and MLAzure - North Europe (Ireland) - AI and MLAI and MLAzure - Sweden Central (Gävle) - AI and MLAI and MLAzure - Japan East (Tokyo, Saitama) - AI and MLAI and MLAWS - Europe (London) - AI and MLAI and MLAWS - Asia Pacific (Sydney) - AI and MLAI and MLAzure - UAE North (Dubai) - AI and MLAI and MLAzure - West Europe (Netherlands) - AI and MLAI and MLGCP - Europe West 4 (Eemshaven) - AI and MLAI and MLAzure - Australia East (New South Wales) - AI and MLAI and MLAWS - South America (São Paulo) - AI and MLAI and MLAzure - Mexico (Central) - AI and MLAI and MLAWS - Canada (Central) - AI and MLAI and MLAWS - Africa (Cape Town) - AI and MLAI and MLAzure - Switzerland North (Zürich) - AI and MLAI and MLAWS - Asia Pacific (Osaka) - AI and MLAI and MLAzure - Central US (Iowa) - AI and MLAI and MLAWS GovCloud - DoD - AI and MLAI and MLAWS - US East (Ohio) - AI and MLAI and MLAWS - Asia Pacific (Mumbai) - AI and MLAI and MLAWS - Europe (Stockholm) - AI and MLAI and MLAzure - Canada Central (Toronto) - AI and MLAI and MLAWS - Asia Pacific (Tokyo) - AI and MLAI and MLAWS - Asia Pacific (Malaysia) - AI and MLAI and MLGCP - Australia Southeast 2 (Melbourne) - AI and ML
Timeline of updates
- investigating
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
- identified
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
- identified
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
- monitoring
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.
- resolved
Current status: We've implemented the fix for this issue and monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer 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.
- postmortem
Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC20000190](https://community.snowflake.com/s/article/INC20000190)
Rewindex changes for this incident
- Major incident: INC20000190 2026-09-01 09:58 UTC
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Snowflake profile · Recent Snowflake incidents · Markdown · JSON