CloudFlare Workers & Bandwidth Alliance


#1

Are the CloudFlare Workers part of the Bandwidth Alliance? In the test on cloudflareworkers.com the traffic to Backblaze is calculated normally for me.


#2

It should be part of the Bandwidth Alliance. But I haven’t looked deeply into this.
Have you tested Backblaze traffic with just DNS configuration? To see if it counts…


#3

That doesn’t count, that’s why I’m surprised.
I mean to create a subdomain and route it like this would not be the problem, but I wanted to know if I could directly bring it into the worker.


#4

Interesting! A worker fetch to a DNS CNAME backblaze should then force Bandwidth Alliance and save you the bandwidth cost.

Let us know the outcome of your tests.


#5

So, the workers themselves don’t seem to participate in the Bandwidth Alliance, they generate costs if you address the URLs directly.
I.E:
f001.backblazeb2.com is counted, but if I do it through my domain via CNAME and with CloudFlare Proxy the traffic is not billed.

I can well imagine that due to the location of the Edge, backblaze does not recognize other routes and therefore calculates the traffic normally.


#6

Interesting findings. I would have thought the bandwidth alliance was just if request_ip = Cloudflare then cut_bandwidth_cost()!


closed #7

This topic was automatically closed after 14 days. New replies are no longer allowed.