---
title: TCP connections via connect() over VPC Networks
description: VPC Network bindings now support the connect() Socket API for raw TCP connections, in addition to HTTP traffic via fetch(). Workers can open TCP sockets to any private destination reachable through the bound Cloudflare Tunnel, Cloudflare Mesh, or Cloudflare WAN on-ramp.
image: https://developers.cloudflare.com/changelog-preview.png
---

> Documentation Index  
> Fetch the complete documentation index at: https://developers.cloudflare.com/changelog/llms.txt  
> Use this file to discover all available pages before exploring further. 

[Skip to content](#%5Ftop) 

# Changelog

New updates and improvements at Cloudflare.

[ Subscribe to RSS ](https://developers.cloudflare.com/changelog/rss/index.xml) [ View RSS feeds ](https://developers.cloudflare.com/fundamentals/new-features/available-rss-feeds/) 

![hero image](https://developers.cloudflare.com/_astro/hero.CVYJHPAd_26AMqX.svg) 

[ ← Back to all posts ](https://developers.cloudflare.com/changelog/) 

## TCP connections via connect() over VPC Networks

Jun 16, 2026 

[ Workers VPC ](https://developers.cloudflare.com/workers-vpc/) 

[VPC Network](https://developers.cloudflare.com/workers-vpc/configuration/vpc-networks/) bindings now support the [connect()](https://developers.cloudflare.com/workers/runtime-apis/tcp-sockets/) Socket API for raw TCP connections to private destinations, in addition to HTTP traffic via `fetch()`.

This means Workers can now open TCP sockets to any private service reachable through the bound Cloudflare Tunnel, Cloudflare Mesh, or Cloudflare WAN on-ramp — Redis, Memcached, MQTT, custom binary protocols, or any other TCP-based service.

* [  wrangler.jsonc ](#tab-panel-2564)
* [  wrangler.toml ](#tab-panel-2565)

JSONC

```
{  "$schema": "./node_modules/wrangler/config-schema.json",  "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, use `connect()` on the binding to open a TCP socket to a private destination:

TypeScript

```
export default {  async fetch(request: Request, env: Env) {    // Open a TCP connection to a private Redis instance    const socket = await env.PRIVATE_NETWORK.connect("10.0.1.50:6379");
    // Write a Redis PING command    const writer = socket.writable.getWriter();    await writer.write(new TextEncoder().encode("PING\r\n"));    await writer.close();
    return new Response(socket.readable);  },};
```

Note

`connect()` over VPC Networks currently supports plaintext TCP only.

For more details, refer to [VPC Networks](https://developers.cloudflare.com/workers-vpc/configuration/vpc-networks/) and the [Workers Binding API](https://developers.cloudflare.com/workers-vpc/api/).

```json
{"@context":"https://schema.org","@type":"BlogPosting","@id":"https://developers.cloudflare.com/changelog/post/2026-06-16-tcp-connect-vpc-networks/#page","headline":"TCP connections via connect() over VPC Networks · Changelog","description":"VPC Network bindings now support the connect() Socket API for raw TCP connections, in addition to HTTP traffic via fetch(). Workers can open TCP sockets to any private destination reachable through the bound Cloudflare Tunnel, Cloudflare Mesh, or Cloudflare WAN on-ramp.","url":"https://developers.cloudflare.com/changelog/post/2026-06-16-tcp-connect-vpc-networks/","inLanguage":"en","image":"https://developers.cloudflare.com/changelog-preview.png","dateModified":"2026-06-16","datePublished":"2026-06-16","publisher":{"@type":"Organization","name":"Cloudflare","url":"https://www.cloudflare.com/"},"isPartOf":{"@type":"WebSite","@id":"https://developers.cloudflare.com/#website","name":"Cloudflare Docs","url":"https://developers.cloudflare.com/"}}
```