← Live dashboard

INC20000063

ResolvedcriticalOfficial source confirmedSpecific component onlyFirst recorded update Jun 30, 2026, 10:34 PM · Resolved Jun 30, 2026, 11:34 PM

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/INC20000063](https://community.snowflake.com/s/article/INC20000063)

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

Applications

Updates (4)

  1. Jul 8, 2026, 11:14 PM
    INC20000063

    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/INC20000063](https://community.snowflake.com/s/article/INC20000063)

    Snowflake ↗
  2. Jun 30, 2026, 11:34 PM
    INC20000063

    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 specified region may have been unable to access Snowsight or may have experienced being logged out unexpectedly. All other Snowflake features were not impacted. Workaround: While we were focused on remediation, customers who were logged out needed to log back in to Snowsight. Incident s

    Snowflake ↗
  3. Jun 30, 2026, 10:39 PM
    INC20000063

    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. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified region may have been unable to access Snowsight or may have experienced being logged out unexpectedly. All other Snowflake features were not impacted. Workaround: While we were focused on remediation, customers who were logged out needed to log back in to Snowsight. Incident start time: 21:47 UTC June 30, 2026 Incident end time

    Snowflake ↗
  4. Jun 30, 2026, 10:34 PM
    INC20000063

    Current status: We're investigating an issue with Snowsight authentication. We are seeing recovery as of 22:03 UTC and are continuing to monitor. We'll provide an update within 60 minutes. Customer experience: Customers may be unable to access Snowsight or may experience being logged out unexpectedly. All other Snowflake features are not impacted. ETA: We have taken action to address the issue and expect it to be resolved as of 22:03 UTC. Incident start time: 21:47 UTC June 30, 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.