What visitors reported during this incident
No visitor reports were filed for this incident.
Having problems with Snowflake now? Check the current statusAffected services
Updates (5)
- Mar 27, 2026, 11:14 PMAWS - US West (Oregon): INC0154019
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)
Snowflake ↗ - Mar 21, 2026, 07:12 AMAWS - US West (Oregon): INC0154019
<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>
Snowflake ↗ - Mar 21, 2026, 06:38 AMAWS - US West (Oregon): INC0154019
<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 ca
Snowflake ↗ - Mar 21, 2026, 06:23 AMAWS - US West (Oregon): INC0154019
<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
Snowflake ↗ - Mar 21, 2026, 06:02 AMAWS - US West (Oregon): INC0154019
<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
Snowflake ↗
What to do next
- Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
- Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
- Watch the provider going forward. Follow Snowflake's status feed →
GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.