// AI Platform Drift

Workers VPC binding cf1:network now egresses through Gateway by default

Cloudflare developer changelog · published 2026-11-19 20:39 UTC
ACTION NEEDED VERIFY_ONLY APISECURITY
WHAT CHANGEDWorkers using VPC Network binding with network_id: "cf1:network" now route public Internet egress through Cloudflare Gateway automatically. Previously this required Cloudflare Tunnel, Mesh, or WAN on-ramp; those are no longer required. Zero Trust traffic policies (DNS, HTTP, Network, and egress) now apply to Worker-originated traffic the same way they apply to WARP users.
WHY IT MATTERSExisting Zero Trust policies that were scoped to WARP users now also enforce on Worker egress traffic. If those policies block or filter traffic your Workers depend on, those Workers will fail. Gateway logs will now capture all Worker egress, changing what appears in audit trails and potentially what triggers alerts.
WHAT TO DOReview your Zero Trust DNS, HTTP, Network and egress policies in the Gateway dashboard. Verify none of them block hostnames or IP ranges your Workers with cf1:network bindings call. Check Gateway logs for new Worker egress entries and confirm they match expected behavior.
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
 Fri, 05 Jun 2026 00:00:00 GMT
 
 Workers using a VPC Network binding with network_id: "cf1:network" now egress to public Internet destinations through Cloudflare Gateway. This means your existing Zero Trust traffic policies — DNS, HTTP, Network, and egress — extend to traffic that originates from your Workers, the same way they do for WARP users today.
-WorkerCalls env.EGRESS.fetch()VPC binding↓Cloudflare MeshBind via cf1:network↓Cloudflare GatewayPolicies applied:DNSHTTPNetwork↓↗Public InternetAny public hostname or IPGateway logsDNSHTTPNetwork
+WorkerCalls env.EGRESS.fetch()VPC binding↓⇄VPC NetworkBind via cf1:networkNo Cloudflare Tunnel, Mesh, or WAN on-ramp required.↓Cloudflare GatewayPolicies applied:DNSHTTPNetwork↓↗Public InternetAny public hostname or IPGateway logsDNSHTTPNetwork
 What you get by default:
 
 Visibility. Worker egress shows up in Gateway DNS, HTTP, and Network logs alongside your other traffic, so you can audit what your Workers are calling and when.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningWorker egress routing and Zero Trust policy application fundamentally changed; existing deployments now subject to Gateway policies.
signalsdeployment architecture change: VPC binding egress routing modified · security/policy scope expansion: Zero Trust policies now apply to Worker egress · integration change: removal of Cloudflare Tunnel/Mesh/WAN requirement · behavioral change: traffic now flows through Cloudflare Gateway by default
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)