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

- Impact (vendor’s label): critical
- Status: postmortem
- Started: 2026-03-21 06:38 UTC · Resolved: 2026-03-21 07:12 UTC · Duration: 34 min
- Updates: 5 · Affected components: AWS - US West (Oregon) - Security and Privacy Features, Security and Privacy Features, Alerts and Notifications, AWS - US West (Oregon) - Alerts and Notifications, AI and ML, AWS - US West (Oregon) - AI and ML, Applications, AWS - US West (Oregon) - Applications, AWS - US West (Oregon) - Developer Tools, Developer Tools, AWS - US West (Oregon) - Data Loading and Unloading, Data Loading and Unloading, AWS - US West (Oregon) - Listings and Collaboration, Listings and Collaboration, AWS - US West (Oregon) - Organization and Account Management, Organization and Account Management, AWS - US West (Oregon) - Snowpark Container Services, Snowpark Container Services, AWS - US West (Oregon) - Databases, Tables, and Views, Databases, Tables, and Views, AWS - US West (Oregon) - Virtual Warehouses, Virtual Warehouses, AWS - US West (Oregon) - Business Continuity, Business Continuity
- [Vendor status page: https://stspg.io/c1z3lsygvcgc](https://stspg.io/c1z3lsygvcgc)
- [Company: Snowflake](https://rewindex.com/company/snowflake.md)

## Summary

Snowflake reported a critical outage in AWS - US West (Oregon), potentially preventing sign-ins, queries, and data management. The vendor reported onset at 05:31 UTC March 21, 2026; the archived duration was 34 min, with resolution at 2026-03-21 07:12 UTC after Snowflake implemented a fix and confirmed service restoration. _(machine-written, sol)_
## Timeline of updates

- **investigating** 2026-03-21 06:02 UTC: \<b\>Current status:\</b\> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 30 minutes. \<b\>Customer experience:\</b\> 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. \<b\>Incident start time:\</b\> 05:31 UTC March 21, 2026
- **identified** 2026-03-21 06:23 UTC: \<b\>Current status:\</b\> We've identified the source of the issue, and we're developing and implementing a fix to restore service. We'll provide another update within 30 minutes. \<b\>Customer experience:\</b\> 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. \<b\>ETA:\</b\> An ETA is not yet available. We'll provide one as soon as possible. \<b\>Incident start time:\</b\> 05:31 UTC March 21, 2026
- **monitoring** 2026-03-21 06:38 UTC: \<b\>Current status:\</b\> We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. \<b\>Customer experience:\</b\> 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 sign in, execute queries, or manage data. Users would have encountered HTTP 404 or other similar errors. \<b\>Incident start time:\</b\> 05:27 UTC March 21, 2026 \<b\>Incident end time:\</b\> 06:18 UTC March 21, 2026 \<b\>Preliminary root cause:\</b\> The investigation determined that infrastructure responsible for high-level traffic routing and name resolution became degraded, which caused customers to encounter HTTP 404 errors when attempting to access or use certain Snowflake services.
- **resolved** 2026-03-21 07:12 UTC: \<b\>Current status:\</b\> 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. \<b\>Customer experience:\</b\> 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 sign in, execute queries, or manage data. Users would have encountered HTTP 404 or other similar errors. \<b\>Incident start time:\</b\> 05:27 UTC March 21, 2026 \<b\>Incident end time:\</b\> 06:18 UTC March 21, 2026 \<b\>Preliminary root cause:\</b\> The investigation determined that infrastructure responsible for high-level traffic routing and name resolution became degraded, which caused customers to encounter HTTP 404 errors when attempting to access or use certain Snowflake services. A root cause analysis (RCA) document will be published within five business days.
- **postmortem** 2026-03-27 23:14 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/INC0154019\](https://community.snowflake.com/s/article/INC0154019)

## Rewindex changes for this incident

- 2026-03-21 06:38 UTC: [Critical incident: AWS - US West (Oregon): INC0154019](https://rewindex.com/change/i5a5d79519c4884.md)


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