INC20000032
Jun 11, 00:30 UTCJun 11, 00:30 UTC
Duration
0m
Impact
Critical
Root cause
Config change
Snowflake, 90 days
27 incidents
Affected
ApplicationsAzure - East US (Virginia) - Applications
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/INC20000032](https://community.snowflake.com/s/article/INC20000032)
Timeline
- Postmortem · Jun 18, 03:59 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/INC20000032](https://community.snowflake.com/s/article/INC20000032)
- Resolved · Jun 11, 00:30 UTC
Current status: We identified and reverted a misconfigured change, 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 multiple core Snowflake services and features. For example, affected users may have been unable to access Snowsight, Snowflake Openflow, Snowpark Container Services, or Cortex AI services (such as Cortex LLM functions, Agents, Analyst, and Search). Workaround: There were no available workarounds for this issue. Incident start time: 23:23 UTC June 10, 2026 Incident end time: 23:58 UTC June 10, 2026 Preliminary root cause: A misconfiguration during a system maintenance operation caused connectivity failures in the affected region. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.