Responses unbearably slow because served by colocation which is far away

I have the same problem with Workers, Pages and Tunnels: everything connects to EWR even though I’m physically near WAW. This makes my services unusably slow. This only happens when I’m connected to my provider - whoever else I asked to try is connected, correctly, to WAW.

I think I understand the general concept of anycast and that “it’s due to peering”. However, it doesn’t seem that I have much influence on peering of my provider and all traffic served from EWR is so slow that it cannot be the closest edge… I need some way to fix this and choose to be served by WAW.

Please help.

Few things:

  1. Can you go to https://cloudflare.com/cdn-cgi/trace and send the output (censor the IP)
  2. What’s your ISP?
  3. Can you do an mtr or traceroute to cloudflare.com and send the output

CDN-CGI is interesting, cloudflare pages would return either VIE or FRA, however my service always returns EWR.

https://cloudflare.com/cdn-cgi/trace:
fl=114f307
h=cloudflare.com
ip=censored
ts=1707263704.973
visit_scheme=https
uag=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36
colo=VIE
sliver=none
http=http/3
loc=PL
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off
rbi=off
kex=X25519Kyber768Draft00

https://censored/cdn-cgi/trace:
fl=650f64
h=censored
ip=censored
ts=1707263584.453
visit_scheme=https
uag=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36
colo=EWR
sliver=005-tier1
http=http/3
loc=PL
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off
rbi=off
kex=X25519Kyber768Draft00

My ISP is T-Mobile Poland

1 172.20.10.1 6.344 ms 5.543 ms 5.381 ms
2 10.9.33.129 118.998 ms 57.369 ms 76.524 ms
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 87.128.239.250 145.066 ms 145.816 ms 144.591 ms
10 * * *
11 66.198.70.2 325.638 ms 218.941 ms 168.813 ms
12 162.158.156.3 165.168 ms
172.70.108.2 171.685 ms
172.70.228.2 230.950 ms
13 172.67.171.164 241.315 ms 211.805 ms 160.127 ms

Hello, the same explained here is true for your ISP too:

Thank you Walshy and Zsolti. I confirm that switching from Free to Pro fixed the issue (now when I’m in T-Mobile, I’m served mostly from FRA instead of WAW but it’s good enough).

The posts you’ve attached also explain the situation and it’s business reason much better than anything I’ve read on the issue so far.