Skip to content

Incident detail

Azure - Switzerland North (Zürich): INC0143996

Resolved incidentCritical

Timeline window

to

Get alerted the next time Snowflake breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Investigating

    <b>Current status:</b> We've confirmed that this issue impacts service, and we're continuing to investigate to determine the source of the issue. 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>Incident start time:</b> 00:03 UTC September 27, 2025

  2. Identified

    <b>Current status:</b> We've identified an issue with a third-party cloud platform, and we're coordinating with the provider to develop and implement a fix to restore service. 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> 00:03 UTC September 27, 2025

  3. Identified

    <b>Current status:</b> We're continuing to coordinate with our third-party cloud platform to develop and implement a fix to restore service. 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. Snowflake is working in close partnership with Microsoft Azure to address the incident, and can confirm that mitigation efforts are underway with the highest priority. In the meantime, we recommend that affected customers using replication initiate their failover procedures.

    <b>Incident start time:</b> 00:03 UTC September 27, 2025

  4. Identified

    <b>Current status:</b> We're continuing to coordinate with our third-party cloud platform to develop and implement a fix to restore service. Azure is actively investigating a recent networking change and is preparing a hotfix to address the issue.

    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. We are actively collaborating with Microsoft Azure to address the incident with the highest urgency. In the meantime, we recommend that affected customers using replication initiate their failover procedures.

    <b>Incident start time:</b> 00:03 UTC September 27, 2025

  5. Monitoring

    <b>Current status:</b> We've coordinated with our third-party cloud platform to implement 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 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> 00:03 UTC September 27, 2025

    <b>Incident end time:</b> 03:33 UTC September 27, 2025

    <b>Preliminary root cause:</b> A network event at our third-party cloud provider has caused a disruption to Snowflake services.

  6. Resolved

    <b>Current status:</b> We've coordinated with our third-party cloud platform to implement the fix for this issue, and we've 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.

    <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> 00:03 UTC September 27, 2025

    <b>Incident end time:</b> 03:33 UTC September 27, 2025

    <b>Preliminary root cause:</b> A network event at our third-party cloud provider has caused a disruption to Snowflake services.

    A root cause analysis (RCA) document will be published within ten business days.

  7. Resolved

    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/INC0143996

Keep exploring

More from Snowflake

Neighboring incidents on Snowflake's timeline and the rest of their record on OutageDeck.