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

Posted Jul 01, 2021 - 19:22 PDT

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.
Posted Jun 30, 2021 - 14:02 PDT
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.
Posted Jun 30, 2021 - 13:01 PDT
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.
Posted Jun 30, 2021 - 12:32 PDT
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.
Posted Jun 30, 2021 - 12:03 PDT
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.
Posted Jun 30, 2021 - 11:53 PDT
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.
Posted Jun 30, 2021 - 11:28 PDT
This incident affected: Azure - East US 2 (Virginia) (Snowflake Data Warehouse (Database), Snowpipe (Data Ingestion), Replication), Azure - West Europe (Netherlands) (Snowflake Data Warehouse (Database), Snowpipe (Data Ingestion), Replication), AWS - Europe (Ireland) (Snowflake Data Warehouse (Database), Snowpipe (Data Ingestion), Replication), AWS - Asia Pacific (Singapore) (Snowflake Data Warehouse (Database), Snowpipe (Data Ingestion), Replication), Azure - Australia East (New South Wales) (Snowflake Data Warehouse (Database), Snowpipe (Data Ingestion), Replication), Azure - US Gov (Virginia) (Snowflake Data Warehouse (Database), Snowpipe (Data Ingestion), Replication), AWS - Canada (Central) (Snowflake Data Warehouse (Database), Snowpipe (Data Ingestion), Replication), Azure - Canada Central (Toronto) (Snowflake Data Warehouse (Database), Snowpipe (Data Ingestion), Replication), Azure - UAE North (Dubai) (Snowflake Data Warehouse (Database)), AWS - US East (Ohio) (Snowflake Data Warehouse (Database), Snowpipe (Data Ingestion), Replication), AWS - Asia Pacific (Tokyo) (Snowflake Data Warehouse (Database), Snowpipe (Data Ingestion), Replication), Azure - West US 2 (Washington) (Snowflake Data Warehouse (Database), Snowpipe (Data Ingestion), Replication), AWS - Asia Pacific (Mumbai) (Snowflake Data Warehouse (Database), Snowpipe (Data Ingestion), Replication), Azure - Switzerland North (Zürich) (Snowflake Data Warehouse (Database), Snowpipe (Data Ingestion), Replication), GCP - Europe West 2 (London) (Snowflake Data Warehouse (Database), Snowpipe (Data Ingestion), Replication), AWS - Europe (London) (Snowflake Data Warehouse (Database), Snowpipe (Data Ingestion), Replication), Azure - Central US (Iowa) (Snowflake Data Warehouse (Database), Snowpipe (Data Ingestion), Replication), AWS - US East (N. Virginia) (Snowflake Data Warehouse (Database), Snowpipe (Data Ingestion), Replication), Azure - Southeast Asia (Singapore) (Snowpipe (Data Ingestion), Replication), GCP - US Central 1 (Iowa) (Snowflake Data Warehouse (Database), Snowpipe (Data Ingestion), Replication), GCP - Europe West 4 (Eemshaven) (Snowflake Data Warehouse (Database), Snowpipe (Data Ingestion), Replication), AWS - US West (Oregon) (Snowflake Data Warehouse (Database), Snowpipe (Data Ingestion), Replication), AWS - Europe (Frankfurt) (Snowflake Data Warehouse (Database), Snowpipe (Data Ingestion), Replication), and AWS - Asia Pacific (Sydney) (Snowflake Data Warehouse (Database), Snowpipe (Data Ingestion), Replication).