Howdy, Stranger!

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


Network traffic between two Amsterdam (NL) datacenters passes through USA
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 traffic between two Amsterdam (NL) datacenters passes through USA

a_chrisa_chris Member
edited August 2014 in Help

Hello,
I've three vps on Amsterdam (NL) nodes from three providers. One uses a datacenter (VPS1 on SingleHop) while the others use another datacenter (VPS2 and VPS3 on Serverius).
Since yesterday network traffic between them go through USA in both directions (from VPS1 to VPS2/VPS3 and vice versa).

The only difference is that traceroute from VPS1 to VPS2/VPS3 shows US nodes while from VPS2/VPS3 to VPS1 they are not shown but they seem "implicit" (nothing between two NL nodes but 90 ms of difference).

Who should I advise about this issue? Provider1, Provider2, Provider3, both of them, nobody?

Thanks

Comments

  • Wouldn't NL to US and back would be at least 150ms?

  • hostnoob said: Wouldn't NL to US and back would be at least 150ms?

    I would think so.

  • Jack said: Do you have a trace route?

    I don't know if I've hidden the correct data.

    From SingleHop to Serverius:
    traceroute to xxx (xxx), 30 hops max, 60 byte packets
    1 xxx (xxx) 0.038 ms 0.015 ms 0.013 ms
    2 xxx.singlehop.net (xxx) 1.317 ms 1.335 ms 1.455 ms
    3 xxx.singlehop.net (xxx) 0.527 ms 0.551 ms 0.774 ms
    4 ge-1-0-4.mpr1.ams13.nl.above.net (94.31.42.121) 0.274 ms 0.262 ms 0.244 ms
    5 ae4.mpr1.ams10.nl.above.net (64.125.20.49) 0.650 ms 0.635 ms 0.607 ms
    6 ae8.cr1.ams10.nl.above.net (64.125.26.157) 0.598 ms 0.601 ms 0.573 ms
    7 ae9.mpr3.lhr3.uk.above.net (64.125.28.242) 5.295 ms 5.222 ms 5.292 ms
    8 x2-1-2-0.cr2.dca2.us.above.net (64.125.31.186) 86.899 ms 86.893 ms 86.866 ms
    9 ae4.er2.iad10.us.above.net (64.125.21.58) 80.001 ms 81.877 ms 80.075 ms
    10 128.177.113.46.IPYX-093237-002-ZYO.above.net (128.177.113.46) 80.158 ms 80.078 ms 80.178 ms
    11 eth1-5.core1.ash2.us.as5580.net (78.152.34.60) 81.906 ms 81.904 ms 81.840 ms
    12 eth2-3.r1.ash1.us.as5580.net (78.152.35.41) 91.263 ms 80.212 ms 91.071 ms
    13 eth2-3.edge1.nyc1.us.as5580.net (78.152.34.118) 106.030 ms 116.916 ms 117.001 ms
    14 eth4-3.core1.nyc1.us.as5580.net (78.152.44.201) 107.974 ms 108.031 ms 109.694 ms
    15 eth1-5.core1.lon1.uk.as5580.net (78.152.44.134) 192.435 ms 194.020 ms 194.152 ms
    16 eth13-1.core1.ams2.nl.as5580.net (78.152.44.239) 199.684 ms 199.766 ms 198.082 ms
    17 eth8-1.r1.ams1.nl.as5580.net (78.152.42.115) 220.616 ms 220.308 ms 220.652 ms
    18 serverius-50673-gw.edge1.ams9.as5580.net (78.152.40.202) 89.210 ms 90.946 ms 78.152.39.101 (78.152.39.101) 91.566 ms
    19 xxx (xxx) 89.532 ms * *
    20 xxx (xxx) 91.123 ms 89.432 ms 89.330 ms

    From Serverius to SingleHop:
    traceroute to xxx (xxx), 30 hops max, 60 byte packets
    1 * * *
    2 serverius-2.telecity2.openpeering.nl (82.150.155.2) 1.482 ms 1.599 ms 3.393 ms
    3 er1.ams1.nl.above.net (195.69.144.122) 91.081 ms 91.021 ms 91.098 ms
    4 xe-0-0-1.mpr1.ams10.nl.above.net (64.125.22.233) 93.063 ms 93.047 ms 90.987 ms
    5 ae2.mpr1.ams13.nl.above.net (64.125.20.50) 90.769 ms 90.808 ms 90.878 ms
    6 94.31.42.122.IPYX-073272-001-ZYO.above.net (94.31.42.122) 91.775 ms 94.31.42.126.IPYX-073272-002-ZYO.above.net (94.31.42.126) 91.524 ms 91.355 ms
    7 agg-b01b02.r01.a05.ams01.singlehop.net (198.20.100.246) 92.417 ms 92.777 ms agg-b01b02.r01.a05.ams01.singlehop.net (198.20.100.250) 92.097 ms
    8 aswg-b01.r02.a05.ams01.singlehop.net (198.20.100.174) 97.528 ms 97.148 ms 97.693 ms
    9 xxx (xxx) 89.582 ms 89.560 ms 89.549 ms
    10 xxx (xxx) 89.448 ms 89.431 ms 89.537 ms

  • Please use < PRE >

  • They may use CloudFlare or other protection,DNS,etc where traffic routed trough US..?

  • SingleHop to Serverius

    traceroute to xxx (xxx), 30 hops max, 60 byte packets
     1  xxx (xxx)  0.038 ms  0.015 ms  0.013 ms
     2  xxx.singlehop.net (198.20.100.173)  1.317 ms  1.335 ms  1.455 ms
     3  xxx.singlehop.net (198.20.100.249)  0.527 ms  0.551 ms  0.774 ms
     4  ge-1-0-4.mpr1.ams13.nl.above.net (94.31.42.121)  0.274 ms  0.262 ms  0.244 ms
     5  ae4.mpr1.ams10.nl.above.net (64.125.20.49)  0.650 ms  0.635 ms  0.607 ms
     6  ae8.cr1.ams10.nl.above.net (64.125.26.157)  0.598 ms  0.601 ms  0.573 ms
     7  ae9.mpr3.lhr3.uk.above.net (64.125.28.242)  5.295 ms  5.222 ms  5.292 ms
     8  x2-1-2-0.cr2.dca2.us.above.net (64.125.31.186)  86.899 ms  86.893 ms  86.866 ms
     9  ae4.er2.iad10.us.above.net (64.125.21.58)  80.001 ms  81.877 ms  80.075 ms
    10  128.177.113.46.IPYX-093237-002-ZYO.above.net (128.177.113.46)  80.158 ms  80.078 ms  80.178 ms
    11  eth1-5.core1.ash2.us.as5580.net (78.152.34.60)  81.906 ms  81.904 ms  81.840 ms
    12  eth2-3.r1.ash1.us.as5580.net (78.152.35.41)  91.263 ms  80.212 ms  91.071 ms
    13  eth2-3.edge1.nyc1.us.as5580.net (78.152.34.118)  106.030 ms  116.916 ms  117.001 ms
    14  eth4-3.core1.nyc1.us.as5580.net (78.152.44.201)  107.974 ms  108.031 ms  109.694 ms
    15  eth1-5.core1.lon1.uk.as5580.net (78.152.44.134)  192.435 ms  194.020 ms  194.152 ms
    16  eth13-1.core1.ams2.nl.as5580.net (78.152.44.239)  199.684 ms  199.766 ms  198.082 ms
    17  eth8-1.r1.ams1.nl.as5580.net (78.152.42.115)  220.616 ms  220.308 ms  220.652 ms
    18  serverius-xxx (78.152.40.202)  89.210 ms  90.946 ms 78.152.39.101 (78.152.39.101)  91.566 ms
    19  xxx (xxx)  89.532 ms * *
    20  xxx (xxx)  91.123 ms  89.432 ms  89.330 ms
    

    Serverius to SingleHop

    traceroute to xxx (xxx), 30 hops max, 60 byte packets
     1  * * *
     2  serverius-2.telecity2.openpeering.nl (82.150.155.2)  1.482 ms  1.599 ms  3.393 ms
     3  er1.ams1.nl.above.net (195.69.144.122)  91.081 ms  91.021 ms  91.098 ms
     4  xe-0-0-1.mpr1.ams10.nl.above.net (64.125.22.233)  93.063 ms  93.047 ms  90.987 ms
     5  ae2.mpr1.ams13.nl.above.net (64.125.20.50)  90.769 ms  90.808 ms  90.878 ms
     6  94.31.42.122.IPYX-073272-001-ZYO.above.net (94.31.42.122)  91.775 ms 94.31.42.126.IPYX-073272-002-ZYO.above.net (94.31.42.126)  91.524 ms  91.355 ms
     7  agg-b01b02.r01.a05.ams01.singlehop.net (198.20.100.246)  92.417 ms  92.777 ms agg-b01b02.r01.a05.ams01.singlehop.net (198.20.100.250)  92.097 ms
     8  aswg-b01.r02.a05.ams01.singlehop.net (198.20.100.174)  97.528 ms  97.148 ms  97.693 ms
     9  xxx (xxx)  89.582 ms  89.560 ms  89.549 ms
    10  xxx (xxx)  89.448 ms  89.431 ms  89.537 ms
    
  • I'd say contact singhelop (or rather the VPS provider that is with them) and give them these traceroutes.
    Of course serverius might also be interested in the traceroutes, but singlehop probably has more power to fix this.

  • hostnoob said: Wouldn't NL to US and back would be at least 150ms?

    This is from SingleHop NL to Serverius NL: rtt min/avg/max/mdev = 89.438/89.471/89.490/0.245 ms
    This is from SingleHop NL to an Atlanta (US) dc: rtt min/avg/max/mdev = 95.976/96.177/96.697/0.267 ms

  • @a_chris Maybe the NSA want your data before it gets to it's destination :)

    Thanked by 3socials iSidle Cakey
  • @MonsteR said:
    a_chris Maybe the NSA want your data before it gets to it's destination :)

    Ha ha I've been waiting for this answer :p

  • Strange that they don't have a sort of cron job running who traceroutes time by time and uses a whitelist to check if the traffic is well routed.

Sign In or Register to comment.