Critical impactResolvedDatabases

Snowflake outage: INC20000063

Snowflake reported this critical-impact incident on its official status page on Jun 30, 2026, 22:34 UTC. It was resolved after 1h.

Right now Snowflake is degraded. Live Snowflake status →

🔔 Get alerted when Snowflake has issuesFree · email alerts · no credit card
Jun 30, 2026, 22:34 UTC
started
Jun 30, 2026, 23:34 UTC
resolved
1h
duration
Critical
impact

Affected components

  • Applications
  1. postmortemJul 8, 2026, 23:14 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/INC20000063](https://community.snowflake.com/s/article/INC20000063)

  2. resolvedJun 30, 2026, 23:34 UTC

    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 start time: 21:47 UTC June 30, 2026 Incident end time: 22:03 UTC June 30, 2026 Preliminary root cause: A routine system configuration change caused authentication issues with Snowsight. Once identified, the configuration was reverted. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

  3. monitoringJun 30, 2026, 22:39 UTC

    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: 22:03 UTC June 30, 2026 Preliminary root cause: A routine system configuration change caused authentication issues with Snowsight. Once identified, the configuration was reverted.

  4. identifiedJun 30, 2026, 22:34 UTC

    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

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Snowflake's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Snowflake have incidents?

Snowflake reported 23 incidents in the last 90 days, 18 of them major or critical. A typical incident lasted 1h 56m. See Snowflake's uptime and incident history

Snowflake outage on Jun 30, 2026: INC20000063 · APIStatus.watch