Join Australia's most dynamic and respected property investment community

Help requested - network speed tests

Discussion in 'Help & Feedback' started by Simon Hampel, 2nd Jul, 2016.

  1. Simon Hampel

    Simon Hampel Founder Staff Member

    Joined:
    3rd Jun, 2015
    Posts:
    1,647
    Location:
    Sydney
    First up - if you don't understand what I'm talking about, this thread is not for you - please move on - nothing to see here! :D

    Anyway, I've finally been cut off from creating new VPSs in Linode's Tokyo datacenter (which is full), so I'm going to have to spin up some new servers in a different datacenter.

    This is a major pain because PropertyChat has grown so fast that we're pushing the database server too hard and it keeps falling over - I need to split it out onto it's own server (currently it's sharing a database server with about 20 other sites, including the old Somersoft site which still gets a lot of traffic).

    Linode have indicated they are working on a second datacenter in Tokyo to be live in Q4, so I may end up moving back there if performance looks like it will be better than where ever I move to now.

    So I'm currently evaluating speed tests between Fremont (California), Dallas and Singapore - compared to Tokyo.

    Can I get anyone who has some time and a bit of technical ability (and the time/inclination) to help with some speed tests - I want to try and get some comparisons between various network locations and ISPs across Australia to see which servers are the best for the majority of our users.

    I would expect that people in WA might do better out of Singapore, but people on the east coast may be better off in Fremont. I've seen traffic from parts of QLD to Singapore go via Brisbane, Sydney, Melbourne, Perth ... but then I've also seen traffic to Tokyo go via the US and Hawaii or via Singapore and Hong Kong :eek: ... so it can be a bit of a mixed bag.

    Anyway, here are the commands I'm running. The -6 option tells ping to use IPv6, so if you don't have IPv6 networking enabled for your ISP don't bother ... interestingly I've found some quite significant differences in performance between IPv4 vs IPv6 (usually in IPv6's favour).

    I'm interested in:
    1. average ping time (minimum of 10 pings)
    2. number of network hops
    3. average download speed
    I'm using wget to test download speed (you can download Windows binaries from here: http://downloads.sourceforge.net/gnuwin32/wget-1.11.4-1-setup.exe)

    I'll want to know your location and ISP and network sync speed (to make sure it's not your link limiting the download speeds).

    Code:
    ping -4 -n 10 speedtest.tokyo.linode.com
    ping -4 -n 10 speedtest.dallas.linode.com
    ping -4 -n 10 speedtest.fremont.linode.com
    ping -4 -n 10 speedtest.singapore.linode.com
    
    tracert -4 speedtest.tokyo.linode.com
    tracert -4 speedtest.dallas.linode.com
    tracert -4 speedtest.fremont.linode.com
    tracert -4 speedtest.singapore.linode.com
    
    # IPv6 only:
    ping -6 -n 10 speedtest.tokyo.linode.com
    ping -6 -n 10 speedtest.dallas.linode.com
    ping -6 -n 10 speedtest.fremont.linode.com
    ping -6 -n 10 speedtest.singapore.linode.com
    
    tracert -6 speedtest.tokyo.linode.com
    tracert -6 speedtest.dallas.linode.com
    tracert -6 speedtest.fremont.linode.com
    tracert -6 speedtest.singapore.linode.com
    
    # Only if you have wget or similar installed:
    wget http://speedtest.tokyo.linode.com/100MB-tokyo.bin
    wget http://speedtest.dallas.linode.com/100MB-dallas.bin
    wget http://speedtest.fremont.linode.com/100MB-fremont.bin
    wget http://speedtest.singapore.linode.com/100MB-singapore.bin
    
    
     
  2. Simon Hampel

    Simon Hampel Founder Staff Member

    Joined:
    3rd Jun, 2015
    Posts:
    1,647
    Location:
    Sydney
    For the record, I'm on Internode in Sydney on a Naked ADSL2+ link connected at 18Mbps.

    I'm also testing from a Binary Lane VPS also in Sydney which I think is on a 100+Mbps link.
     
  3. wombat777

    wombat777 Well-Known Member Premium Member

    Joined:
    18th Jun, 2015
    Posts:
    1,412
    Location:
    33°41'24.7"S 150°55'34.3"E
    Will run that on my Mac later today.
     
  4. Simon Hampel

    Simon Hampel Founder Staff Member

    Joined:
    3rd Jun, 2015
    Posts:
    1,647
    Location:
    Sydney
    Turns out all of these speed test files are maxing out my ADSL link - so I can't get accurate tests from home ... at least they are all consistently fast (and download speed isn't quite as important for websites like this as ping times are).
     
  5. D.T.

    D.T. Adelaide Property Manager Business Member

    Joined:
    13th Jun, 2015
    Posts:
    5,570
    Location:
    Adelaide, SA
    From office computer (will do home computer after my 4 home opens today)
    ping -4 -n 10 speedtest.tokyo.linode.com : Minimum = 176ms, Maximum = 324ms, Average = 207ms
    ping -4 -n 10 speedtest.dallas.linode.com : Minimum = 271ms, Maximum = 362ms, Average = 287ms
    ping -4 -n 10 speedtest.fremont.linode.com : Minimum = 192ms, Maximum = 314ms, Average = 210ms
    ping -4 -n 10 speedtest.singapore.linode.com : Minimum = 273ms, Maximum = 407ms, Average = 299ms

    Code:
    Tracing route to speedtest.tokyo.linode.com [106.187.96.148]
    over a maximum of 30 hops:
    
      1    33 ms    33 ms    60 ms  lo100.mflinbras11.nw.aapt.net.au [210.8.1.233]
      2    34 ms    34 ms    33 ms  te2-3.mflindist02.aapt.net.au [203.131.61.146]
      3    34 ms    35 ms    35 ms  bu9.mflinbrdr11.aapt.net.au [202.10.14.33]
      4    45 ms    45 ms    45 ms  nme-sot-dry-wgw1-be-30.tpgi.com.au [203.219.107.201]
      5   172 ms    46 ms    46 ms  203-219-155-65.tpgi.com.au [203.219.155.65]
      6    49 ms    49 ms    46 ms  203-219-106-217.tpgi.com.au [203.219.106.217]
      7    48 ms    46 ms    46 ms  203-221-3-3.tpgi.com.au [203.221.3.3]
      8   158 ms   157 ms   157 ms  ix-xe-0-0-2-572.tcore1.HK2-Hong-Kong.as6453.net [116.0.67.33]
      9   287 ms   215 ms   206 ms  180.87.112.162
    10   183 ms   156 ms   156 ms  hkmjbb001.int-gw.kddi.ne.jp [111.87.5.17]
    11   174 ms   260 ms   174 ms  otejbb205.int-gw.kddi.ne.jp [118.155.198.209]
    12   177 ms   178 ms   178 ms  cm-fcu204.kddnet.ad.jp [124.215.194.181]
    13   175 ms   174 ms   261 ms  124.215.199.170
    14   177 ms   177 ms   178 ms  speedtest.tokyo.linode.com [106.187.96.148]
    
    Trace complete.
    Code:
    Tracing route to speedtest.dallas.linode.com [50.116.25.154]
    over a maximum of 30 hops:
    
      1    66 ms    33 ms    33 ms  lo100.mflinbras11.nw.aapt.net.au [210.8.1.233]
      2    87 ms    34 ms    34 ms  te2-3.mflindist02.aapt.net.au [203.131.61.146]
      3    34 ms    34 ms    34 ms  bu9.mflinbrdr11.aapt.net.au [202.10.14.33]
      4    45 ms    45 ms    45 ms  nme-sot-dry-wgw1-be-30.tpgi.com.au [203.219.107.201]
      5    49 ms    46 ms    46 ms  203-219-155-1.tpgi.com.au [203.219.155.1]
      6    49 ms    46 ms    46 ms  syd-sot-ken-crt1-te-gi-0-4-0-2.tpgi.com.au [203.219.106.185]
      7    50 ms    50 ms    51 ms  203-219-35-131.static.tpgi.com.au [203.219.35.131]
      8     *        *        *     Request timed out.
      9   245 ms   359 ms   245 ms  ae7.bbr02.eq01.sjc02.networklayer.com [173.192.18.165]
    10   240 ms   240 ms   240 ms  ae0.bbr02.cs01.lax01.networklayer.com [173.192.18.151]
    11   239 ms   274 ms   240 ms  ae7.bbr01.cs01.lax01.networklayer.com [173.192.18.166]
    12   278 ms   290 ms   276 ms  ae19.bbr01.eq01.dal03.networklayer.com [173.192.18.140]
    13   259 ms   322 ms   259 ms  81.3d.7e4b.ip4.static.sl-reverse.com [75.126.61.129]
    14     *        *        *     Request timed out.
    15     *        *        *     Request timed out.
    16   255 ms   255 ms   255 ms  ae5.dar02.dal06.networklayer.com [50.97.19.5]
    17   382 ms   258 ms   258 ms  po62.dsr02.dllstx2.networklayer.com [184.172.118.149]
    18   255 ms   255 ms   282 ms  po2.car01.dllstx2.networklayer.com [70.87.254.78]
    19   256 ms   256 ms   256 ms  62.7.1243.static.theplanet.com [67.18.7.98]
    20   256 ms   256 ms   256 ms  gw-h18.linode.com [173.255.207.1]
    21   274 ms   274 ms   274 ms  speedtest.dallas.linode.com [50.116.25.154]
    
    Trace complete.
    Code:
    Tracing route to speedtest.fremont.linode.com [50.116.14.9]
    over a maximum of 30 hops:
    
      1    33 ms    33 ms    35 ms  lo100.mflinbras11.nw.aapt.net.au [210.8.1.233]
      2    34 ms    33 ms    34 ms  te2-3.mflindist02.aapt.net.au [203.131.61.146]
      3    34 ms    34 ms    34 ms  bu9.mflinbrdr11.aapt.net.au [202.10.14.33]
      4    45 ms    45 ms    45 ms  nme-sot-dry-wgw1-be-30.tpgi.com.au [203.219.107.201]
      5    50 ms    54 ms    54 ms  203-219-155-66.tpgi.com.au [203.219.155.66]
      6    45 ms    46 ms    46 ms  syd-sot-ken-crt1-te-gi-0-6-0-2.tpgi.com.au [203.219.106.189]
      7   151 ms    47 ms    46 ms  203-219-35-199.static.tpgi.com.au [203.219.35.199]
      8   190 ms   190 ms   199 ms  10ge3-7.core1.sjc1.he.net [72.52.66.21]
      9   319 ms   224 ms   223 ms  10ge7-2.core1.sjc2.he.net [72.52.92.118]
     10   192 ms   192 ms   195 ms  10ge3-2.core3.fmt2.he.net [184.105.222.13]
     11     *        *        *     Request timed out.
     12   191 ms   191 ms   191 ms  gw-h16.linode.com [173.230.159.1]
     13   320 ms   192 ms   192 ms  speedtest.fremont.linode.com [50.116.14.9]
    
    Trace complete.
    Code:
    Tracing route to speedtest.singapore.linode.com [139.162.23.4]
    over a maximum of 30 hops:
    
      1    36 ms    33 ms    33 ms  lo100.mflinbras11.nw.aapt.net.au [210.8.1.233]
      2    34 ms    34 ms    34 ms  te2-3.mflindist02.aapt.net.au [203.131.61.146]
      3    34 ms    34 ms    34 ms  bu9.mflinbrdr11.aapt.net.au [202.10.14.33]
      4    45 ms    59 ms    45 ms  nme-sot-dry-wgw1-be-30.tpgi.com.au [203.219.107.201]
      5    52 ms    46 ms    46 ms  203-219-155-65.tpgi.com.au [203.219.155.65]
      6    46 ms    46 ms    46 ms  syd-sot-ken-crt1-te-gi-0-4-0-2.tpgi.com.au [203.219.106.185]
      7    47 ms    47 ms    46 ms  203-219-35-195.static.tpgi.com.au [203.219.35.195]
      8   229 ms   324 ms   227 ms  216.156.100.157.ptr.us.xo.net [216.156.100.157]
      9   212 ms   211 ms   210 ms  vb2002.rar3.sanjose-ca.us.xo.net [207.88.13.150]
     10   209 ms   209 ms   209 ms  207.88.14.226.ptr.us.xo.net [207.88.14.226]
     11   241 ms   204 ms   204 ms  63-218-41-141.static.pccwglobal.net [63.218.41.141]
     12   310 ms   403 ms   310 ms  TenGE0-0-0-0.br03.sin02.pccwbtn.net [63.218.228.94]
     13   312 ms   311 ms   311 ms  linode.te0-1-0-21.br03.sin02.pccwbtn.net [63.217.59.62]
     14   275 ms   275 ms   275 ms  139.162.0.10
     15   274 ms   274 ms   314 ms  speedtest.singapore.linode.com [139.162.23.4]
    
    Trace complete.
    
     
  6. DaveM

    DaveM Adelaide Buyers Agent & KFC Strategist Business Member

    Joined:
    14th Jun, 2015
    Posts:
    2,095
    Location:
    Sydney & Adelaide
    Internode Adelaide, NBN 50/20 fibre

    Code:
    C:\Users\dmews>ping -4 -n 10 speedtest.tokyo.linode.com
    
    Pinging speedtest.tokyo.linode.com [106.187.96.148] with 32 bytes of data:
    Reply from 106.187.96.148: bytes=32 time=124ms TTL=49
    Reply from 106.187.96.148: bytes=32 time=122ms TTL=49
    Reply from 106.187.96.148: bytes=32 time=122ms TTL=49
    Reply from 106.187.96.148: bytes=32 time=124ms TTL=49
    Reply from 106.187.96.148: bytes=32 time=123ms TTL=49
    Reply from 106.187.96.148: bytes=32 time=124ms TTL=49
    Reply from 106.187.96.148: bytes=32 time=124ms TTL=49
    Reply from 106.187.96.148: bytes=32 time=124ms TTL=49
    Reply from 106.187.96.148: bytes=32 time=122ms TTL=49
    Reply from 106.187.96.148: bytes=32 time=123ms TTL=49
    
    Ping statistics for 106.187.96.148:
        Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 122ms, Maximum = 124ms, Average = 123ms
    
    C:\Users\dmews>ping -4 -n 10 speedtest.dallas.linode.com
    
    Pinging speedtest.dallas.linode.com [50.116.25.154] with 32 bytes of data:
    Reply from 50.116.25.154: bytes=32 time=200ms TTL=52
    Reply from 50.116.25.154: bytes=32 time=200ms TTL=52
    Reply from 50.116.25.154: bytes=32 time=199ms TTL=52
    Reply from 50.116.25.154: bytes=32 time=229ms TTL=52
    Reply from 50.116.25.154: bytes=32 time=199ms TTL=51
    Reply from 50.116.25.154: bytes=32 time=199ms TTL=52
    Reply from 50.116.25.154: bytes=32 time=200ms TTL=52
    Reply from 50.116.25.154: bytes=32 time=201ms TTL=52
    Reply from 50.116.25.154: bytes=32 time=200ms TTL=52
    Reply from 50.116.25.154: bytes=32 time=200ms TTL=52
    
    Ping statistics for 50.116.25.154:
        Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 199ms, Maximum = 229ms, Average = 202ms
    
    C:\Users\dmews>ping -4 -n 10 speedtest.fremont.linode.com
    
    Pinging speedtest.fremont.linode.com [50.116.14.9] with 32 bytes of data:
    Reply from 50.116.14.9: bytes=32 time=178ms TTL=55
    Reply from 50.116.14.9: bytes=32 time=176ms TTL=55
    Reply from 50.116.14.9: bytes=32 time=177ms TTL=55
    Reply from 50.116.14.9: bytes=32 time=176ms TTL=55
    Reply from 50.116.14.9: bytes=32 time=176ms TTL=55
    Reply from 50.116.14.9: bytes=32 time=199ms TTL=55
    Reply from 50.116.14.9: bytes=32 time=199ms TTL=55
    Reply from 50.116.14.9: bytes=32 time=175ms TTL=55
    Reply from 50.116.14.9: bytes=32 time=171ms TTL=55
    Reply from 50.116.14.9: bytes=32 time=175ms TTL=55
    
    Ping statistics for 50.116.14.9:
        Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 171ms, Maximum = 199ms, Average = 180ms
    
    C:\Users\dmews>ping -4 -n 10 speedtest.singapore.linode.com
    
    Pinging speedtest.singapore.linode.com [139.162.23.4] with 32 bytes of data:
    Reply from 139.162.23.4: bytes=32 time=77ms TTL=57
    Reply from 139.162.23.4: bytes=32 time=79ms TTL=57
    Reply from 139.162.23.4: bytes=32 time=78ms TTL=57
    Reply from 139.162.23.4: bytes=32 time=78ms TTL=57
    Reply from 139.162.23.4: bytes=32 time=78ms TTL=57
    Reply from 139.162.23.4: bytes=32 time=79ms TTL=57
    Reply from 139.162.23.4: bytes=32 time=78ms TTL=57
    Reply from 139.162.23.4: bytes=32 time=78ms TTL=57
    Reply from 139.162.23.4: bytes=32 time=77ms TTL=57
    Reply from 139.162.23.4: bytes=32 time=77ms TTL=57
    
    Ping statistics for 139.162.23.4:
        Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 77ms, Maximum = 79ms, Average = 77ms
    
    C:\Users\dmews>tracert -4 speedtest.tokyo.linode.com
    
    Tracing route to speedtest.tokyo.linode.com [106.187.96.148]
    over a maximum of 30 hops:
    
      1    <1 ms    <1 ms    <1 ms  Vigor.router [10.1.1.1]
      2     1 ms     1 ms     1 ms  lns20.adl2.on.ii.net [203.16.215.197]
      3     2 ms     3 ms     3 ms  ae4.cr1.adl2.on.ii.net [150.101.225.16]
      4    33 ms    21 ms    21 ms  ae16.br1.syd4.on.ii.net [150.101.33.188]
      5   121 ms   121 ms   121 ms  te0-0-0.bdr2.nrt1.on.ii.net [203.16.211.58]
      6   120 ms   121 ms   121 ms  xe-0-0-0-2.r00.tokyjp03.jp.bb.gin.ntt.net [61.120.146.177]
      7   122 ms   122 ms   125 ms  ae-14.r31.tokyjp05.jp.bb.gin.ntt.net [129.250.4.248]
      8   120 ms   121 ms   122 ms  ae-11.r27.tokyjp05.jp.bb.gin.ntt.net [129.250.2.154]
      9   120 ms   178 ms   122 ms  ae-5.a20.tokyjp01.jp.ra.gin.ntt.net [61.213.162.170]
    10   121 ms   121 ms   121 ms  210.163.230.17
    11   121 ms   121 ms   121 ms  210.163.230.102
    12   122 ms   121 ms   121 ms  otejbb206.int-gw.kddi.ne.jp [106.187.6.89]
    13   134 ms   125 ms   125 ms  cm-fcu204.kddnet.ad.jp [124.215.194.181]
    14   123 ms   123 ms   123 ms  124.215.199.170
    15   122 ms   123 ms   123 ms  speedtest.tokyo.linode.com [106.187.96.148]
    
    Trace complete.
    
    C:\Users\dmews>tracert -4 speedtest.dallas.linode.com
    
    Tracing route to speedtest.dallas.linode.com [50.116.25.154]
    over a maximum of 30 hops:
    
      1     1 ms    <1 ms    <1 ms  Vigor.router [10.1.1.1]
      2     1 ms     1 ms     2 ms  lns20.adl2.on.ii.net [203.16.215.197]
      3     1 ms     3 ms     1 ms  ae4.cr1.adl2.on.ii.net [150.101.225.16]
      4    21 ms    21 ms    21 ms  ae16.br1.syd4.on.ii.net [150.101.33.188]
      5   168 ms   168 ms   168 ms  te0-1-1-2.br2.lax1.on.ii.net [203.16.213.190]
      6   168 ms   168 ms   168 ms  softlayer.as36351.any2ix.coresite.com [206.72.210.131]
      7   200 ms   199 ms   199 ms  ae19.bbr01.eq01.dal03.networklayer.com [173.192.18.140]
      8   202 ms   205 ms   208 ms  81.3d.7e4b.ip4.static.sl-reverse.com [75.126.61.129]
      9     *        *        *     Request timed out.
    10     *        *        *     Request timed out.
    11   201 ms   199 ms   199 ms  ae5.dar01.dal06.networklayer.com [50.97.19.3]
    12   200 ms   199 ms   201 ms  po61.dsr02.dllstx2.networklayer.com [184.172.118.143]
    13   232 ms   200 ms   199 ms  po2.car01.dllstx2.networklayer.com [70.87.254.78]
    14   200 ms   202 ms   201 ms  62.7.1243.static.theplanet.com [67.18.7.98]
    15   199 ms   199 ms   199 ms  173.255.207.3
    16   200 ms   200 ms   200 ms  speedtest.dallas.linode.com [50.116.25.154]
    
    Trace complete.
    
    C:\Users\dmews>tracert -4 speedtest.fremont.linode.com
    
    Tracing route to speedtest.fremont.linode.com [50.116.14.9]
    over a maximum of 30 hops:
    
      1     1 ms     1 ms     1 ms  Vigor.router [10.1.1.1]
      2     3 ms     1 ms     3 ms  lns20.adl2.on.ii.net [203.16.215.197]
      3     1 ms     3 ms     8 ms  ae4.cr1.adl2.on.ii.net [150.101.225.16]
      4    33 ms    29 ms    29 ms  ae16.br1.syd4.on.ii.net [150.101.33.188]
      5   167 ms   168 ms   168 ms  te-0-2-1-2.br1.lax1.on.ii.net [150.101.34.42]
      6   167 ms   168 ms   169 ms  10gigabitethernet1-3.core1.lax1.he.net [206.223.123.37]
      7   183 ms   175 ms   176 ms  100ge14-1.core1.sjc2.he.net [184.105.223.249]
      8   176 ms   175 ms   175 ms  10ge3-2.core3.fmt2.he.net [184.105.222.13]
      9     *        *        *     Request timed out.
    10   176 ms   177 ms   176 ms  173.230.159.7
    11   176 ms   176 ms   175 ms  speedtest.fremont.linode.com [50.116.14.9]
    
    Trace complete.
    
    C:\Users\dmews>tracert -4 speedtest.singapore.linode.com
    
    Tracing route to speedtest.singapore.linode.com [139.162.23.4]
    over a maximum of 30 hops:
    
      1    <1 ms    <1 ms    <1 ms  Vigor.router [10.1.1.1]
      2     1 ms     1 ms     1 ms  lns20.adl2.on.ii.net [203.16.215.197]
      3     2 ms     2 ms     1 ms  ae4.cr1.adl2.on.ii.net [150.101.225.16]
      4    29 ms    29 ms    29 ms  ae17.cr1.per1.on.ii.net [150.101.33.19]
      5    79 ms    77 ms    77 ms  pos1-2-0.bdr1.sin1.on.ii.net [150.101.33.68]
      6    80 ms    78 ms    78 ms  63949.sgw.equinix.com [27.111.228.235]
      7    79 ms    79 ms    79 ms  139.162.0.6
      8    78 ms    78 ms    78 ms  speedtest.singapore.linode.com [139.162.23.4]
    
    Trace complete.
     
  7. wombat777

    wombat777 Well-Known Member Premium Member

    Joined:
    18th Jun, 2015
    Posts:
    1,412
    Location:
    33°41'24.7"S 150°55'34.3"E
    Sydney (Rouse Hill), internode (via Telstra Velocity Fibre)

    Code:
    PING speedtest.tokyo.linode.com (106.187.96.148): 56 data bytes
    64 bytes from 106.187.96.148: icmp_seq=0 ttl=50 time=109.957 ms
    64 bytes from 106.187.96.148: icmp_seq=1 ttl=50 time=107.438 ms
    64 bytes from 106.187.96.148: icmp_seq=2 ttl=50 time=108.008 ms
    64 bytes from 106.187.96.148: icmp_seq=3 ttl=50 time=110.959 ms
    64 bytes from 106.187.96.148: icmp_seq=4 ttl=50 time=107.398 ms
    64 bytes from 106.187.96.148: icmp_seq=5 ttl=50 time=112.156 ms
    64 bytes from 106.187.96.148: icmp_seq=6 ttl=50 time=111.125 ms
    64 bytes from 106.187.96.148: icmp_seq=7 ttl=50 time=106.226 ms
    64 bytes from 106.187.96.148: icmp_seq=8 ttl=50 time=109.148 ms
    64 bytes from 106.187.96.148: icmp_seq=9 ttl=50 time=107.952 ms
    
    
    --- speedtest.tokyo.linode.com ping statistics ---
    10 packets transmitted, 10 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 106.226/109.037/112.156/1.844 ms
    
    
    PING speedtest.dallas.linode.com (50.116.25.154): 56 data bytes
    64 bytes from 50.116.25.154: icmp_seq=0 ttl=52 time=189.033 ms
    64 bytes from 50.116.25.154: icmp_seq=1 ttl=52 time=188.944 ms
    64 bytes from 50.116.25.154: icmp_seq=2 ttl=52 time=188.139 ms
    64 bytes from 50.116.25.154: icmp_seq=3 ttl=52 time=222.158 ms
    64 bytes from 50.116.25.154: icmp_seq=4 ttl=52 time=193.690 ms
    64 bytes from 50.116.25.154: icmp_seq=5 ttl=52 time=193.051 ms
    64 bytes from 50.116.25.154: icmp_seq=6 ttl=52 time=193.699 ms
    64 bytes from 50.116.25.154: icmp_seq=7 ttl=51 time=188.312 ms
    64 bytes from 50.116.25.154: icmp_seq=8 ttl=52 time=217.644 ms
    64 bytes from 50.116.25.154: icmp_seq=9 ttl=52 time=189.169 ms
    
    
    --- speedtest.dallas.linode.com ping statistics ---
    10 packets transmitted, 10 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 188.139/196.384/222.158/11.985 ms
    
    
    PING speedtest.fremont.linode.com (50.116.14.9): 56 data bytes
    64 bytes from 50.116.14.9: icmp_seq=0 ttl=55 time=162.414 ms
    64 bytes from 50.116.14.9: icmp_seq=1 ttl=55 time=161.927 ms
    64 bytes from 50.116.14.9: icmp_seq=2 ttl=55 time=158.851 ms
    64 bytes from 50.116.14.9: icmp_seq=3 ttl=55 time=163.676 ms
    64 bytes from 50.116.14.9: icmp_seq=4 ttl=55 time=163.934 ms
    64 bytes from 50.116.14.9: icmp_seq=5 ttl=55 time=186.329 ms
    64 bytes from 50.116.14.9: icmp_seq=6 ttl=55 time=162.909 ms
    64 bytes from 50.116.14.9: icmp_seq=7 ttl=55 time=163.939 ms
    64 bytes from 50.116.14.9: icmp_seq=8 ttl=55 time=160.205 ms
    64 bytes from 50.116.14.9: icmp_seq=9 ttl=55 time=165.298 ms
    
    
    --- speedtest.fremont.linode.com ping statistics ---
    10 packets transmitted, 10 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 158.851/164.948/186.329/7.351 ms
    
    
    PING speedtest.singapore.linode.com (139.162.23.4): 56 data bytes
    64 bytes from 139.162.23.4: icmp_seq=0 ttl=56 time=192.738 ms
    64 bytes from 139.162.23.4: icmp_seq=1 ttl=56 time=193.034 ms
    64 bytes from 139.162.23.4: icmp_seq=2 ttl=56 time=193.762 ms
    64 bytes from 139.162.23.4: icmp_seq=3 ttl=56 time=193.919 ms
    64 bytes from 139.162.23.4: icmp_seq=4 ttl=56 time=193.725 ms
    64 bytes from 139.162.23.4: icmp_seq=5 ttl=56 time=191.227 ms
    64 bytes from 139.162.23.4: icmp_seq=6 ttl=56 time=192.327 ms
    64 bytes from 139.162.23.4: icmp_seq=7 ttl=56 time=193.097 ms
    64 bytes from 139.162.23.4: icmp_seq=8 ttl=56 time=193.603 ms
    64 bytes from 139.162.23.4: icmp_seq=9 ttl=56 time=194.058 ms
    
    
    --- speedtest.singapore.linode.com ping statistics ---
    10 packets transmitted, 10 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 191.227/193.149/194.058/0.830 ms
    
    Code:
    traceroute to speedtest.tokyo.linode.com (106.187.96.148), 64 hops max, 52 byte packets
     1  10.1.1.1 (10.1.1.1)  0.577 ms  0.276 ms  0.229 ms
     2  lns20.syd7.on.ii.net (150.101.199.219)  9.318 ms  5.364 ms  5.846 ms
     3  te3-1-120.cor2.syd6.on.ii.net (150.101.199.241)  6.305 ms  4.532 ms  6.416 ms
     4  ae5.br1.syd7.on.ii.net (150.101.33.50)  8.788 ms  15.734 ms  9.384 ms
     5  po-0-7-2-0.br1.nrt1.on.ii.net (150.101.33.201)  105.636 ms  109.835 ms  104.880 ms
     6  xe-0-0-0-2.r00.tokyjp03.jp.bb.gin.ntt.net (61.120.146.177)  104.650 ms  110.219 ms  104.652 ms
     7  ae-14.r30.tokyjp05.jp.bb.gin.ntt.net (129.250.4.80)  113.288 ms
        ae-14.r31.tokyjp05.jp.bb.gin.ntt.net (129.250.4.248)  107.548 ms
        ae-14.r30.tokyjp05.jp.bb.gin.ntt.net (129.250.4.80)  110.117 ms
     8  ae-10.r26.tokyjp05.jp.bb.gin.ntt.net (129.250.2.152)  109.984 ms
        ae-10.r27.tokyjp05.jp.bb.gin.ntt.net (129.250.2.156)  110.049 ms
        ae-11.r27.tokyjp05.jp.bb.gin.ntt.net (129.250.2.154)  105.654 ms
     9  ae-4.a21.tokyjp01.jp.ra.gin.ntt.net (61.213.162.166)  109.774 ms
        ae-5.a21.tokyjp01.jp.ra.gin.ntt.net (61.213.162.174)  104.154 ms
        ae-4.a21.tokyjp01.jp.ra.gin.ntt.net (61.213.162.166)  104.473 ms
    10  211.122.27.197 (211.122.27.197)  110.518 ms
        210.163.230.9 (210.163.230.9)  109.882 ms
        210.163.230.73 (210.163.230.73)  117.734 ms
    11  210.163.230.102 (210.163.230.102)  106.101 ms
        210.163.230.98 (210.163.230.98)  133.203 ms
        210.163.230.102 (210.163.230.102)  106.101 ms
    12  otejbb206.int-gw.kddi.ne.jp (59.128.5.205)  109.899 ms
        otejbb206.int-gw.kddi.ne.jp (106.187.6.105)  109.266 ms
        otejbb205.int-gw.kddi.ne.jp (106.187.6.81)  109.273 ms
    13  cm-fcu204.kddnet.ad.jp (124.215.194.165)  116.033 ms  111.436 ms  122.004 ms
    14  124.215.199.170 (124.215.199.170)  111.023 ms  110.309 ms  109.916 ms
    15  speedtest.tokyo.linode.com (106.187.96.148)  117.098 ms  112.626 ms  110.498 ms
    
    traceroute to speedtest.dallas.linode.com (50.116.25.154), 64 hops max, 52 byte packets
     1  10.1.1.1 (10.1.1.1)  0.479 ms  0.279 ms  0.374 ms
     2  lns20.syd7.on.ii.net (150.101.199.219)  6.199 ms  5.471 ms  5.859 ms
     3  te3-1-120.cor2.syd6.on.ii.net (150.101.199.241)  5.988 ms  6.188 ms  11.605 ms
     4  ae5.br1.syd7.on.ii.net (150.101.33.50)  5.229 ms  5.316 ms  5.856 ms
     5  te0-1-1-3.br2.sjc2.on.ii.net (150.101.33.149)  161.431 ms
        te0-2-0-3.br2.sjc2.on.ii.net (203.16.213.158)  185.354 ms
        te0-1-1-3.br2.sjc2.on.ii.net (150.101.33.149)  161.063 ms
     6  eqix-ix.softlayer.com (198.32.176.207)  163.036 ms  165.500 ms  162.553 ms
     7  ae3.bbr02.eq01.sjc02.networklayer.com (173.192.18.242)  164.339 ms  167.168 ms  163.044 ms
     8  ae0.bbr02.cs01.lax01.networklayer.com (173.192.18.151)  167.243 ms  185.821 ms  166.219 ms
     9  ae7.bbr01.cs01.lax01.networklayer.com (173.192.18.166)  162.868 ms  165.804 ms  162.746 ms
    10  ae19.bbr01.eq01.dal03.networklayer.com (173.192.18.140)  220.139 ms  218.572 ms  220.897 ms
    11  81.3d.7e4b.ip4.static.sl-reverse.com (75.126.61.129)  196.873 ms  196.996 ms  193.282 ms
    12  * * *
    13  * * *
    14  ae5.dar01.dal06.networklayer.com (50.97.19.3)  194.057 ms  189.790 ms  196.667 ms
    15  po61.dsr02.dllstx2.networklayer.com (184.172.118.143)  195.602 ms
        po62.dsr02.dllstx2.networklayer.com (184.172.118.149)  194.572 ms
        po61.dsr01.dllstx2.networklayer.com (184.172.118.139)  196.643 ms
    16  po1.car01.dllstx2.networklayer.com (70.87.254.74)  194.692 ms
        po2.car01.dllstx2.networklayer.com (70.87.254.78)  192.830 ms
        po1.car01.dllstx2.networklayer.com (70.87.254.74)  199.080 ms
    17  62.7.1243.static.theplanet.com (67.18.7.98)  196.386 ms  196.969 ms  198.022 ms
    18  gw-h18.linode.com (173.255.207.1)  222.411 ms  222.086 ms  220.902 ms
    19  speedtest.dallas.linode.com (50.116.25.154)  189.061 ms  189.557 ms  194.512 ms
    
    traceroute to speedtest.fremont.linode.com (50.116.14.9), 64 hops max, 52 byte packets
     1  10.1.1.1 (10.1.1.1)  0.399 ms  0.310 ms  0.393 ms
     2  lns20.syd7.on.ii.net (150.101.199.219)  6.321 ms  5.603 ms  5.820 ms
     3  te3-1-120.cor2.syd6.on.ii.net (150.101.199.241)  6.048 ms  7.698 ms  12.091 ms
     4  ae5.br1.syd7.on.ii.net (150.101.33.50)  26.220 ms  6.552 ms  10.302 ms
     5  te-0-2-1-3.br1.sjc2.on.ii.net (150.101.33.251)  160.945 ms
        te0-2-1-2.br1.sjc2.on.ii.net (150.101.33.147)  161.127 ms
        te0-1-1-2.br1.sjc2.on.ii.net (150.101.33.193)  157.038 ms
     6  100gigabitethernet2-3.core1.sjc2.he.net (206.223.116.37)  157.189 ms  158.051 ms  161.356 ms
     7  10ge3-2.core3.fmt2.he.net (184.105.222.13)  168.619 ms  164.927 ms  161.480 ms
     8  * * *
     9  173.230.159.5 (173.230.159.5)  167.009 ms
        173.230.159.3 (173.230.159.3)  162.545 ms  162.079 ms
    10  speedtest.fremont.linode.com (50.116.14.9)  158.712 ms  153.933 ms  161.411 ms
    
    traceroute to speedtest.singapore.linode.com (139.162.23.4), 64 hops max, 52 byte packets
     1  10.1.1.1 (10.1.1.1)  0.465 ms  0.296 ms  0.231 ms
     2  lns20.syd7.on.ii.net (150.101.199.219)  8.792 ms  5.518 ms  5.810 ms
     3  te3-1-120.cor2.syd6.on.ii.net (150.101.199.241)  7.902 ms  10.436 ms  10.209 ms
     4  ae5.br1.syd7.on.ii.net (150.101.33.50)  120.721 ms  119.100 ms  128.835 ms
     5  ae0.br1.syd4.on.ii.net (150.101.33.14)  9.428 ms  8.218 ms  39.731 ms
     6  te0-0-0-0.br1.hkg2.on.ii.net (150.101.33.199)  163.633 ms  161.799 ms  162.953 ms
     7  btn1-lacp-10g.hkix.net (123.255.90.244)  123.911 ms  119.454 ms  123.236 ms
     8  tenge0-0-0-2.br03.sin02.pccwbtn.net (63.218.228.138)  208.424 ms
        tenge0-0-0-3.br03.sin02.pccwbtn.net (63.218.228.118)  212.376 ms  207.777 ms
     9  linode.te0-1-0-21.br03.sin02.pccwbtn.net (63.217.59.62)  216.455 ms
        tenge0-2-0-14.br03.sin02.pccwbtn.net (63.218.228.178)  194.282 ms
        tenge0-0-0-1.br03.sin02.pccwbtn.net (63.218.228.110)  251.687 ms
    10  linode.te0-1-0-21.br03.sin02.pccwbtn.net (63.217.59.62)  151.462 ms  151.254 ms  151.031 ms
    11  speedtest.singapore.linode.com (139.162.23.4)  246.413 ms
        139.162.0.2 (139.162.0.2)  193.288 ms  196.110 ms
    
     
  8. wombat777

    wombat777 Well-Known Member Premium Member

    Joined:
    18th Jun, 2015
    Posts:
    1,412
    Location:
    33°41'24.7"S 150°55'34.3"E
    Code:
    --2016-07-02 11:45:08--  http://speedtest.tokyo.linode.com/100MB-tokyo.bin
    Resolving speedtest.tokyo.linode.com... 106.187.96.148, 2400:8900::4b
    Connecting to speedtest.tokyo.linode.com|106.187.96.148|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 104857600 (100M) [application/octet-stream]
    Saving to: ‘100MB-tokyo.bin’
    100MB-tokyo.bin                                    100%[===============================================================================================================>] 100.00M  3.78MB/s    in 27s    
    
    2016-07-02 11:45:36 (3.67 MB/s) - ‘100MB-tokyo.bin’ saved [104857600/104857600]
    
    
    --2016-07-02 11:45:36--  http://speedtest.dallas.linode.com/100MB-dallas.bin
    Resolving speedtest.dallas.linode.com... 50.116.25.154, 2600:3c00::4b
    Connecting to speedtest.dallas.linode.com|50.116.25.154|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 104857600 (100M) [application/octet-stream]
    Saving to: ‘100MB-dallas.bin’
    100MB-dallas.bin                                   100%[===============================================================================================================>] 100.00M  3.62MB/s    in 28s    
    2016-07-02 11:46:05 (3.59 MB/s) - ‘100MB-dallas.bin’ saved [104857600/104857600]
    
    
    --2016-07-02 11:46:05--  http://speedtest.fremont.linode.com/100MB-fremont.bin
    Resolving speedtest.fremont.linode.com... 50.116.14.9, 2600:3c01::4b
    Connecting to speedtest.fremont.linode.com|50.116.14.9|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 104857600 (100M) [application/octet-stream]
    Saving to: ‘100MB-fremont.bin’
    100MB-fremont.bin                                  100%[===============================================================================================================>] 100.00M  3.73MB/s    in 27s    
    
    2016-07-02 11:46:33 (3.64 MB/s) - ‘100MB-fremont.bin’ saved [104857600/104857600]
    
    
    --2016-07-02 11:46:33--  http://speedtest.singapore.linode.com/100MB-singapore.bin
    Resolving speedtest.singapore.linode.com... 139.162.23.4, 2400:8901::4b
    Connecting to speedtest.singapore.linode.com|139.162.23.4|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 104857600 (100M) [application/octet-stream]
    Saving to: ‘100MB-singapore.bin’
    100MB-singapore.bin                                100%[===============================================================================================================>] 100.00M  3.31MB/s    in 30s    
    
    2016-07-02 11:47:04 (3.30 MB/s) - ‘100MB-singapore.bin’ saved [104857600/104857600]