DocsDigest
Back to listLanguage: JA
ClaudeCloudflare Developer PlatformMay 21, 2026, 12:00 AM

Workers VPC - Reach Cloudflare WAN destinations from Workers VPC

A condensed section focused on the key takeaways first.

Original Post
OpenAIClaude

Quick Digest

Summary

A condensed section focused on the key takeaways first.

claudeen

Workers VPC - Reach Cloudflare WAN destinations from Workers VPC Summary

cloudflareworkerswranglerapijavascriptchangelogvpcreach

Key Points

  • Point 1: Changelog New updates and improvements at Cloudflare.
  • Point 2: Subscribe to RSS View RSS feeds ← Back to all posts Reach Cloudflare WAN destinations from Workers VPC May 21, 2026 Workers VPC You can now use VPC Network bindings with network_id
  • Point 3: wrangler.jsonc wrangler.toml JSONC { " vpc_networks " : [ { " binding " : "PRIVATE_NETWORK" , " network_id " : "cf1:network" , " remote " : true , }, ], } TOML [[ vpc_networks ]] b

Summary

This is an English summary of "Workers VPC - Reach Cloudflare WAN destinations from Workers VPC" published on 2026-05-21.

Key Points

  • Point 1: Changelog New updates and improvements at Cloudflare.
  • Point 2: Subscribe to RSS View RSS feeds ← Back to all posts Reach Cloudflare WAN destinations from Workers VPC May 21, 2026 Workers VPC You can now use VPC Network bindings with network_id
  • Point 3: wrangler.jsonc wrangler.toml JSONC { " vpc_networks " : [ { " binding " : "PRIVATE_NETWORK" , " network_id " : "cf1:network" , " remote " : true , }, ], } TOML [[ vpc_networks ]] b

Full Translation

Translations

A translation section that keeps the flow of the original article.

claudeja

Workers VPC - Reach Cloudflare WAN destinations from Workers VPC（原文タイトル）

概要

公開日: 2026-05-21 翻訳生成に失敗したため、原文をそのまま保存しています。

原文

Changelog New updates and improvements at Cloudflare. Subscribe to RSS View RSS feeds ← Back to all posts Reach Cloudflare WAN destinations from Workers VPC May 21, 2026 Workers VPC You can now use VPC Network bindings with network_id: "cf1:network" to reach your full private network from Workers, including: Cloudflare Mesh nodes and client devices Subnet routes and hostname routes announced through Cloudflare Tunnel or Cloudflare Mesh Destinations connected through Cloudflare WAN on-ramps — GRE, IPsec, and CNI This means a single VPC Network binding can route Worker requests to private services regardless of how those services are connected to Cloudflare: through a Cloudflare Tunnel from a cloud VPC, a Mesh node on a private subnet, or a Cloudflare WAN on-ramp from your data center or branch site. wrangler.jsonc wrangler.toml JSONC { " vpc_networks " : [ { " binding " : "PRIVATE_NETWORK" , " network_id " : "cf1:network" , " remote " : true , }, ], } TOML [[ vpc_networks ]] binding = "PRIVATE_NETWORK" network_id = "cf1:network" remote = true At runtime, the URL you pass to fetch() determines the destination: JavaScript // Reach a service behind a Cloudflare WAN IPsec on-ramp const response = await env . PRIVATE_NETWORK . fetch ( "http://10.50.0.100:8080/api" ) ; Note For destinations behind Cloudflare WAN on-ramps (GRE, IPsec, or CNI), your network must route the Cloudflare source IP range back through the on-ramp so reply traffic returns to Cloudflare. Without this route, stateful flows will fail. This is part of standard Cloudflare WAN onboarding. For configuration options, refer to VPC Networks . Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings Was this helpful? Yes No