INC20000034

Final update

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

1. Postmortem · Jul 2, 21:58 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/INC20000034](https://community.snowflake.com/s/article/INC20000034)
2. Resolved · Jun 16, 21:15 UTC
   Current status: We've validated the fix for this issue with our third-party provider 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 or use Snowflake services and features using Snowsight. The most significant periods of impact for most customers were between 14:05-14:35 and 16:27-16:46 UTC, during which customers could not authenticate or access Snowsight. After initial recovery actions, customers were able to access Snowsight but may have been unable to perform operations within the UI or experienced intermittent periods of significant performance issues. Customers may have seen "something went wrong" or "no healthy upstream" error messages. Incident start time: 14:15 UTC June 15, 2026 Incident end time: 21:45 UTC June 15, 2026 Preliminary root cause: Backend infrastructure that supports authentication to the Snowsight service experienced a degradation due to a third-party cloud platform infrastructure issue. This triggered a cascade of connectivity issues in backend components supporting the Snowsight platform, resulting in service disruptions and intermittent access problems. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 10 business days.
3. Monitoring · Jun 16, 04:00 UTC
   Current status: Our third-party cloud platform has confirmed that the underlying infrastructure issue was resolved as of 21:45 UTC. Service health remains stable, and out of an abundance of caution, we will continue to actively monitor the environment before posting our final update. We'll provide another update within 18 hours. Customer experience: Customers hosted in the specified region may have been unable to access or use Snowflake services and features using Snowsight, or may have experienced short periods of intermittent impact. The most significant periods of impact for most customers were between 14:05-14:35 and 16:27-16:46 UTC, during which customers could not authenticate or access Snowsight. After initial recovery actions, customers were able to access Snowsight but were unable to perform operations within the UI or experienced significant performance issues. Customers may have seen "something went wrong" or "no healthy upstream" error messages. ETA: Service is currently healthy and the underlying infrastructure issue has been resolved; however, we're continuing to validate recovery. For affected customers using replication that have initiated their failover procedures, we don't currently recommend failback to the region until after we have finished validating recovery. Incident start time: 14:15 UTC June 15, 2026 Incident end time: 21:45 UTC June 15, 2026 Preliminary root cause: Backend infrastructure that supports authentication to the Snowsight service experien
4. Monitoring · Jun 15, 21:55 UTC
   Current status: We are continuing to coordinate with our third-party cloud provider on addressing the underlying infrastructure issue while we closely monitor the environment. Service health has remained stable after implementing our previous mitigation actions; however, customers may continue to experience intermittent periods of degraded service performance until the issue is fully resolved. We'll provide another update in the next 4 hours. Customer experience: Customers hosted in the specified regions may experience short periods of intermittent impact to Snowflake services and features using Snowsight. The most significant periods of impact for most customers were between 14:05-14:35 UTC and 16:27-16:46, during which customers could not authenticate or access Snowsight. After initial recovery actions, customers were able to access Snowsight but were unable to perform operations within the UI or experienced significant performance issues. Customers may have seen "something went wrong" or "no healthy upstream" error messages. ETA: Service is currently healthy; however an ETA for confirming resolution of the underlying infrastructure issue is not yet available. We’ll provide one as soon as possible. For affected customers using replication that have initiated their failover procedures, we don’t currently recommend failback to the region until after we have finished validating recovery. Incident start time: 14:15 UTC June 15, 2026 Incident end time: 17:05 UTC June 15, 2026 Pr
5. Monitoring · Jun 15, 19:22 UTC
   Current status: Services remain stable following our previously implemented mitigation actions; however, customers could experience performance issues until the underlying issue is resolved. We are closely monitoring the environment while we continue to collaborate with the third-party cloud provider to ensure the underlying infrastructure remains healthy. We'll provide another update in the next 2 hours. Customer experience: Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. The most significant periods of impact for most customers were between 14:05-14:35 UTC and 16:27-16:46, during which customers could not authenticate or access Snowsight. After initial recovery actions, customers were able to access Snowsight but were unable to perform operations within the UI or experienced significant performance issues. Customers may have seen "something went wrong" or "no healthy upstream" error messages. ETA: Service is currently healthy; however an ETA for confirming resolution of the underlying infrastructure issue is not yet available. We’ll provide one as soon as possible. For affected customers using replication that have initiated their failover procedures, we don’t currently recommend failback to the region until after we have finished validating recovery. Incident start time: 14:15 UTC June 15, 2026 Incident end time: 17:05 UTC June 15, 2026 Preliminary root cause: Backend infrastructure that suppo
6. Identified · Jun 15, 17:43 UTC
   Current status: We have implemented recovery actions and telemetry indicates that service health has currently returned to normal. However, we are continuing to coordinate with our cloud provider to address the underlying issue affecting backend infrastructure health that may result in periods of intermittent performance impact. We are actively monitoring health and network connectivity of the affected components and will provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. Customers may see "something went wrong" or "no healthy upstream" error messages. Some customers may be able to access Snowsight but are unable to perform operations within the UI. Recovery may be inconsistent as different parts of Snowsight are restored. ETA: Service is currently healthy; however an ETA for confirming resolution of the underlying infrastructure issue is not yet available. We’ll provide one as soon as possible. For affected customers using replication that have initiated their failover procedures, we don’t currently recommend failback to the region until after we have finished validating recovery. Incident start time: 14:15 UTC June 15, 2026
7. Identified · Jun 15, 16:19 UTC
   Current status: Following our initial recovery actions, authentication and basic navigation have been restored for most customers; however, other core Snowsight features are continuing to experience failures or degraded performance. We have identified a network connectivity issue affecting infrastructure components used by Snowsight's backend infrastructure, and we are attempting to recover the affected components. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. Customers may see "something went wrong" or "no healthy upstream" error messages. Some customers may be able to access Snowsight but are unable to perform operations within the UI. Recovery may be inconsistent as different parts of Snowsight are restored. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: While we're focused on remediation, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 14:15 UTC June 15, 2026
8. Identified · Jun 15, 15:13 UTC
   Current status: We've identified an issue affecting Snowsight backend infrastructure, and we're attempting to restart affected components to restore service. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. Customers may see "something went wrong" or "no healthy upstream" error messages. Some customers may be able to access Snowsight but are unable to perform operations within the UI. 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: 14:15 UTC June 15, 2026
9. Investigating · Jun 15, 14:30 UTC
   Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight.