// AI Platform Drift
Cloudflare Workers VPC bindings can now select specific virtual networks
Cloudflare developer changelog · published 2026-10-31 05:46 UTC
WHAT CHANGEDVPC Network bindings now accept network_id set to cf1:vnet:<UUID> to select a specific virtual network, instead of only cf1:network for the account default. Multiple bindings in one Worker can target different virtual networks, each identified by its UUID in the network_id field.
WHY IT MATTERSA single Worker can now reach separate backends that use overlapping private IP addresses by binding to different virtual networks. Without this, Workers could only connect to one virtual network at a time, forcing IP address uniqueness across all backends a Worker needed to reach.
WHAT TO DOIf you run Workers that need to reach staging and production backends with the same private IPs, configure multiple vpc_networks bindings with distinct network_id values pointing to each environment's virtual network UUID.
Model-reported confidence 85% (not measured accuracy)
Primary source ↗
written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Workers VPC - Select a virtual network for VPC Network bindings +https://developers.cloudflare.com/changelog/post/2026-10-28-virtual-network-bindings/ +Wed, 28 Oct 2026 00:00:00 GMT + +VPC Network bindings can select a specific virtual network by setting network_id to cf1:vnet:<UUID>, where the UUID is the ID of the virtual network. Continue to use cf1:network to select your account's default virtual network. +Multiple bindings can select different virtual networks. This lets one Worker reach separate backends that use the same private IP address: +{ +"$schema": "./node_modules/wrangler/config-schema.json", +"vpc_networks": [ +{ +"binding": "PRODUCTION", +"network_id": "cf1:vnet:<PRODUCTION_VNET_UUID>", +"remote": true +}, +{ +"binding": "STAGING", +"network_id": "cf1:vnet:<STAGING_VNET_UUID>", +"remote": true +} +] +}[[vpc_networks]] +binding = "PRODUCTION" +network_id = "cf1:vnet:<PRODUCTION_VNET_UUID>" +remote = true + +[[vpc_networks]] +binding = "STAGING" +network_id = "cf1:vnet:<STAGING_VNET_UUID>" +remote = true +For details, refer to VPC Networks configuration.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
| triage verdict | MATERIAL at 0.92, needed 0.5 |
|---|---|
| triage reasoning | New VPC network selection capability changes how Workers deployments configure and route to backends. |
| signals | new API capability: network_id parameter with cf1:vnet:<UUID> format · deployment configuration change: vpc_networks binding structure · functional expansion: multiple bindings can now select different virtual networks · integration change: enables Workers to reach separate backends with overlapping private IPs · future date: 2026-10-28 marks availability |
| suppression | — |
| triage model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | anthropic/claude-sonnet-4.5 ($0.00000) |