Cloudflare retires CIDR route endpoints and connections field

Starting October 5, 2026, calls and integrations built around the old shapes stop working.

• POST, PATCH, and DELETE calls to the CIDR-encoded route endpoints (/teamnet/routes/network/{ip_network_encoded}) stop working
• GET /accounts/{account_id}/cfd_tunnel and its {tunnel_id} variant no longer include a connections field in the response
• GET /accounts/{account_id}/warp_connector and its {tunnel_id} variant no longer include a connections field in the response
• Scripts, dashboards, or monitoring that parse connections off tunnel or Mesh node list/get responses stop getting that data
• cloudflared tunnel route ip add | delete commands on outdated cloudflared versions stop working against the removed route endpoints

Move to the route_id-based endpoints and the dedicated connections endpoint before October 5, 2026.

• Capture each route's route_id via List tunnel routes, or read it from the response when creating a route with the replacement endpoint
• Update scripts, backend services, or CI/CD pipelines that call the CIDR-encoded route endpoints to use POST /teamnet/routes, PATCH /teamnet/routes/{route_id}, and DELETE /teamnet/routes/{route_id}
• Upgrade cloudflared to the latest version if you manage routes with tunnel route ip add | delete
• Update the cloudflare_zero_trust_tunnel_cloudflared_route Terraform resource and the Cloudflare Terraform provider to a current version
• Update dashboards, monitoring scripts, or automation to call GET /cfd_tunnel/{tunnel_id}/connections or GET /warp_connector/{tunnel_id}/connections instead of parsing connections from list or get responses
• No action needed for cloudflared or the Terraform provider regarding the connections field removal, as neither reads it