# Snowflake: AWS - US West (Oregon): INC0150359

- Impact (vendor’s label): critical
- Status: resolved
- Started: 2026-01-21 19:23 UTC · Resolved: 2026-01-21 21:57 UTC · Duration: 2.6 h
- Updates: 1
- [Vendor status page: https://status.snowflake.com/incidents/s2j1bnnjshl4](https://status.snowflake.com/incidents/s2j1bnnjshl4)
- [Company: Snowflake](https://rewindex.com/company/snowflake.md)

## Timeline of updates

- **resolved** 2026-01-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.

_From the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._


---
Canonical: https://rewindex.com/company/snowflake/incidents/s2j1bnnjshl4 · Markdown: https://rewindex.com/company/snowflake/incidents/s2j1bnnjshl4.md · JSON: https://rewindex.com/api/v1/companies/snowflake/incidents/s2j1bnnjshl4 · Generated 2026-10-18T10:39:40.451Z