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

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

## Timeline of updates

- **resolved** 2026-01-22 23:24 UTC: Current status: Our observations of service telemetry continue to indicate that our service has recovered following the restart of the systems related to the Snowsight application-hosting layer. 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 using Snowsight or may have experienced delays. A subset of customers may have encountered errors while executing queries and other related operations. Incident start time: 19:02 UTC January 22, 2026 Incident end time: 19:30 UTC January 22, 2026 Preliminary root cause: While we're continuing to investigate to determine the underlying root cause of this issue, we suspect that a recent change made to our internal monitoring systems may have resulted in the problem with the Snowsight application-hosting layer. 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/0w11t7x10rzg · Markdown: https://rewindex.com/company/snowflake/incidents/0w11t7x10rzg.md · JSON: https://rewindex.com/api/v1/companies/snowflake/incidents/0w11t7x10rzg · Generated 2026-10-18T09:58:50.564Z