Skip to main content
Snowflake

INC20000190

Partial outage Lasted 3h 52m · started · Snowflake's page

Level
confirmed
Worst impact
Partial outage
Components
AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML, AI and ML
Down Index
32of 100

What to do

  • Check whether you use Snowflake AI and ML, AI and ML, AI and ML, AI and ML and 48 more. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 3h 52m it lasted.

    Anything that failed between 2026-09-01 09:58 UTC and 2026-09-01 13:50 UTC may need a replay.
  • Subscribe to Snowflake's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=snowflake works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Snowflake 6

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

    provider

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

    provider

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

    provider

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

    provider

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

    provider

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

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-312f40ec96

Is Snowflake still down?

No, this incident was resolved 2026-09-01 13:50 UTC. For Snowflake's live state, see https://down.guide/snowflake.

How long did it last?

3h 52m, from 2026-09-01 09:58 UTC to 2026-09-01 13:50 UTC, by the times Snowflake posted.

What was affected?

Snowflake named AI and ML, AI and ML, AI and ML, AI and ML and 48 more.

What caused it?

Snowflake hasn't published a root cause. If it does, it shows here.

Where does this come from?

Snowflake's official status page, https://status.snowflake.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.