Skip to content
Snowflake · Data and observabilityJan 21, 2026, 19:23 UTC

AWS - US West (Oregon): INC0150359

CriticalCapacityUpdated 19h ago
Jan 21, 19:23 UTCJan 21, 21:57 UTC
Duration
2h 34m
Impact
Critical
Root cause
Capacity
Snowflake, 90 days
22 incidents
Affected
ApplicationsAWS - US West (Oregon) - ApplicationsAWS - US West (Oregon) - Databases, Tables, and Views
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/INC0150359-and-INC0150440](https://community.snowflake.com/s/article/INC0150359-and-INC0150440)

Timeline

  1. Postmortem · Jan 28, 23:57 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/INC0150359-and-INC0150440](https://community.snowflake.com/s/article/INC0150359-and-INC0150440)
  2. Resolved · Jan 21, 21:57 UTC
    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 access or use Snowflake services and features via Snowsight and may have experienced delays. Incident start time: 19:00 UTC January 21, 2026 Incident end time: 20:08 UTC January 21, 2026 Preliminary root cause: Our preliminary investigation identified that the Snowsight application-hosting layer and the Snowsight-specific database layer experienced an issue that led to an unexpected surge in requests, leading to high resource utilization and preventing the service from processing the associated traffic, resulting in suspended login attempts. A root cause analysis (RCA) document will be published within five business days.
  3. Monitoring · Jan 21, 20:57 UTC
    Current status: We've completed a restart on systems related to the application layer. Our telemetry indicates that this issue is no longer occurring, and users should be able to successfully access the service via the Snowsight User Interface (UI). 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 Snowflake services and features via Snowsight and may have experienced delays. Incident start time: 19:00 UTC January 21, 2026 Incident end time: 20:08 UTC January 21, 2026 Preliminary root cause: Our preliminary investigation identified that the Snowsight application-hosting layer and the Snowsight-specific database layer experienced an issue that led to an unexpected surge in requests, leading to high resource utilization and preventing the service from processing the associated traffic, resulting in suspended login attempts.
  4. Investigating · Jan 21, 20:14 UTC
    Current status: We have refined our understanding of how this issue manifests, and determined that it is isolated to Snowsight. Our investigation is currently focused on potential issues with the Snowsight application-hosting layer and the Snowsight-specific database layer. We're in the process of restarting systems related to the application layer and reverting any recent application releases that were in progress to mitigate the issue as quickly as possible. We will provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight and may experience delays. Incident start time: 19:00 UTC January 21, 2026
  5. Investigating · Jan 21, 19:33 UTC
    Current status: We're continuing to investigate the issue with Snowflake Data Cloud. We'll provide another 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.
  6. Investigating · Jan 21, 19:31 UTC
    Current status: We're continuing to investigate the issue with Snowflake Data Cloud. We'll provide another 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.
  7. Investigating · Jan 21, 19:23 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

Also caused by capacity and load

All
StartedIncidentDuration
Sep 2213:19 UTCWe are investigating an issue with CH servers in Azure germanywestcentral regionClickHouse5h 6m
Sep 1607:20 UTCDegradation with Gemini 3.8 FlashGitHub10h 28m
Sep 1509:47 UTCDisruption with some GitHub servicesGitHub1h 30m
Sep 422:02 UTCDegradation in repos contents APIGitHub21m
Sep 221:44 UTCElevated Linux worker queue timesExpo21m
Sep 115:00 UTCDelays in commit processingGitHub1h 1m

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.