Traffic routed too far from actual location

1

Hey all. For the past few days, I have noticed very high latency on my website. I recently added my first US based machine, and since then, I’ve noticed the issue. Previously, I only had an AMS machine. Now, I have one machine in FRA and one in IAD.

I tried to debug where the routing was leading and used the fly-request-id header to do so. The last part seems to indicate the machine or edge where the request either left or entered. I first tried using debug.fly.dev, which showed me EWR as the Fly-Region header. As of today, it now shows CDG, which is correct. However, for my own site, the routing changed from EWR to SIN, which is still much too far. I also tried another Fly provided service (worldpagespeed.fly.dev), which also routed my traffic through SIN, resulting in high latency.

I tested this with both my home connection and mobile carrier, and both routed my traffic through SIN. However, when I tried from my Windows Server hosted at Hetzner, it routed my traffic through CDG. Im located in Germany.

1 Like
2

Hey @TAINCER

Is traffic routed to sin for ipv4, ipv6 or both?

Could you please share the output of flyio-debug header when connecting via ipv4 and ipv6:

$ curl -s -I -H "flyio-debug: doit" http://debug.fly.dev | grep flyio-debug
$ curl -6 -s -I -H "flyio-debug: doit" http://debug.fly.dev | grep flyio-debug

And ipv4/ipv6 traceroutes:

$ traceroute debug.fly.dev
$ traceroute -6 debug.fly.dev
3

Hey @pavel,

since this morning it seems to route correctly again with my home connection and my mobile carrier, it now enters or leaves at AMS. (fly-request-id ends in -ams)

These are the result for the commands:

~ » curl -s -I -H "flyio-debug: doit" http://debug.fly.dev | grep flyio-debug
flyio-debug: {"n":"edge-cf-cdg1-8d0d","nr":"cdg","ra":"77.21.246.106","rf":"Verbatim","sr":"cdg","sdc":"cdg1","sid":"732871473b0859","st":0,"nrtt":0,"bn":"worker-cf-cdg1-5954","fbn":null}

~ » curl -6 -s -I -H "flyio-debug: doit" http://debug.fly.dev | grep flyio-debug
flyio-debug: {"n":"edge-cf-cdg1-8d0d","nr":"cdg","ra":"77.21.246.106","rf":"Verbatim","sr":"cdg","sdc":"cdg1","sid":"732871473b0859","st":0,"nrtt":0,"bn":"worker-cf-cdg1-5954","fbn":null

traceroute: (My version of traceroute doesn’t has an -6 flag - macos15)

traceroute: Warning: debug.fly.dev has multiple addresses; using 37.16.21.10
traceroute to debug.fly.dev (37.16.21.10), 64 hops max, 40 byte packets
 1  fritz.box (192.168.178.1)  3.746 ms  2.224 ms  2.303 ms
 2  ip4d15f6fe.dynamic.kabel-deutschland.de (77.21.246.254)  12.460 ms  11.542 ms  10.233 ms
 3  ip53a99a56.static.kabel-deutschland.de (83.169.154.86)  10.139 ms  13.182 ms  12.679 ms
 4  ip5886c21b.static.kabel-deutschland.de (88.134.194.27)  12.894 ms  13.526 ms  13.189 ms
 5  145.254.3.122 (145.254.3.122)  14.561 ms  16.141 ms  14.158 ms
 6  145.254.2.209 (145.254.2.209)  21.729 ms  20.563 ms  21.887 ms
 7  ae6-210.rt.irx.fkt.de.retn.net (87.245.236.150)  28.641 ms  23.321 ms *
 8  ae10-11.rt.thv.par.fr.retn.net (87.245.232.252)  32.958 ms  28.107 ms  28.020 ms
 9  gw-as30081.retn.net (87.245.246.253)  30.744 ms  30.382 ms  30.649 ms
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
31  * * *
32  * * *
33  * * *
34  * * *
35  * * *
36  * * *
37  * * *
38  * * *
39  * * *
40  * * *
41  * * *
42  * * *
43  * * *
44  * * *
45  * * *
46  * * *
47  * * *
48  * * *
49  * * *
50  * * *
51  * * *
52  * * *
53  * * *
54  * * *
55  * * *
56  * * *
57  * * *
58  * * *
59  * * *
60  * * *
61  * * *
62  * * *
63  * * *
64  * * *

Thanks for the help :slight_smile:

4

This is an issue I’m having as well. I am near PHX, USA but all of my traffic seems to be routed to LHR. Sadly my ISP does not support ipv6 so I cannot test that.

~ ❯❯❯ curl -s -I -H "flyio-debug: doit" http://debug.fly.dev | grep flyio-debug
flyio-debug: {"n":"edge-cf-lon1-8e62","nr":"lhr","ra":"67.1.197.253","rf":"Verbatim","sr":"lhr","sdc":"lon1","sid":"e148e2365a7892","st":0,"nrtt":0,"bn":"worker-cf-lon1-ac54","fbn":null}
~ ❯❯❯ traceroute debug.fly.dev
traceroute to debug.fly.dev (77.83.140.164), 30 hops max, 60 byte packets
 1  _gateway (192.168.0.1)  0.713 ms  0.754 ms  0.795 ms
 2  tcso-dsl-gw26.tcso.qwest.net (75.160.240.26)  9.748 ms  9.589 ms  10.097 ms
 3  tcso-agw1.inet.qwest.net (75.160.241.201)  9.679 ms  10.028 ms  10.124 ms
 4  ae16.edge2.phx1.sp.lumen.tech (4.68.73.122)  14.184 ms  14.220 ms  14.322 ms
 5  * * *
 6  4.30.181.50 (4.30.181.50)  68.451 ms  77.403 ms  67.164 ms
 7  ae1-5.rt.thn.lon.uk.retn.net (87.245.233.230)  136.680 ms  131.095 ms  131.060 ms
 8  87.245.208.155 (87.245.208.155)  131.373 ms  158.138 ms  131.272 ms
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
5

Really strange that this is happening, I just reported this problem earlier this week and they had to put in a manual fix…

1 Like
6

If this helps, my ISP also doesn’t provide IPv6 addresses, just IPv4.

7

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