What visitors reported during this incident
No visitor reports were filed for this incident.
Having problems with Snowflake now? Check the current statusAffected services
Updates (6)
- Sep 9, 2026, 11:25 AMINC20000190
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)
Snowflake ↗ - Sep 1, 2026, 01:50 PMINC20000190
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 Sep
Snowflake ↗ - Sep 1, 2026, 12:44 PMINC20000190
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 t
Snowflake ↗ - Sep 1, 2026, 11:36 AMINC20000190
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 workaro
Snowflake ↗ - Sep 1, 2026, 10:32 AMINC20000190
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
Snowflake ↗ - Sep 1, 2026, 09:58 AMINC20000190
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 is
Snowflake ↗
What to do next
- Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
- Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
- Watch the provider going forward. Follow Snowflake's status feed →
GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.