# Snowflake: AWS - Europe (Zürich): INC0153183

- Impact (vendor’s label): major
- Status: postmortem
- Started: 2026-03-07 20:05 UTC · Resolved: 2026-03-07 22:20 UTC · Duration: 2.2 h
- Updates: 5 · Affected components: AWS - Europe (Zürich) - Security and Privacy Features, Security and Privacy Features, AWS - Europe (Zürich) - Virtual Warehouses, Virtual Warehouses, AWS - Europe (Zürich) - Listings and Collaboration, Listings and Collaboration, AWS - Europe (Zürich) - Snowflake Postgres, Snowflake Postgres, AWS - Europe (Zürich) - Developer Tools, Developer Tools, AWS - Europe (Zürich) - Snowpark Container Services, Snowpark Container Services, AWS - Europe (Zürich) - Business Continuity, Business Continuity, AI and ML, AWS - Europe (Zürich) - AI and ML, AWS - Europe (Zürich) - Data Loading and Unloading, Data Loading and Unloading, Alerts and Notifications, AWS - Europe (Zürich) - Alerts and Notifications, AWS - Europe (Zürich) - Organization and Account Management, Organization and Account Management, Applications, AWS - Europe (Zürich) - Applications, AWS - Europe (Zürich) - Databases, Tables, and Views, Databases, Tables, and Views
- [Vendor status page: https://stspg.io/ws4nygntkfjw](https://stspg.io/ws4nygntkfjw)
- [Company: Snowflake](https://rewindex.com/company/snowflake.md)

## Summary

Snowflake reported a major outage in AWS - Europe (Zürich), potentially preventing sign-ins, queries and data management. It started at 2026-03-07 20:05 UTC and was resolved at 2026-03-07 22:20 UTC; the recorded duration was 2 h 14 min. Snowflake identified a third-party cloud platform issue and confirmed service restoration after coordinating a fix with the provider. _(machine-written, sol)_
## Timeline of updates

- **investigating** 2026-03-07 20:05 UTC: \<b\>Current status:\</b\> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 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.
- **identified** 2026-03-07 20:37 UTC: \<b\>Current status:\</b\> We've identified an issue with a third-party cloud platform, and we're coordinating with the provider to restore service. We're beginning to see some relief as mitigation actions take effect. We're continuing to monitor, and we'll provide another update within 60 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. In the meantime, we recommend that affected customers using replication initiate their failover procedures. \<b\>Incident start time:\</b\> 19:30 UTC March 07, 2026
- **monitoring** 2026-03-07 21:23 UTC: \<b\>Current status:\</b\> We've coordinated with our third-party cloud platform to remediate 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. \<b\>Incident start time:\</b\> 19:30 UTC March 07, 2026 \<b\>Incident end time:\</b\> 21:10 UTC March 07, 2026 \<b\>Preliminary root cause:\</b\> A third-party cloud platform experienced an issue with part of their storage service, which temporarily prevented some Snowflake services and features from working for a subset of customers in this region.
- **resolved** 2026-03-07 22:20 UTC: \<b\>Current status:\</b\> We've coordinated with our third-party cloud platform to confirm that the fix for this issue was successfully implemented, and we've monitored the environment to confirm that service has been fully 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. \<b\>Incident start time:\</b\> 19:30 UTC March 07, 2026 \<b\>Incident end time:\</b\> 21:10 UTC March 07, 2026 \<b\>Preliminary root cause:\</b\> A third-party cloud platform experienced an issue with part of their storage service, which temporarily prevented some Snowflake services and features from working for a subset of customers in this region. A root cause analysis (RCA) document will be published within ten business days.
- **postmortem** 2026-03-20 21:32 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/INC0153183\](https://community.snowflake.com/s/article/INC0153183)

## Rewindex changes for this incident

- 2026-03-07 20:05 UTC: [Major incident: AWS - Europe (Zürich): INC0153183](https://rewindex.com/change/i24692d536188c2.md)


---
Canonical: https://rewindex.com/company/snowflake/incidents/6ghqh8nfw4wc · Markdown: https://rewindex.com/company/snowflake/incidents/6ghqh8nfw4wc.md · JSON: https://rewindex.com/api/v1/companies/snowflake/incidents/6ghqh8nfw4wc · Generated 2026-10-18T11:43:46.423Z
