Skip to content

Incident detail

Azure - West US 2 (Washington): INC0149493

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'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 Snowflake services and features using Snowsight.

  2. Investigating

    <b>Current status:</b> We've confirmed that this issue is restricted to Snowsight availability, all other methods of accessing Snowflake remain available. We're actively engaging with our cloud service provider (CSP) to identify and resolve the issue. 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 Snowflake services and features using Snowsight.

    <b>Workaround:</b> This issue impacts Snowsight availability only. Snowflake services and features remain available via all other methods of access.

    <b>Incident start time:</b> 09:02 UTC January 08, 2026

  3. Identified

    <b>Current status:</b> Snowflake engineers have performed recovery actions expected to restore Snowsight connectivity and are currently confirming that service has resumed. In parallel, we remain engaged with our cloud service provider (CSP) to identify and resolve the issue.This issue has been confirmed as being restricted to Snowsight availability, all other methods of 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 Snowflake services and features using Snowsight.

    <b>ETA:</b> Although an ETA is not yet available, our initial validations indicate service is beginning to return to expected levels.

    <b>Workaround:</b> This issue impacts Snowsight availability only. Snowflake services and features remain available via all other methods of access.

    <b>Incident start time:</b> 09:02 UTC January 08, 2026

  4. Identified

    <b>Current status:</b> Snowflake engineers have performed recovery actions expected to restore Snowsight connectivity and are currently confirming that service has resumed. In parallel, we remain engaged with our cloud service provider (CSP) to identify and resolve the issue. This issue has been confirmed as being restricted to Snowsight availability. 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 Snowflake services and features using Snowsight.

    <b>ETA:</b> Although an ETA is not yet available, our initial validations indicate service is beginning to return to expected levels.

    <b>Workaround:</b> This issue impacts Snowsight availability only. Snowflake services and features remain available via all other methods of access.

    <b>Incident start time:</b> 09:02 UTC January 08, 2026

  5. Monitoring

    <b>Current status:</b> Snowflake engineers have performed recovery actions to restore Snowsight connectivity and have confirmed that service has resumed.

    <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight.

    <b>Incident start time:</b> 09:02 UTC January 08, 2026

    <b>Incident end time:</b> 10:43 UTC January 08, 2026

    <b>Preliminary root cause:</b> A third-party cloud platform experienced an as-yet-undiagnosed issue which caused underlying infrastructure for Snowsight to become unavailable.

  6. Resolved

    <b>Current status:</b> Snowflake engineers have performed recovery actions to restore Snowsight availability and monitored the environment to confirm that service has resumed. We remain engaged with our third-party cloud platform provider as they work to identify root cause and follow-up actions. 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 have been unable to access or use Snowflake services and features using Snowsight.

    <b>Incident start time:</b> 09:02 UTC January 08, 2026

    <b>Incident end time:</b> 10:43 UTC January 08, 2026

    <b>Preliminary root cause:</b> A third-party cloud platform experienced an as-yet-undiagnosed issue which caused underlying infrastructure for Snowsight to become unavailable.

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

Keep exploring

More from Snowflake

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