So when I analyze routing to a destination with <code>traceroute</code>, I have this output:
[email protected]:~# traceroute 95.214.53.226 -nq 1
traceroute to 95.214.53.226 (95.214.53.226), 30 hops max, 60 byte packets
1 *
2 172.22.100.4 1.348 ms
3 172.22.100.1 1.522 ms
4 172.16.202.1 1.709 ms
5 172.16.202.41 3.290 ms
6 172.16.199.1 3.359 ms
7 172.20.252.14 15.861 ms
8 87.245.230.30 16.383 ms
9 87.245.232.234 167.755 ms
10 *
11 *
12 *
13 154.54.56.189 168.284 ms
14 154.54.58.226 174.436 ms
15 130.117.51.61 191.255 ms
16 154.54.37.42 198.364 ms
17 149.6.71.139 212.325 ms
18 185.16.37.11 190.273 ms
19 95.214.53.226 190.993 ms !X
Where
*
indicate the route didn't respond, and
!X
idk what is that!
The problem is, as you see,
hop 8
and
hop 9
have many delay between them (167.755 - 16.384) or
151.372 ms
delay! How do I prevent my server is not routing to
87.245.232.234
. Instead it will route to another router that will have low latency, as we know internet topology is mesh topology (CMIIW) so I think it's possible.
So if it's possible to solve this, I will not have latency problem anymore (perhaps).
Be First to Comment