Skip to content
Snowflake · Data and observabilityJun 22, 2026, 20:35 UTC

AWS - US West (Oregon): INC0159680

CriticalNot disclosedUpdated 19h ago
Jun 22, 20:35 UTCJun 23, 00:26 UTC
Duration
3h 51m
Impact
Critical
Root cause
Not disclosed
Snowflake, 90 days
22 incidents
Affected
Databases, Tables, and ViewsData Loading and UnloadingAWS - US West (Oregon) - Databases, Tables, and ViewsAWS - US West (Oregon) - Data Loading and Unloading
Status page

Final update

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)

Timeline

  1. Postmortem · Jun 30, 19:16 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)
  2. Resolved · Jun 23, 00:26 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.
  3. Monitoring · Jun 22, 22:16 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.
  4. Investigating · Jun 22, 21:48 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
  5. Investigating · Jun 22, 21:10 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
  6. Investigating · Jun 22, 20:41 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.
  7. Investigating · Jun 22, 20:35 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.

More from Snowflake

Full history
StartedIncidentDuration
Sep 1404:48 UTCINC200002171h 21m
Sep 1107:18 UTCINC200002136h 1m
Sep 921:53 UTCINC200002111h 58m
Sep 407:34 UTCINC200001992h 36m
Sep 109:58 UTCINC200001903h 52m
Aug 3117:20 UTCINC200001882h 24m

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.