← Live dashboard

INC20000217

ResolvedmajorOfficial source confirmedMulti-region impactFirst recorded update Sep 14, 2026, 04:48 AM · Resolved Sep 14, 2026, 06:09 AM

Current status: 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. Customer experience: Customers hosted in the affected deployments may have experienced performance degradation or issues logging into Snowflake, including delayed sign-ins, and SSO login loops. Incident start time: 22:22 UTC September 13, 2026 Incident end time: 05:18 UTC September 14, 2026 Preliminary root cause: An update...

Snowflake live status →

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with Snowflake now? Check the current status

Affected services

Databases, Tables, and Views

Updates (4)

  1. Sep 14, 2026, 06:09 AM
    INC20000217

    Current status: 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. Customer experience: Customers hosted in the affected deployments may have experienced performance degradation or issues logging into Snowflake, including delayed sign-ins, and SSO login loops. Incident start time: 22:22 UTC September 13, 2026 Incident end time: 05:18 UTC September 14, 2026 Preliminary root cause: An update intend

    Snowflake ↗
  2. Sep 14, 2026, 05:40 AM
    INC20000217

    Current status: 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. Customer experience: Customers hosted in the affected deployments may have experienced performance degradation or issues logging into Snowflake, including delayed sign-ins, and SSO login loops. Incident start time: 23:35 UTC September 13, 2026 Incident end time: 05:18 UTC September 14, 2026 Preliminary root cause: An update intended to improve authentication handling caused a subset of single sign-on (SSO) sign-in attempts acros

    Snowflake ↗
  3. Sep 14, 2026, 05:18 AM
    INC20000217

    Current status: 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 1 hour. Customer experience: Customers hosted in the affected deployments may experience performance degradation or issues logging into Snowflake, including delayed sign-ins, and SSO login loops. ETA: 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. Workaround: There are currently no available workarounds for t

    Snowflake ↗
  4. Sep 14, 2026, 04:48 AM
    INC20000217

    Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 1 hour. Customer experience: Customers in the affected regions may experience performance degradation or issues logging into Snowflake, including delayed sign-ins, query execution failures, and errors managing data. ETA: 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. Workaround: There are currently no available workarounds for this issue. Incident start time: 23

    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.