Cloudflare Tunnels without a connection for 30+ days

CloudflareGovernanceTeam planSeverity: lowcloudflare.tunnel

Cloudflare Tunnels that are down with no connection for more than 30 days, or that were never run and are older than 30 days

What LeftSize checks

Find Cloudflare Tunnels that have had no connection for more than 30 days: tunnels that are down (their connectors stopped) or that never ran at all (inactive).

Why it matters

Resources without an owner are hard to charge back and easy to forget, and certificates that expire unnoticed cause outages.

What you get in the issue

LeftSize runs this check from a scheduled GitHub Action with a read-only Cloudflare API token that stays on your runner, and opens one issue per Cloudflare account in GitHub or Jira, updated on every scan. The issue includes:

  • The affected resources, grouped per Cloudflare account
  • Background on why it was flagged and when it is a false positive
  • Step-by-step remediation with safety checks
  • Ready-to-run fix scripts (Cloudflare API, Wrangler or Terraform where available)
  • Cost and operational impact of fixing it
  • Alternative approaches and their trade-offs
  • Snooze, ignore or report a finding with a comment on the issue
Install LeftSizeIncluded in the Team and Business plans.

See the @leftsize commands,how LeftSize works andhow to set it up.

Official references