Skip to content
Snowflake · Data and observabilityJun 11, 2026, 00:30 UTC

INC20000032

CriticalConfig changeUpdated 19h ago
Jun 11, 00:30 UTCJun 11, 00:30 UTC
Duration
0m
Impact
Critical
Root cause
Config change
Snowflake, 90 days
22 incidents
Affected
ApplicationsAzure - East US (Virginia) - Applications
Status page

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

  1. 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)
  2. 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.

More from Snowflake

Full history
StartedIncidentDuration
Sep 1404:48 UTCINC200002171h 21m
Sep 1107:18 UTCINC200002136h 1m
Sep 921:53 UTCINC200002111h 58m
Sep 407:34 UTCINC200001992h 36m
Sep 109:58 UTCINC200001903h 52m
Aug 3117:20 UTCINC200001882h 24m

Also caused by configuration change

All
StartedIncidentDuration
Sep 2218:20 UTCPhone Number APIs and Console Were Returning Incorrect 404 ResponsesTwilio0m
Sep 1622:30 UTCHyperdrive Elevated Origin Connection Failure RatesCloudflare0m
Sep 1211:04 UTCSome customers experiencing blurry image previews and download issuesSlack8h 56m
Sep 108:01 UTCSentry requests timing out / 504'sSentry3h 20m
Aug 2620:00 UTCFlag delivery errors in Streaming APILaunchDarkly0m
Aug 2407:19 UTCDegraded Git Operations over SSHGitHub0m

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.