← Back to all sparks
C

Cloudflare Tunnel

INFRA · APIS
Velocity5.0

Daemon that creates secure outbound-only tunnels to Cloudflare

Cloudflare Tunnel ships version bumps monthly with no public release notes — direction is opaque.

networkingtunnelinginfrastructurecloudflarezero-trust
Current state
Cloudflare Tunnel's changelog consists entirely of version releases with SHA256 checksums and no accompanying release notes. In 10 entries covering July through September 2026, the only user-visible signal is a documented regression in 2026.8.0 (trailing slash stripping that broke applications requiring canonical trailing-slash URLs), patched in 2026.8.1. The product ships approximately monthly.
Where it's heading
Without release note content, the product direction cannot be assessed from the changelog alone. The consistent monthly cadence indicates active maintenance, but the absence of notes for any release means there is no observable feature trajectory in this data window.
Prediction
The release cadence will remain consistent given the pattern. Whether meaningful features are being shipped is impossible to determine from this changelog — more likely this is a mature infrastructure tool where changes are primarily internal and the lack of notes is a documentation process issue rather than an absence of development.

Recent moves

  1. 4d ago

    2026.9.1

    Version release with SHA256 checksums only. No release notes provided — changes cannot be assessed from the changelog entry alone.

    View source ↗
  2. 6d ago

    2026.9.0

    Version release with SHA256 checksums only. No release notes provided — consistent with the product's changelog pattern for this period.

    View source ↗
  3. 16d ago

    2026.8.3

    Version release with SHA256 checksums only. No release notes provided.

    View source ↗
  4. 1mo ago

    2026.8.2

    Version release with SHA256 checksums only. No release notes provided.

    View source ↗
  5. 1mo ago

    Cloudflare Tunnel 2026.8.0 — do not use (trailing slash regression, fixed in 2026.8.1)

    This release introduced a regression: trailing slashes are stripped from requests to HTTP origins, causing redirect loops for applications that require canonical trailing-slash URLs (such as WordPress). Marked as a known issue at release time with an explicit advisory to use 2026.8.1 or later instead.

    View source ↗
  6. 1mo ago

    2026.8.1

    Version release with SHA256 checksums only. Implicitly the fix release for the 2026.8.0 trailing slash regression, though no release notes confirm this.

    View source ↗