Snowflake Status - Incident History

Snowflake Status - Incident History https://status.snowflake.com Statuspage Wed, 27 Aug 2025 03:11:13 -0700 Update New VNet Subnet IDs to Avoid Service Interruptions <p><strong>THIS IS A SCHEDULED EVENT Sep <var data-var='date'>18</var>, <var data-var='time'>17:00</var> - <var data-var='time'>21:00</var> PDT</strong></p><p><small>Aug <var data-var='date'>18</var>, <var data-var='time'>16:46</var> PDT</small><br><strong>Update</strong> - <p><span style="font-weight: 400;">We are extending the deadline to update VNet subnet IDs (</span><a href="https://docs.snowflake.com/en/release-notes/bcr-bundles/un-bundled/bcr-1955"><span style="font-weight: 400;">BCR-1955</span></a><span style="font-weight: 400;">) in the Azure &ndash; East US 2 (Virginia) and Azure &ndash; West US 2 (Washington) regions to September 18, 2025, at 19:00 UTC. Services will remain available until that time, and we will work directly with customers who are ready to transition to the new set of VNets before the scheduled deadline to ensure a smooth changeover.</span></p><br /><p>&nbsp;</p><br /><p><strong>What happened?</strong></p><br /><p><span style="font-weight: 400;">In May 2025, we announced a future update to the VNet subnet IDs in the affected Azure regions. The update was implemented on August 14, 2025; however, based on feedback, we&rsquo;ve extended the timeline to give you more flexibility in completing the required changes.</span></p><br /><p>&nbsp;</p><br /><p><strong>How will this affect my service?</strong></p><br /><p><span style="font-weight: 400;">If the required changes are not implemented by the new deadline, you may begin experiencing service interruptions, such as being unable to perform replication, access databases, run queries, and ingest data via Snowpipe. Affected customers may encounter error messages at that time, such as: &ldquo;Something went wrong: Error received from the customer managed key (CMK) provider caused by user: 'Your request cannot be completed because of t