Cloudflare Tunnel Error | Current Status (March 18, 2026)

Current Status (March 18, 2026)

Maintenance in Progress: Scheduled maintenance is currently active at data centers in Houston (IAH), Portland (PDX), and Los Angeles (LAX). If you are routed through these locations, you may see increased latency or intermittent “Tunnel Offline” alerts.
Regional Instability: There are reported “Partially Re-routed” status alerts for Dhaka (DAC) and network performance issues in Amsterdam and Brussels.

If your error isn’t related to the data center maintenance above, it likely falls into one of these three categories:

This is the most common “Tunnel Down” error. It means the Cloudflare edge can’t find a healthy cloudflared instance.

The Fix: Check your local logs. Run journalctl -u cloudflared (Linux) or check your Docker logs.
Common Culprit: A change in your local firewall (blocking UDP/7844) or an expired Tunnel token. Try restarting the service: sudo systemctl restart cloudflared.

This occurs if you are trying to point a CNAME from one Cloudflare account to a tunnel in a different Cloudflare account.

The Fix: By default, Cloudflare prohibits this for security. You must either move both domains to the same account or use Cloudflare for SaaS (Custom Hostnames) to bridge them.

If you see this in your terminal logs, your local network is likely blocking QUIC (UDP port 7844).

The Fix: Force the tunnel to use TCP instead of QUIC by adding the protocol flag to your run command:

cloudflared tunnel run --protocol http2 <your-tunnel-name>

Tool	Command	Purpose
Status	`cloudflared tunnel status`	Checks if the local instance is “Healthy”.
Logs	`cloudflared tunnel info`	Shows which data center (e.g., IAH, LAX) you are connected to.
Update	`cloudflared update`	Ensures you aren’t hitting a bug fixed in a newer version.