Snowflake: [Scheduled] Update New VNet Subnet IDs to Avoid Service Interruptions
Timeline of updates
- unknown
We have removed the previously communicated deadline to update VNet subnet IDs (BCR-1955) in the Azure - East US 2 (Virginia) and Azure - West US 2 (Washington) regions. Services will remain available, and no immediate action is required. What happened? 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. Based on customer feedback, we extended the timeline on August 18, 2025. After further review, we are removing the deadline altogether. Customers will only need to take action if contacted directly by Snowflake. How will this affect my service? There is no expected service impact at this time. If a migration becomes necessary for your account, Snowflake will notify you with specific instructions and support to complete the change.
From Snowflake’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.snowflake.com (opens in new tab).
Cite this
Maintenance posted by Snowflake, started 2025-09-03 22:04 UTC, not resolved, 1 update(s).
- Title
- [Scheduled] Update New VNet Subnet IDs to Avoid Service Interruptions
- Vendor
- Snowflake
- Date
- URL
- https://rewindex.com/company/snowflake/incidents/b56lhg7bwnh6
Snowflake profileRecent Snowflake incidentsAll outages on September 3, 2025Snowflake in September 2025MarkdownJSON