Multiple Deployments: MI-20210630
Incident
Report for Snowflake
Postmortem
Dear Customer,
Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis is made available on the Snowflake Community site.
https://community.snowflake.com/s/article/MI-20210630
We apologize for the service incident and the impact on your applications.
If you have any questions or difficulty accessing the Snowflake community site, please send feedback by submitting a support case or calling Snowflake Technical Support.
Thank you,
Snowflake Support
Resolved
The Service Incident is now closed.
A Root Cause Analysis (RCA) will be posted within the next seven business days.
We apologize for the inconvenience caused by this incident.
If you have any questions or experience any related issues, please open a support case via the Snowflake Community Site.
A Root Cause Analysis (RCA) will be posted within the next seven business days.
We apologize for the inconvenience caused by this incident.
If you have any questions or experience any related issues, please open a support case via the Snowflake Community Site.
Monitoring
We applied a fix to resolve the issue.
Symptom(s): Cannot connect to Snowflake
Incident Start Time: 11:07 PT June 30, 2021
Incident End Time: 12:56 PT June 30, 2021
We are now monitoring the system for any further recurrence of the problem. We will remain in this state for 60 minutes.
If you have any questions or experience any related issues, please open a support case via the Snowflake Community Site.
Symptom(s): Cannot connect to Snowflake
Incident Start Time: 11:07 PT June 30, 2021
Incident End Time: 12:56 PT June 30, 2021
We are now monitoring the system for any further recurrence of the problem. We will remain in this state for 60 minutes.
If you have any questions or experience any related issues, please open a support case via the Snowflake Community Site.
Update
Engineering is working to revert the change.
Update:
Issue tied to a recent change.
Customer Action:
None
Symptom(s): Cannot connect to Snowflake
Incident Start Time: 11:07 PT June 30, 2021
We are working on mitigating the problem. We will update the status as soon as the issue is resolved or provide an update within 60 minutes.
Update:
Issue tied to a recent change.
Customer Action:
None
Symptom(s): Cannot connect to Snowflake
Incident Start Time: 11:07 PT June 30, 2021
We are working on mitigating the problem. We will update the status as soon as the issue is resolved or provide an update within 60 minutes.
Identified
We have identified the problem with the Snowflake Service that is causing the following symptom(s):
Symptom(s): Can not connect to Snowflake
Incident Start Time: 11:07 PT June 30, 2021
We are working on mitigating the problem.
We will update the status as soon as the issue is resolved or provide an update within 30 minutes.
Symptom(s): Can not connect to Snowflake
Incident Start Time: 11:07 PT June 30, 2021
We are working on mitigating the problem.
We will update the status as soon as the issue is resolved or provide an update within 30 minutes.
Update
We are continuing to investigate the issue with Snowflake services.
Symptom(s): Can not connect to Snowflake
Incident Start Time: 11:07 PT June 30, 2021
Customer Action:
None
We will provide more information on the problem investigation status as soon as we have identified the problem or provide an update within 30 minutes.
Symptom(s): Can not connect to Snowflake
Incident Start Time: 11:07 PT June 30, 2021
Customer Action:
None
We will provide more information on the problem investigation status as soon as we have identified the problem or provide an update within 30 minutes.
Investigating
We are investigating an issue with one of the Snowflake services.
Symptom(s): Can not connect to Snowflake
Incident Start Time: 11:07 PT June 30, 2021
We will provide more information on the problem investigation status as soon as we have identified the problem or provide an update within 30 minutes.
Symptom(s): Can not connect to Snowflake
Incident Start Time: 11:07 PT June 30, 2021
We will provide more information on the problem investigation status as soon as we have identified the problem or provide an update within 30 minutes.
This incident affected: AWS - US East (N. Virginia) (Databases, Tables, and Views, Data Loading and Unloading, Business Continuity), Azure - East US 2 (Virginia) (Databases, Tables, and Views, Data Loading and Unloading, Business Continuity), Azure - West Europe (Netherlands) (Databases, Tables, and Views, Data Loading and Unloading, Business Continuity), AWS - Europe (Frankfurt) (Databases, Tables, and Views, Data Loading and Unloading, Business Continuity), AWS - Asia Pacific (Sydney) (Databases, Tables, and Views, Data Loading and Unloading, Business Continuity), AWS - US West (Oregon) (Databases, Tables, and Views, Data Loading and Unloading, Business Continuity), AWS - Europe (Ireland) (Databases, Tables, and Views, Data Loading and Unloading, Business Continuity), AWS - Asia Pacific (Singapore) (Databases, Tables, and Views, Data Loading and Unloading, Business Continuity), Azure - Australia East (New South Wales) (Databases, Tables, and Views, Data Loading and Unloading, Business Continuity), Azure - US Gov (Virginia) (Databases, Tables, and Views, Data Loading and Unloading, Business Continuity), AWS - Canada (Central) (Databases, Tables, and Views, Data Loading and Unloading, Business Continuity), Azure - Canada Central (Toronto) (Databases, Tables, and Views, Data Loading and Unloading, Business Continuity), Azure - UAE North (Dubai) (Databases, Tables, and Views), AWS - US East (Ohio) (Databases, Tables, and Views, Data Loading and Unloading, Business Continuity), AWS - Asia Pacific (Tokyo) (Databases, Tables, and Views, Data Loading and Unloading, Business Continuity), Azure - West US 2 (Washington) (Databases, Tables, and Views, Data Loading and Unloading, Business Continuity), GCP - US Central 1 (Iowa) (Databases, Tables, and Views, Data Loading and Unloading, Business Continuity), GCP - Europe West 4 (Eemshaven) (Databases, Tables, and Views, Data Loading and Unloading, Business Continuity), AWS - Asia Pacific (Mumbai) (Databases, Tables, and Views, Data Loading and Unloading, Business Continuity), Azure - Switzerland North (Zürich) (Databases, Tables, and Views, Data Loading and Unloading, Business Continuity), GCP - Europe West 2 (London) (Databases, Tables, and Views, Data Loading and Unloading, Business Continuity), AWS - Europe (London) (Databases, Tables, and Views, Data Loading and Unloading, Business Continuity), Azure - Central US (Iowa) (Databases, Tables, and Views, Data Loading and Unloading, Business Continuity), and Azure - Southeast Asia (Singapore) (Data Loading and Unloading, Business Continuity).