Howdy, Stranger!

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

Sign In Register

Quick Links


Categories

In this Discussion

› › Bad Route / High Latency
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.

Bad Route / High Latency

cirrus_cloudcirrus_cloud Member
edited January 2017 in Help

I'm wondering why this route is so bad. It's from Dallas, TX to Atlanta, GA.

https://budgetnode.com/network

45.43.208.106

This is on a VPN, hence the additional ~40ms. Is this typical? It's going through what looks to be Los Angeles and then going through Ashburn, VA before going to Atlanta.

5 44 ms 45 ms 44 ms ix-ae-67-0.tcore1.DT8-Dallas.as6453.net [216.6.53.41] 6 44 ms 46 ms 44 ms 66.110.56.82 7 76 ms 76 ms 76 ms las-b21-link.telia.net [62.115.123.137] 8 75 ms 81 ms 78 ms voxility-ic-304820-las-bb1.c.telia.net [62.115.38.202] 9 74 ms 74 ms 82 ms lax-eqx-01c.voxility.net [37.221.175.230] 10 105 ms 105 ms 106 ms ash-eqx-01c.voxility.net [5.254.109.81] 11 105 ms 104 ms 106 ms lh29657.voxility.net [5.254.109.50] 12 107 ms 107 ms 112 ms 192.168.76.2 13 107 ms 107 ms 108 ms 45.43.208.106

Comments

  • DumbledoreDumbledore Member

    May be due to voxility ?.

  • cirrus_cloudcirrus_cloud Member
    edited January 2017

    But before that (hop 6 to 7), it's already ending up in Los Angeles. The problem is it ending up in LA at all. I've seen some bad routing before, but this is pretty bad.

    https://db-ip.com/62.115.134.41

  • WilliamWilliam Member

    stolipeach said: May be due to voxility ?.

    Ding.

    VOX by design wants this route; it could be different.

  • IshaqIshaq Member

    Your provider's upstream (TATA) is handing the traffic to Telia in LA.

  • PioHostPioHost Member

    Voxility for you, it's the one downside to their protection.

  • cirrus_cloudcirrus_cloud Member

    Are they aware this sort of thing is happening? Is there anyway to prevent this from happening?

  • qpsqps Member, Host Rep

    piohost said: Voxility for you, it's the one downside to their protection.

    This is not caused by Voxility, but by the handoff from this user's upstream provider. The user's upstream provider is handing the traffic to Telia in Los Angeles.

    cirrus_cloud said: Are they aware this sort of thing is happening? Is there anyway to prevent this from happening?

    The user should contact their upstream provider and ask them to re-route traffic over a different carrier, if possible.

    Thanked by 1Clouvider
  • cirrus_cloudcirrus_cloud Member
    edited January 2017

    The same result of going through Telia and Voxility in LA to Ashburn, VA to Atlanta has happened with

    1) The result above I posted. This was through a VPN going through Dallas (Goes through some Linode stuff from the traceroute, I omitted this part).

    2) I tried with my SSDNodes VPS in dallas and got the same result.

    3) I've had two people using their residential internet in entirely different major cities get the same result.

    @qps: Who would I contact about the route being bad? I get the internet doesn't work by distance necessarily, but it seems like a ping of 30-50ms should be reasonable from Dallas to Atlanta if a decent route is taken, instead of in the 70-100 ms range by routing through LA.

  • qpsqps Member, Host Rep

    cirrus_cloud said: Who would I contact about the route being bad?

    Since you are a Budget Node customer, please contact them, and they can pass the info to us and we can investigate further.

  • cirrus_cloudcirrus_cloud Member

    Ishaq already commented on this thread, so maybe I'll wait for him to read this again. But like I said, there's multiple separate sources that are having this same issue in the Texas region.

  • qpsqps Member, Host Rep

    cirrus_cloud said: same issue in the Texas region.

    If they all have Tata in common, there may not be much we can do, as Tata is routing the traffic to LA and handing it off to Telia there.

  • doghouchdoghouch Member

    Not bad for me (in TO):

    traceroute to 45.43.208.106, 30 hops max
1 172.25.45.215      79.692ms 27.995ms 18.231ms
2 172.25.50.97   39.886ms 40.464ms 37.864ms
3 172.25.58.10   37.12ms 44.555ms 27.952ms
4 172.25.50.6    38.704ms 36.603ms 37.65ms
5 172.25.45.130      38.815ms 38.057ms 41.255ms
6 204.101.4.33   18.003ms 46.526ms 29.94ms
7 tcore3-toronto21_tengige0-13-1-0.net.bell.ca (64.230.49.116)   56.291ms 60.36ms 66.353ms
8 tcore4-toronto12_pos1-12-0-0.net.bell.ca (64.230.50.118)   54.796ms 61.31ms 58.144ms
9 tcore3-ashburnbk_0-3-0-0.net.bell.ca (64.230.51.17)    56.101ms 51.513ms 50.134ms
10 bx2-ashburn_ae0.net.bell.ca (64.230.79.51)    64.406ms 49.142ms 56.379ms
11 ash-eqx-01gw.voxility.net (206.126.236.169)   39.396ms 57.356ms 37.97ms
12 ash-eqx-01c.voxility.net (37.221.173.74)      56.907ms 51.058ms 38.127ms
13 lh29657.voxility.net (5.254.109.50)   57.874ms 54.124ms 39.386ms
14 quick-packet.te8-1.br01.atl02.pccwbtn.net (63.218.69.90)      80.204ms 66.955ms 81.823ms
15 45.43.208.106     64.796ms 130.349ms 66
  • cirrus_cloudcirrus_cloud Member

    @doghouch Clarification: I get fine ping on it from northeast US and probably other places. I noticed Texas in particular from people trying to connect to it and reporting high ping.

  • qpsqps Member, Host Rep

    @cirrus_cloud I did a traceroute from Telia in Dallas and it routes through LA as well, so it may be something that Voxility can fix. I have a ticket open with them.

  • cirrus_cloudcirrus_cloud Member

    Alright. All I can tell you is the common link in all of the tests from Texas are:

    las-b21-link.telia.net

    And the hop after that is

    voxility-ic-304820-las-bb1.c.telia.net

  • qpsqps Member, Host Rep

    @cirrus_cloud Please check again. Voxility made some changes.

  • doghouchdoghouch Member

    @cirrus_cloud said:
    @doghouch Clarification: I get fine ping on it from northeast US and probably other places. I noticed Texas in particular from people trying to connect to it and reporting high ping.

    Oh. I thought that you meant that it was bad everywhere :P

    If it helps, latency was pretty high from NY earier

  • SplitIceSplitIce Member, Host Rep

    Unfortunately its not uncommon to see this with Ashburn Voxility. They don't have a Dallas PoP so with Anycast central US has to go one way or the other (West/East).

    They probably have some tuning nobs which the adjust depending on load on either datacenter.

  • cirrus_cloudcirrus_cloud Member
    edited January 2017

    From my Dallas VPS (SSDNodes) to Atlanta VPS

    4 ae32.cr3-dal3.ip4.gtt.net (173.205.47.97) 0.488 ms 0.466 ms 0.441 ms 5 dls-b21-link.telia.net (213.248.81.73) 11.887 ms 11.866 ms 0.434 ms 6 ash-bb3-link.telia.net (80.91.252.121) 31.905 ms ash-bb3-link.telia.net (213.248.80.141) 31.915 ms ash-bb3-link.telia.net (213.155.137.110) 31.913 ms 7 ash-b1-link.telia.net (80.91.252.44) 32.249 ms ash-b1-link.telia.net (62.115.113.209) 32.260 ms ash-b1-link.telia.net (62.115.122.233) 32.435 ms 8 voxility-ic-311384-ash-b3.c.telia.net (62.115.55.66) 32.830 ms 32.867 ms 32.965 ms 9 ash-eqx-01c.voxility.net (37.221.173.74) 32.083 ms 32.133 ms 32.191 ms 10 lh29657.voxility.net (5.254.109.50) 31.925 ms 31.918 ms 31.929 ms 11 Quick-Packet.Te8-1.br01.atl02.pccwbtn.net (63.218.69.90) 51.506 ms 51.396 ms 51.466 ms 12 45.43.208.106 (45.43.208.106) 46.584 ms 46.570 ms 46.542 ms

    Much better. Thanks for the help.

Sign In or Register to comment.