Cloudflare preserves Workers context for BYOIP destinations
Cloudflare's 30 October notice describes a Workers/BYOIP fix. Review security rules and the different client-IP handling of cross-zone requests.
Cloudflare's 30 October announcement describes a fix for Workers subrequests to Cloudflare-proxied BYOIP hostnames. The company says these requests now retain Workers context, addressing incorrect security decisions and false HTTP 403 responses on affected paths. Release notice
What changed
The notice covers requests made by a Worker to another proxied hostname using customer-provided addresses. Cloudflare says the destination retains CF-Worker and cf.worker.upstream_zone, while affected Bot Management signals describe the original user connection rather than an internal Cloudflare connection. The announcement provides no separate rollout-completion date.
Client-IP headers need separate attention. Cloudflare's HTTP-header documentation says cross-zone Worker subrequests use 2a06:98c0:3600::103 for CF-Connecting-IP. Same-zone requests reflect x-real-ip, which a Worker script can modify. Preserving request context therefore does not mean every destination receives the original visitor IP in that header.
Why it matters for BYOIP
Cloudflare's BYOIP service remains an Enterprise offering for using customer prefixes with supported services. Our Cloudflare provider profile covers the wider onboarding process.
For operators, the implication is that address reachability and application correctness need different acceptance checks. A prefix can be reachable while a downstream application makes an unexpected decision about the request passing through it. Testing only a direct connection to the destination can miss the Worker path that real users take.
Teams investigating unexplained denials now have a specific vendor-reported change to compare with their own observations. It is also a reason to review how logs, rate limits and access decisions interpret client identity. A shared header value on a cross-zone path should not be mistaken for evidence that all those requests came from one visitor.
What to check
- Map the Worker-to-destination paths that use BYOIP, separating same-zone and cross-zone requests. Compare representative requests with the security decisions and origin logs you expect.
- For WAF custom rules, use
cf.worker.upstream_zoneto identify the originating zone. Cloudflare documents thatCF-Workeris added after those rules run. The field reference defines the value as the Worker's zone name, or empty when the request is not from a Worker. - Check assumptions in application logs and rate-limit keys before interpreting
CF-Connecting-IPas an end-user identifier on every path. - Reassess any exception introduced during earlier troubleshooting against observed results. A vendor fix alone does not demonstrate that removing an exception is safe for your application.
Sources and further reading
The dated release notice establishes the reported change; the documentation explains its interpretation. The checks above are editorial recommendations, not results of testing a customer deployment.
Sources
- Workers subrequests now preserve context for BYOIP destinations
Cloudflare · published 30 Oct 2026 · checked 17 Nov 2026
- Cloudflare HTTP headers: Worker subrequests and CF-Worker
Cloudflare · checked 17 Nov 2026
- cf.worker.upstream_zone
Cloudflare · checked 17 Nov 2026
- Cloudflare BYOIP
Cloudflare · checked 17 Nov 2026