Request from Japan routed to SYD, ICN, and SJC

I have two sites both served using Cloudflare Workers. Site A is served from a nearby edge as expected, but site B is routed to all kinds of other places. Since site A is working fine and I reproduced the issue in three locations, I don’t think this is an ISP issue on my end.

My house Internet in Tokyo: SJC
My phone: ICN
Server on GCP in Tokyo: SYD

Site A goes to KIX from all three places.

Are both domains on a Free plan? I find that under certain conditions, my Free plan doesn’t hit the closest POP, but my Pro plan does.

Yes, it’s a Free plan. Is Pro officially meant to have better routing? If so, I’ll upgrade but I was happier just paying for the workers :sweat_smile:

Currently, my Free Plans are hitting my local POP. They usually do.

But it sounds like both Site A and Site B are on Free Plans, yet they both don’t hit local POPs.

I do see that none of my free plans have the same IP addresses as another. Some are in the same Class B range (104.27.xx.xx). It could still be an ISP issue on how they route the different IP addresses.

What does Traceroute look like for Site A and Site B? At some point, their paths diverge. Go ahead and post Traceroutes if you’d like more feedback.

Site A is hitting the local POP. The KIX or NRT POP is what I would like.

Site B was also hitting the local POP until recently. I just noticed everything was slower than usual and it turned out out it was because of this.

I ran traceroute from a GCP server in Tokyo.

Site A, i.e. the good one:

traceroute to ricky.me (104.24.109.119), 30 hops max, 46 byte packets
1 172.17.0.1 (172.17.0.1) 0.005 ms 0.005 ms 0.002 ms
2 104.24.109.119 (104.24.109.119) 8.290 ms 7.615 ms 7.530 ms

Site B, the bad one:

traceroute to momocloportal.com (104.27.161.149), 30 hops max, 46 byte packets
1 172.17.0.1 (172.17.0.1) 0.005 ms 0.005 ms 0.002 ms
2 104.27.161.149 (104.27.161.149) 113.895 ms 113.949 ms 114.294 ms

That’s…one hop from your internal network straight to the Cloudflare IP address? That’s an impossibility.

I believe that the lack of hops is because GCP is directly peered with Cloudflare.

Here’s the traceroutes from my house.

traceroute to ricky.me (104.24.109.119), 64 hops max, 52 byte packets
1 192.168.86.1 (192.168.86.1) 11.618 ms 6.821 ms 6.746 ms
2 192.168.1.1 (192.168.1.1) 7.967 ms 6.480 ms 12.055 ms
3 tkynik32.asahi-net.or.jp (124.155.80.119) 9.250 ms 8.665 ms 8.812 ms
4 tkynik32-v1.asahi-net.or.jp (124.155.80.53) 9.083 ms 13.645 ms 10.286 ms
5 cs1bi1-v1101.asahi-net.or.jp (124.155.80.2) 9.879 ms 11.415 ms 11.222 ms
6 cs1cr1-v1005.asahi-net.or.jp (202.224.51.17) 10.943 ms 9.864 ms 14.845 ms
7 cs1cr2-v1004.asahi-net.or.jp (202.224.51.14) 10.282 ms 14.470 ms 16.644 ms
8 os4cr2-v1010.asahi-net.or.jp (202.224.51.38) 18.594 ms 24.112 ms 19.377 ms
9 os4ni2-v1041.asahi-net.or.jp (202.224.51.162) 19.014 ms 19.101 ms 19.275 ms
10 218.100.9.25 (218.100.9.25) 17.828 ms 16.693 ms 21.812 ms
11 104.24.109.119 (104.24.109.119) 19.764 ms 21.560 ms 24.925 ms

traceroute to momocloportal.com (104.27.161.149), 64 hops max, 52 byte packets
1 192.168.86.1 (192.168.86.1) 14.509 ms 5.989 ms 5.745 ms
2 192.168.1.1 (192.168.1.1) 8.630 ms 7.083 ms 7.709 ms
3 tkynik32.asahi-net.or.jp (124.155.80.119) 10.808 ms 10.639 ms 13.329 ms
4 tkynik32-v2.asahi-net.or.jp (124.155.80.57) 16.617 ms 10.603 ms 8.997 ms
5 cs1bi2-v1201.asahi-net.or.jp (124.155.80.6) 17.765 ms 11.820 ms 10.231 ms
6 cs1cr2-v1006.asahi-net.or.jp (202.224.51.21) 29.598 ms 11.994 ms 11.083 ms
7 kddni6-v1069.asahi-net.or.jp (202.224.52.9) 27.493 ms 13.851 ms 15.130 ms
8 kddni5-v1071.asahi-net.or.jp (202.224.52.12) 62.783 ms 11.177 ms 30.183 ms
9 210.130.134.109 (210.130.134.109) 13.289 ms 14.475 ms 11.514 ms
10 tky001bb10.iij.net (58.138.100.17) 12.371 ms
tky001bb11.iij.net (58.138.102.109) 18.410 ms
tky001bb11.iij.net (58.138.100.21) 10.201 ms
11 sjc002bb13.iij.net (58.138.88.94) 105.872 ms
sjc002bb12.iij.net (58.138.88.86) 105.459 ms 107.050 ms
12 equinix-sanjose.as13335.net (206.223.116.237) 114.192 ms 118.325 ms 118.544 ms
13 104.27.161.149 (104.27.161.149) 119.022 ms 319.515 ms 197.238 ms

In that case, both sites should show KIX when testing from GCP. Can you try a ‘curl -I example.com’ and look at the cf-ray header.

So, for whatever reason. Asahi routes momocloportal off to JPNIC instead of BBIX, and then it goes downhill from there. You’d have to find out from Asahi why they’re doing this.

ricky.me: 4f1ab1f8687adb24-KIX
momocloportal.com: 4f1ab22d28dfd0dc-SJC

I don’t know what is happening behind the scenes, but I don’t think this is an issue with just one ISP, since as I said it happens on every network I’ve tried. I don’t think AsahiNet, Google, or Docomo would take my call anyway.

At this point, you should contact Support and include a link to this thread:
Login to Cloudflare and then contact Cloudflare Support by clicking on the Get More Help button.

OK, thanks for you help :grinning:

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.