Cloudflare retires CIDR tunnel route endpoints and inline connections fields

What changed

On October 5, 2026, Cloudflare makes two related API changes:

1. CIDR-encoded route endpoints under /accounts/{account_id}/teamnet/routes/network/{ip_network_encoded} are removed. Replacements use route_id-based endpoints (POST/PATCH/DELETE under /teamnet/routes).
2. The connections array is removed from Cloudflare Tunnel and Cloudflare Mesh (cfd_tunnel / warp_connector) list and get responses. Connection details must be fetched from dedicated connections endpoints.

Who is affected

Operators who manage private network routes or read tunnel connection details through the Cloudflare API, cloudflared, Terraform, or other integrations that still call the CIDR-encoded route endpoints or parse connections from tunnel list/get payloads.

Cloudflare notes that cloudflared and the Cloudflare Terraform provider do not read the connections field, so that part of the change does not require action on those tools. Route management via older cloudflared tunnel route commands or outdated Terraform resources still needs review.

What you need to do

Required before October 5, 2026 if you use the affected APIs:

1. Capture each route’s route_id (list routes, or read it from create responses on the replacement endpoint).
2. Update scripts and pipelines that call CIDR-encoded create/update/delete routes to the route_id-based endpoints (network moves into the create body).
3. Upgrade cloudflared if you manage routes with cloudflared tunnel route ip add|delete.
4. Confirm Terraform uses a current cloudflare_zero_trust_tunnel_cloudflared_route resource and provider version.
5. Change any monitoring that read connections from tunnel list/get to call GET .../cfd_tunnel/{tunnel_id}/connections (or the Mesh equivalent).

Migration effort

Likely medium for teams with custom route automation or dashboards that parse nested connections. Path/shape changes and identifier capture are required. Likely lower if you only use current cloudflared/Terraform paths that Cloudflare says are unaffected for the connections field.

Cost impact

Unknown. This is an API contract change. The changelog does not establish whether spend changes for any account. Absence of pricing detail is not evidence of neutral impact.