Sign inGet started
Provider changes/CloudflareCLOUDFLARE · VERIFIED CHANGE

Workers subrequests to BYOIP destinations now preserve Workers context and original client signals

Workers subrequests to BYOIP destinations now preserve Workers context and original client signals. Bot Management fields change meaning for affected requests, and cross-zone CF-Connecting-IP now uses the Workers client IP address.

Verified Oct 30, 20262 official sources

Mentioned in the evidence

  • Cloudflare Workers
  • Cloudflare BYOIP
  • Bot Management
  • CF-Connecting-IP
  • CF-Worker header

Official sources

  • Cloudflare developer changelog (changelog) ↗
    Because Cloudflare-proxied BYOIP destinations now follow standard Workers subrequest handling, cross-zone requests set CF-Connecting-IP to the Workers client IP address 2a06:98c0:3600::103 for security reasons. This applies when a Worker in one Cloudflare zone sends a subrequest
  • Cloudflare developer changelog (changelog) ↗
    Bot Management fields on the destination zone now represent the original end-user connection for affected BYOIP subrequests. Bot scores, verified bot status, and JA3/JA4 fingerprints no longer represent the internal connection between Cloudflare services.

This is a global change, verified against Cloudflare’s own sources. It is not an assessment of your systems or your impact.

A global change is not your impact.

Auterim checks your confirmed dependencies and can verify repository references when GitHub is connected.

Scan a company URLMore Cloudflare changesMore from this provider