AWS - US West (Oregon): INC0159680

What to do

• Check whether you use Snowflake Databases, Tables, and Views, Data Loading and Unloading in us. 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 51m it lasted.

  Anything that failed between 2026-06-22 20:35 UTC and 2026-06-23 00:26 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 7

1. investigatingJun 22, 2026, 8:35 PM UTC

   Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 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.

   provider

2. investigatingJun 22, 2026, 8:41 PM UTC

   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. Users may may experience delays or failures when using Snowpipe to ingest files.

   provider

3. investigatingJun 22, 2026, 9:10 PM UTC

   Current status: We've confirmed that this issue impacts service, and we're continuing to investigate to determine the source of the issue. 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 execute queries and tasks, or manage data. Users may may experience delays or failures when using Snowpipe to ingest files. Affected users may see a SQL execution internal error: Processing aborted due to error. Incident start time: 20:12 UTC June 22, 2026

   provider

4. investigatingJun 22, 2026, 9:48 PM UTC

   Current status: We are continuing to investigate the underlying source of the issue. In parallel, we are working to improve processing efficiency in a portion of our service infrastructure as a potential mitigation for the increased downstream load affecting related services. 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 execute queries and tasks, or manage data. Users may experience delays or failures with replication or when using Snowpipe to ingest files. Affected users may see a SQL execution internal error: Processing aborted due to error. Workaround: There are currently no available workarounds for this issue. An ETA is not yet available. We'll provide one as soon as possible. Incident start time: 20:12 UTC June 22, 2026

   provider

5. monitoringJun 22, 2026, 10:16 PM UTC

   Current status: We've completed actions to improve processing efficiency on the affected infrastructure and are seeing relief. We anticipate some customers may continue to experience latency as processing queues are resolved. 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 execute queries and tasks, or manage data. Users may have experienced delays or failures with replication or when using Snowpipe to ingest files. Affected users may have seen a SQL execution internal error: Processing aborted due to error. Incident start time: 20:12 UTC June 22, 2026 Incident end time: 21:45 UTC June 22, 2026 Preliminary root cause: Elevated load in a critical internal coordination service affected request processing for a subset of workloads. The underlying cause of the issue remains under investigation.

   provider

6. resolvedJun 23, 2026, 12:26 AM UTC

   Current status: We've monitored the environment to confirm our actions have restored service. 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, and may have experienced delays or failures with replication or when using Snowpipe to ingest files. Affected users may have been unable to execute queries and tasks or manage data, and may have seen a "Processing aborted due to error" SQL execution internal error. Incident start time: 20:12 UTC June 22, 2026 Incident end time: 21:45 UTC June 22, 2026 Preliminary root cause: Elevated load in a critical internal coordination service affected request processing for a subset of workloads. The underlying cause of the issue remains under investigation. A root cause analysis (RCA) document will be published within five business days.

   provider

7. postmortemJun 30, 2026, 7:16 PM UTC

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

   provider

Corrections

None so far.

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