Skip to main content
Snowflake

INC20000168

Partial outage Lasted 1h 56m · started · Snowflake's page

Level
confirmed
Worst impact
Partial outage
Components
Security and Privacy Features
Down Index
29of 100

What to do

  • Check whether you use Snowflake Security and Privacy Features. 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 1h 56m it lasted.

    Anything that failed between 2026-08-20 13:47 UTC and 2026-08-20 15:43 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 5

  1. investigating

    Current status: We're investigating an issue with Snowflake Data Cloud. We've engaged the associated Cloud Service Provider to investigate and troubleshoot this issue further. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may have been unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. 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: 13:25 UTC August 20, 2026

    provider

  2. identified

    Current status: We're investigating an issue with Snowflake Data Cloud. We've engaged the associated Cloud Service Provider to investigate and troubleshoot this issue further. We'll provide an update within 30 minutes. Customer experience: Customers hosted in the specified regions may have been unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. ETA: An ETA is not yet available. We'll provide one as soon as possible. Incident start time: 13:25 UTC August 20, 2026

    provider

  3. monitoring

    Current status: We've coordinated with our third-party cloud platform, which has implemented a mitigation for this issue. We will continue to monitor the environment until we're confident that all services are functioning properly. Customer experience: Customers hosted in the specified regions may have been unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. Other connection methods were unaffected. Incident start time: 13:25 UTC August 20, 2026 Incident end time: 14:10 UTC August 20, 2026 Preliminary root cause: A third-party cloud platform experienced a virtual networking infrastructure issue, preventing customers from connecting to Snowflake via private connectivity solutions, such as PrivateLink.

    provider

  4. resolved

    Current status: The third-party cloud platform confirmed that the mitigation was complete, and its automated recovery system appears to have initiated. We independently monitored the environment and verified 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 connect to Snowflake via private connectivity solutions, such as PrivateLink. Other connection methods were unaffected. Incident start time: 13:25 UTC August 20, 2026 Incident end time: 14:10 UTC August 20, 2026 Preliminary root cause: A third-party cloud platform experienced a virtual networking infrastructure issue, preventing customers from connecting to Snowflake via private connectivity solutions, such as PrivateLink. While we suspect that this issue may be a recurrence of a third-party cloud platform virtual networking problem, we remain closely engaged with our third-party cloud platform as they perform their own investigation into the underlying root cause of the issue. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 10 business days.

    provider

  5. 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/INC20000168](https://community.snowflake.com/s/article/INC20000168)

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

Is Snowflake still down?

No, this incident was resolved 2026-08-20 15:43 UTC. For Snowflake's live state, see https://down.guide/snowflake.

How long did it last?

1h 56m, from 2026-08-20 13:47 UTC to 2026-08-20 15:43 UTC, by the times Snowflake posted.

What was affected?

Snowflake named Security and Privacy Features.

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.