Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Network latency from Moscow, Russia to some European countries
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Network latency from Moscow, Russia to some European countries

kingpinkingpin Member
edited June 2022 in General

I saw an offer by one of the hosts on LET, and checked their network using the test IPs.

I found that the latency between Moscow and their Stockholm location is as low as 20 ms and there's only 4 hops in my traceroute output! I don't remember I've seen anything close to that with some other hosts and locations outside of Russia.

I guess the route that my packets are going through is a part of Rascom network which has direct connections to a number of major European cities.

The lowest latency between the cities according to WonderNetwork is 60 ms though, but their servers are likely routed through some different network.

Do you know any other hosting providers that could benefit from this or some other network which has a good connectivity to other European countries? I would like to buy a VPS or two.

Comments

  • AbdAbd Member, Patron Provider
    edited June 2022
  • Not from MSK side, but from whole Russia - closest countries is Fi (yep, hetzner), LT (time4vps, bacloud for example), and Estonia. But from Estonia I don't know LET-priced hosts.

  • Unfortunately, the best I'm getting from my location is 52 ms. And oddly enough the traceroute output shows that my packets are routed through Sweden:

     4  * * *
     5  195.14.62.67 (195.14.62.67)  20.281 ms  20.270 ms  20.027 ms
     6  et-1-0-22.edge4.Stockholm2.Level3.net (213.249.107.189)  20.498 ms  20.231 ms  19.893 ms
     7  ae1.16.edge1.Helsinki1.level3.net (4.69.161.102)  47.041 ms  47.579 ms  47.323 ms
     8  212.133.6.2 (212.133.6.2)  53.229 ms  53.461 ms  53.126 ms
     9  core32.hel1.hetzner.com (213.239.224.26)  53.844 ms core31.hel1.hetzner.com (213.239.224.38)  57.328 ms  57.054 ms
    

    Thanks anyway! I'm going to check back in a few days and see if the routes changed.

  • kingpinkingpin Member
    edited June 2022

    Time4vps:

     4  * * *
     5  195.14.62.67 (195.14.62.67)  20.265 ms  19.758 ms  19.989 ms
     6  * * *
     7  ae1.20.edge2.Stockholm1.level3.net (4.69.133.150)  22.677 ms ae2.25.edge2.Stockholm1.level3.net (4.69.133.154)  22.426 ms ae1.20.edge2.Stockholm1.level3.net (4.69.133.150)  22.654 ms
     8  UAB-BITE-LI.edge2.Stockholm1.Level3.net (213.249.107.214)  20.425 ms  24.091 ms  22.157 ms
     9  213.252.224.233 (213.252.224.233)  30.866 ms  31.318 ms  30.941 ms
    10  84.15.2.98 (84.15.2.98)  30.916 ms  30.805 ms  30.609 ms
    11  ae042-wan4.rackray.com (185.38.165.42)  46.731 ms  46.464 ms  46.440 ms
    12  n14-b5-lt1.node.serveriai.lt (31.14.178.110)  34.742 ms  34.242 ms  34.516 ms
    13  lg.time4vps.com (212.24.110.207)  34.634 ms  34.544 ms  34.682 ms
    
    --- lg.time4vps.com ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4002ms
    rtt min/avg/max/mdev = 34.392/34.564/34.849/0.154 ms
    

    Bacloud:

     4  * * *
     5  195.14.62.67 (195.14.62.67)  22.861 ms  19.883 ms  22.599 ms
     6  * * *
     7  ae1.20.edge2.Stockholm1.level3.net (4.69.133.150)  20.331 ms ae2.25.edge2.Stockholm1.level3.net (4.69.133.154)  20.558 ms  20.547 ms
     8  UAB-BITE-LI.edge2.Stockholm1.Level3.net (213.249.107.214)  20.780 ms  26.068 ms  26.095 ms
     9  213.252.227.130 (213.252.227.130)  31.257 ms 213.252.227.170 (213.252.227.170)  31.465 ms 213.252.227.130 (213.252.227.130)  31.355 ms
    10  213.226.128.131 (213.226.128.131)  33.761 ms  33.539 ms  33.403 ms
    11  * 3-240-206-85.bacloud.info (85.206.240.3)  33.586 ms *
    12  5-240-206-85.bacloud.info (85.206.240.5)  33.510 ms  33.287 ms  33.093 ms
    13  185-25-50-85.bacloud.com (185.25.50.85)  33.579 ms !X  36.329 ms !X  33.471 ms !X
    
    --- lg-lt-eu.bacloud.com ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4005ms
    rtt min/avg/max/mdev = 33.337/33.548/33.899/0.193 ms
    

    Something might be wrong with my network, many destinations are routed through Sweden.

    Thanks for the suggestions anyway!

  • pikepike Veteran

    @kingpin said:

    Unfortunately, the best I'm getting from my location is 52 ms. And oddly enough the traceroute output shows that my packets are routed through Sweden:

     4  * * *
     5  195.14.62.67 (195.14.62.67)  20.281 ms  20.270 ms  20.027 ms
     6  et-1-0-22.edge4.Stockholm2.Level3.net (213.249.107.189)  20.498 ms  20.231 ms  19.893 ms
     7  ae1.16.edge1.Helsinki1.level3.net (4.69.161.102)  47.041 ms  47.579 ms  47.323 ms
     8  212.133.6.2 (212.133.6.2)  53.229 ms  53.461 ms  53.126 ms
     9  core32.hel1.hetzner.com (213.239.224.26)  53.844 ms core31.hel1.hetzner.com (213.239.224.38)  57.328 ms  57.054 ms
    

    Thanks anyway! I'm going to check back in a few days and see if the routes changed.

    Maybe Level 3 or your ISP decided to not like each other anymore, so the connection is routed via a third party, vimpelcom that peers with level 3 in Stockholm? Seems runet will become the next gfw.

  • kingpinkingpin Member
    edited June 2022

    Yeah, must be something to do with my ISP's (Vimpelkom) network settings, because with the other ISP (Megafon), the latency to Finland and Lithuania is (a little) better:

    1. 44 ms to hel.icmp.hetzner.com in Helsinki.
    2. 26 ms to lg.time4vps.com in Lithuania.
    3. 21.5 ms to lg-lt-eu.bacloud.com in Lithuania.

    Much worse to the same host in Sweden on the other hand though, 55 ms avg.

    For some reason, Megafon routes the packets through Germany, Spain, and Romania now instead of sending them directly to Sweden as Vimpelkom does:

     4  178.176.152.213 (178.176.152.213)  2.212 ms  2.207 ms  2.538 ms
     5  * * *
     6  83.169.204.126 (83.169.204.126)  54.730 ms 83.169.204.124 (83.169.204.124)  33.374 ms 83.169.204.126 (83.169.204.126)  54.669 ms
     7  po-2-0-0.bb1.fra1.de.m247.com (80.81.192.165)  41.285 ms  41.285 ms  41.036 ms
     8  193.27.15.222 (193.27.15.222)  38.296 ms  38.190 ms 37.120.128.252 (37.120.128.252)  39.400 ms
     9  xe-1-1-1-0.bb1.cph1.dk.m247.com (193.27.15.129)  42.378 ms  42.227 ms  42.220 ms
    10  37.120.220.16 (37.120.220.16)  61.748 ms  62.673 ms  63.333 ms
    11  * * *
    12  193.27.15.235 (193.27.15.235)  46.214 ms  46.217 ms  46.203 ms
    13  a.b.c.d (a.b.c.d)  43.090 ms  43.052 ms  42.817 ms
    

    Go figure.

    But I'm an idiot and don't know much about networks and routing.

  • @kingpin said: Go figure.

    Grab some cheap vps from justhost and make tunnel.

  • Yeah, will give it a go. Thanks!

Sign In or Register to comment.