Howdy, Stranger!

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


High ping with new BuyVM datacenter?
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.

High ping with new BuyVM datacenter?

gianggiang Veteran
edited August 2011 in General

My average ping is 64x ms now, anyone got this issue? It was about 23x ms in the old datacenter.

Thanked by 1Sofia_K

Comments

  • camargcamarg Member
    edited July 2011

    mine is about the same, as it used to be.
    have you compared new to old route?

  • fanfan Veteran

    The BGP is not optimized well now, I guess.

  • gianggiang Veteran
    edited July 2011

    @camarg I don't have old route record =(

    @fan It seems so :D

  • efballefball Member

    My ping times from my BuyVM VPS are 6ms to a VPS at Hurricane Electric in San Jose, and 2.5ms to a VPS at Hurricane Electric in Fremont. Seems backwards, but I'm not complaining.

  • gianggiang Veteran
    edited July 2011

    efball said: My ping times from my BuyVM VPS are 6ms to a VPS at Hurricane Electric in San Jose, and 2.5ms to a VPS at Hurricane Electric in Fremont. Seems backwards, but I'm not complaining.

    My ping now is about 450ms, still higher than the old ping a lot :(

  • fanfan Veteran

    giang said: My ping now is about 450ms, still higher than the old ping a lot :(

    What's your traceroute result now?

  • gianggiang Veteran
    edited August 2011
    C:\Users\Giang>tracert 205.185.116.174
    Tracing route to host.giang.us [205.185.116.174]
    over a maximum of 30 hops:
    
      1    <1 ms    <1 ms    <1 ms  192.168.1.1
      2    11 ms    11 ms     9 ms  GiangPC [113.169.60.1]
      3     *        *        *     Request timed out.
      4     *        *        *     Request timed out.
      5     *        *        *     Request timed out.
      6   288 ms   242 ms   282 ms  GiangPC [123.31.2.89]
      7    38 ms    39 ms    39 ms  218.188.104.173
      8    39 ms    39 ms   424 ms  te1-3-10G.ar6.PHX1.gblx.net [67.16.139.6]
      9   203 ms   203 ms   203 ms  d1-18-224-143-118-on-nets.com [118.143.224.18]
     10   404 ms   392 ms   401 ms  218.189.5.182
     11   287 ms   302 ms   311 ms  te8-5.bbr1.sjc1.bandcon.com [216.151.179.182]
     12   375 ms   416 ms   308 ms  car1.sjc2.bandcon.com [216.151.179.213]
     13   386 ms   374 ms   371 ms  216.151.186.154
     14   375 ms   371 ms   374 ms  173.245.86.18
     15   371 ms   374 ms   378 ms  173.245.86.18
     16   357 ms   364 ms   358 ms  host.giang.us [205.185.116.174]
    Trace complete.
    

    Here it is, It's lower to 357ms now, still higher than average 22x ms to CA.

  • fanfan Veteran

    giang said: Here it is, It's lower to 357ms now, still higher than average 22x ms to CA.

    I'm having similar connectivity, too. Probably we can wait a few days to see how's things going.

  • It's that dang bandcon hop. It hikes the ping times up like crazy coming from south florida. Get rid of that bandcon crap.

  • FranciscoFrancisco Top Host, Host Rep, Veteran

    We'll work at getting more routes over nlayer :)

    Bandcon is decent but very hit/miss it seems.

    Francisco

  • gianggiang Veteran
    edited August 2011

    Francisco said: We'll work at getting more routes over nlayer :)

    >

    Bandcon is decent but very hit/miss it seems.

    >

    Francisco

    Thank you for the update. My average ping is lower to 292ms now :D

    Here is the new tracert:

    
    Tracing route to mydomain.com [205.185.116.174]
    over a maximum of 30 hops:
    
      1    <1 ms    <1 ms    <1 ms  192.168.1.1
      2    11 ms    12 ms     8 ms  MyPC [113.169.60.1]
      3     *        *        *     Request timed out.
      4     *     3825 ms  3533 ms  vdc.vn [123.29.14.85]
      5     *        *        *     Request timed out.
      6     *        *        *     Request timed out.
      7     *      277 ms   277 ms  GiangPC [123.31.2.81]
      8     *        *        *     Request timed out.
      9   288 ms   482 ms   420 ms  po2-20G.ar2.PHX1.gblx.net [67.16.132.70]
     10   320 ms   296 ms   297 ms  HIGHWINDS-NETWORK-GROUP.TenGigabitEthernet2-4.sar2.phx1.gblx.net [146.82.33.142]
     11     *        *        *     Request timed out.
     12   295 ms   295 ms   296 ms  1-1.r2.ch.hwng.net [209.197.1.213]
     13   295 ms   295 ms   298 ms  216.151.186.154
     14     *        *      298 ms  173.245.86.18
     15   298 ms   296 ms   298 ms  node24.buyvm.net [205.185.112.124]
     16   297 ms   303 ms   296 ms  host.giang.us [205.185.116.174]
    
    
  • gianggiang Veteran

    Average ping is back to ~650ms :D

  • InfinityInfinity Member, Host Rep
    edited August 2011

    Mine has reduced too however only by about 40ms, nothing noticable.

    C:\Users\Humza>ping 205.185.122.220
    
    Pinging 205.185.122.220 with 32 bytes of data:
    Reply from 205.185.122.220: bytes=32 time=192ms TTL=52
    Reply from 205.185.122.220: bytes=32 time=186ms TTL=52
    Reply from 205.185.122.220: bytes=32 time=192ms TTL=52
    Reply from 205.185.122.220: bytes=32 time=200ms TTL=52
    
    Ping statistics for 205.185.122.220:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 186ms, Maximum = 200ms, Average = 192ms
    C:\Users\Humza>ipconfig/flushdns
    
    Windows IP Configuration
    
    Successfully flushed the DNS Resolver Cache.
    
    C:\Users\Humza>tracert 205.185.122.220
    
    Tracing route to alpha.infinitymedia.org.uk [205.185.122.220]
    over a maximum of 30 hops:
    
      1     *        *        *     Request timed out.
      2     6 ms     7 ms     7 ms  10.14.164.1
      3    13 ms     9 ms    17 ms  popl-core-1a-ae3-1439.network.virginmedia.net [6
    2.255.161.5]
      4     7 ms     7 ms     7 ms  popl-bb-1a-as2-0.network.virginmedia.net [213.10
    5.174.234]
      5    10 ms     7 ms     7 ms  popl-bb-1b-ae0-0.network.virginmedia.net [213.10
    5.174.230]
      6     7 ms     7 ms     8 ms  popl-tmr-2-ae5-0.network.virginmedia.net [213.10
    5.159.6]
      7     8 ms     7 ms     7 ms  tele-ic-2-as0-0.network.virginmedia.net [62.253.
    184.6]
      8     8 ms    21 ms     7 ms  134-14-250-212.static.virginmedia.com [212.250.1
    4.134]
      9   101 ms    90 ms    79 ms  4-1.r1.ny.hwng.net [69.16.190.209]
     10   109 ms   109 ms   109 ms  e2-4.r1.ch.hwng.net [209.197.0.33]
     11   165 ms   165 ms   165 ms  unknown.hwng.net [209.197.1.217]
     12   189 ms   189 ms   186 ms  216.151.186.154
     13   179 ms   183 ms   188 ms  173.245.86.18
     14   189 ms   191 ms   188 ms  node12.buyvm.net [205.185.112.112]
     15   188 ms   191 ms   186 ms  alpha.infinitymedia.org.uk [205.185.122.220]
    
    Trace complete.

    I seem to remember that on the first few days I did a traceroute and we were with nlayer. But this seems to work better for me :P Or maybe im missing something >.>

  • gianggiang Veteran
    edited August 2011

    LOL, I couldn't post code zzz

    My ping now is lower to about 260ms, a big different :D

  • FranciscoFrancisco Top Host, Host Rep, Veteran

    It's likely because you're going over HE again.

    HE had a failure in FMT1 again taking everything offline. I don't care what people say about us planning the move to coresite - we dodged a bullet there.

    Francisco

    Thanked by 1dmmcintyre3
  • Dodged a bullet indeed. I'm pretty happy with the latency after the move. Not to mention free upgrade to L5520s :)

    Thanked by 1Francisco
  • fanfan Veteran

    @Francisco I'm also going over He.net sometimes, nlayer is better all the time. :P

  • FranciscoFrancisco Top Host, Host Rep, Veteran

    We're awaiting some BGP addons that egi's working on for us so we can force certain ISP's over different routes - namely favor nlayer for a lot of the asia/pacific traffic ;)

    Thanks everyone for the feedback,

    Francisco

  • TigersWayTigersWay Member
    edited August 2011
    Pinging fremont.tigersway.net [205.185.122.37] with 32 bytes of data:
    
    Reply from 205.185.122.37: bytes=32 time=459ms TTL=48
    Reply from 205.185.122.37: bytes=32 time=216ms TTL=48
    Reply from 205.185.122.37: bytes=32 time=228ms TTL=50
    Reply from 205.185.122.37: bytes=32 time=241ms TTL=50
    
    Ping statistics for 205.185.122.37:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 216ms, Maximum = 459ms, Average = 286ms

    It would be good without that always first very slow ping.

    Tracing route to fremont.tigersway.net [205.185.122.37]
    over a maximum of 30 hops:
    
      1    <1 ms    <1 ms    <1 ms  mygateway1.ar7 [192.168.1.1]
      2    85 ms    46 ms    55 ms  58.64.126.255
      3   107 ms    34 ms     8 ms  203.146.222.157
      4    15 ms    14 ms     9 ms  58.64.124.237
      5    28 ms    25 ms    52 ms  ge-11-0-2.401.iig-suk-pe01.sbn.co.th.59.178.115.in-addr.arpa [115.178.59.157]
      6    71 ms    25 ms     9 ms  ge-2-1-1.400.iig-suk-p01.sbn.co.th.59.178.115.in-addr.arpa [115.178.59.217]
      7    92 ms    98 ms    49 ms  172.16.1.42
      8    73 ms    99 ms   128 ms  203.208.190.9
      9    41 ms    79 ms    48 ms  203.208.152.205
     10   291 ms   298 ms   268 ms  203.208.153.162
     11   248 ms   279 ms   230 ms  ge-0-0-0-0.plapx-dr1.ix.singtel.com [203.208.149.1]
     12   237 ms   227 ms   250 ms  paix.he.net [198.32.176.20]
     13   280 ms   236 ms   271 ms  10gigabitethernet3-4.core1.sjc1.he.net [72.52.92.113]
     14   285 ms   340 ms   347 ms  energy-group-networks-llc.10gigabitethernet1-3.core1.sjc1.he.net [64.71.150.22]
     15   230 ms   270 ms   273 ms  173.245.86.18
     16   856 ms   271 ms   222 ms  node12.buyvm.net [205.185.112.112]
     17   225 ms   244 ms     *     fremont.tigersway.net [205.185.122.37]
     18   259 ms   263 ms   259 ms  fremont.tigersway.net [205.185.122.37]
    
    Trace complete.</code>
This discussion has been closed.