6 Deployments Affected: INC0107907
Incident Report for Snowflake
Postmortem

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

Posted May 17, 2024 - 00:33 PDT

Resolved
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.
Customer experience: Customers hosted in the specified regions may have experienced delays while attempting to access or use Snowflake services and features using Snowsight.
Incident start time: 01:16 UTC May 07, 2024
Incident end time: 04:31 UTC May 07, 2024
Preliminary root cause: An update intended for improving query execution in worksheets caused a subset of PrivateLink customers to experience delays while attempting to access or use Snowflake services and features using Snowsight.
Posted May 06, 2024 - 21:46 PDT
Identified
Current status: We're continuing to develop and implement a fix to restore service. We'll provide another update within 90 minutes.
Customer experience: Customers hosted in the specified regions may experience delays while attempting to access or use Snowflake services and features using Snowsight.
Workaround: While we are focused on the remediation, please use alternate UIs to access Snowflake services.
Posted May 06, 2024 - 21:25 PDT
This incident affected: AWS - Canada (Central) (Snowsight), AWS - Asia Pacific (Singapore) (Snowsight), AWS - Asia Pacific (Tokyo) (Snowsight), Azure - Australia East (New South Wales) (Snowsight), AWS - Asia Pacific (Seoul) (Snowsight), and AWS - Asia Pacific (Jakarta) (Snowsight).