Skip to content
Cloudflare Docs

Cloudflare Tunnel

Subscribe to RSS

2025-07-15


Faster, more reliable UDP traffic for Cloudflare Tunnel

Your real-time applications running over Cloudflare Tunnel are now faster and more reliable. We've completely re-architected the way cloudflared proxies UDP traffic in order to isolate it from other traffic, ensuring latency-sensitive applications like private DNS are no longer slowed down by heavy TCP traffic (like file transfers) on the same Tunnel.

This is a foundational improvement to Cloudflare Tunnel, delivered automatically to all customers. There are no settings to configure — your UDP traffic is already flowing faster and more reliably.

What’s new:

  • Faster UDP performance: We've significantly reduced the latency for establishing new UDP sessions, making applications like private DNS much more responsive.
  • Greater reliability for mixed traffic: UDP packets are no longer affected by heavy TCP traffic, preventing timeouts and connection drops for your real-time services.

Learn more about running TCP or UDP applications and private networks through Cloudflare Tunnel.

2024-12-19


Troubleshoot tunnels with diagnostic logs

The latest cloudflared build 2024.12.2 ↗ introduces the ability to collect all the diagnostic logs needed to troubleshoot a cloudflared instance.

A diagnostic report collects data from a single instance of cloudflared running on the local machine and outputs it to a cloudflared-diag file.

The cloudflared-diag-YYYY-MM-DDThh-mm-ss.zip archive contains the files listed below. The data in a file either applies to the cloudflared instance being diagnosed (diagnosee) or the instance that triggered the diagnosis (diagnoser). For example, if your tunnel is running in a Docker container, the diagnosee is the Docker instance and the diagnoser is the host instance.

File nameDescriptionInstance
cli-configuration.jsonTunnel run parameters used when starting the tunneldiagnosee
cloudflared_logs.txtTunnel log file1diagnosee
configuration.jsonTunnel configuration parametersdiagnosee
goroutine.pprofgoroutine profile made available by pprofdiagnosee
heap.pprofheap profile made available by pprofdiagnosee
metrics.txtSnapshot of Tunnel metrics at the time of diagnosisdiagnosee
network.txtJSON traceroutes to Cloudflare's global network using IPv4 and IPv6diagnoser
raw-network.txtRaw traceroutes to Cloudflare's global network using IPv4 and IPv6diagnoser
systeminformation.jsonOperating system information and resource usagediagnosee
task-result.jsonResult of each diagnostic taskdiagnoser
tunnelstate.jsonTunnel connections at the time of diagnosisdiagnosee

Footnotes

  1. If the log file is blank, you may need to set --loglevel to debug when you start the tunnel. The --loglevel parameter is only required if you ran the tunnel from the CLI using a cloudflared tunnel run command. It is not necessary if the tunnel runs as a Linux/macOS service or runs in Docker/Kubernetes. ↩

For more information, refer to Diagnostic logs.

2024-10-17

Simplifed WARP Connector deployment

You can now deploy WARP Connector using a simplified, guided workflow similar to cloudflared connectors. For detailed instructions, refer to the WARP Connector documentation.

2024-10-10

Bugfix for --grace-period

The new cloudflared build 2024.10.0 ↗ has a bugfix related to the --grace-period tunnel run parameter. cloudflared connectors will now abide by the specified waiting period before forcefully closing connections to Cloudflare's network.

2024-08-06

cloudflared builds available in GitHub for Apple silicon

macOS users can now download cloudflared-arm64.pkg directly from GitHub ↗, in addition to being available via Homebrew.