Afrihost Business Uncapped Feedback - 2

Status
Not open for further replies.
kohlhtor said:
This is no torrent it is a html download
With no download manager single download
Link
http://dl.vsl.co.at/downloader.aspx?ID=39388

webafrica

Traceroute has started…

traceroute to dl.vsl.co.at (212.24.125.71), 64 hops max, 72 byte packets
1 fritz.box (192.168.178.1) 0.878 ms 0.455 ms 0.290 ms
2 196-215-43-1.dynamic.isadsl.co.za (196.215.43.1) 8.816 ms 8.585 ms 8.407 ms
3 vlan2473.cdsl2-ctn.isdsl.net (196.38.72.193) 26.351 ms 26.286 ms 26.254 ms
4 196.35.115.136 (196.35.115.136) 33.115 ms 34.740 ms 33.153 ms
5 168.209.6.13 (168.209.6.13) 27.010 ms 27.231 ms 29.044 ms
6 core1b-ctn-gi0-1.ip.isnet.net (168.209.2.4) 26.165 ms 26.456 ms 25.952 ms
7 te0-7-0-1.ccr21.lon02.atlas.cogentco.com (149.6.148.129) 204.908 ms 205.235 ms 205.503 ms
8 be2328.ccr21.lon01.atlas.cogentco.com (130.117.49.85) 191.707 ms 192.106 ms 192.435 ms
9 be2350.ccr41.lon13.atlas.cogentco.com (154.54.39.185) 195.744 ms 196.355 ms 195.100 ms
10 be2194.ccr41.ams03.atlas.cogentco.com (130.117.50.242) 219.176 ms 218.892 ms 219.235 ms
11 be2261.ccr41.fra03.atlas.cogentco.com (154.54.37.30) 202.678 ms 203.337 ms 202.859 ms
12 be2228.ccr21.muc01.atlas.cogentco.com (154.54.38.50) 214.853 ms 217.467 ms 214.580 ms
13 be2200.ccr21.vie01.atlas.cogentco.com (130.117.49.2) 214.037 ms 213.791 ms 214.542 ms
14 te1-1.mag01.vie01.atlas.cogentco.com (154.54.74.6) 212.924 ms 213.153 ms 214.156 ms
15 149.6.80.42 (149.6.80.42) 220.120 ms 220.847 ms 220.936 ms
16 ip-212-24-125-71.cyberservice.net (212.24.125.71) 224.443 ms 224.125 ms 223.523 ms

Afrihost

Traceroute has started…

traceroute to dl.vsl.co.at (212.24.125.71), 64 hops max, 72 byte packets
1 fritz.box (192.168.178.1) 0.614 ms 0.577 ms 0.311 ms
2 105-236-10-65-esr-lo.mtnbusiness.co.za (105.236.10.65) 8.626 ms 8.923 ms 8.506 ms
3 41.181.51.182 (41.181.51.182) 25.859 ms 26.084 ms 26.311 ms
4 tb-dca-2.za--qux-a.za.mtnbusiness.net (41.181.184.28) 27.253 ms 26.094 ms 73.729 ms
5 compj-cpt-1.mtnns.net (196.44.18.2) 26.251 ms 26.867 ms 26.444 ms
6 * ls-cr-2.uk--tb-cr-1.za.mtnns.net (196.44.31.113) 171.360 ms 170.414 ms
7 ls-pr-1.uk--ls-cr-2.uk-a.mtn.net (209.212.111.201) 184.684 ms 176.939 ms *
8 tengigabitethernet8-2.ar6.lon3.gblx.net (208.48.238.185) 177.244 ms 176.835 ms 176.778 ms
9 ae3-20g.scr3.lon3.gblx.net (67.17.73.94) 177.211 ms 178.271 ms 177.444 ms
10 lag1.ar9.lon3.gblx.net (67.17.72.21) 175.083 ms 169.979 ms 169.931 ms
11 cogent-1.ar9.lon3.gblx.net (64.208.110.110) 178.689 ms 178.486 ms 177.389 ms
12 be2350.ccr41.lon13.atlas.cogentco.com (154.54.39.185) 171.782 ms 171.447 ms 172.014 ms
13 be2194.ccr41.ams03.atlas.cogentco.com (130.117.50.242) 223.830 ms 223.105 ms 224.166 ms
14 be2261.ccr41.fra03.atlas.cogentco.com (154.54.37.30) 192.958 ms 192.033 ms 193.072 ms
15 be2228.ccr21.muc01.atlas.cogentco.com (154.54.38.50) 242.529 ms 242.632 ms 242.881 ms
16 be2200.ccr21.vie01.atlas.cogentco.com (130.117.49.2) 248.913 ms 249.471 ms 248.407 ms
17 * te1-1.mag01.vie01.atlas.cogentco.com (154.54.74.6) 248.852 ms 248.375 ms
18 149.6.80.42 (149.6.80.42) 210.245 ms 210.082 ms 210.644 ms
19 ip-212-24-125-71.cyberservice.net (212.24.125.71) 210.030 ms 209.802 ms 210.083 ms
Click to expand...

Traces are pretty similar. I tried the download myself. First one averaged just under 700kbps, but the second time seemed stuck around 200kbps. It may be how the content is being served, maybe one link is on a slower storage.
 
kohlhtor said:
I don't use torrent is all html download
Click to expand...

This was my 3rd attempt - averaged again just under 700Mbps (about the same as my speedtest)

TbwogH8.png
 
Trying to download the same file. Doesn't go over 20 KB/s.
This on a 4 mbps business line.

But my speedtest shows 1.16 mbps. So ja.......
 
Last edited:
Hi Afriman.

Finally managed to get the Afrihost Network Tester to work and run a test. The results are below. Would you mind looking at it and telling me if you can see anything that might suggest why my speeds are so bad?

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=57 time=34 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=57 time=28 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=57 time=47 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=57 time=43 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=57 time=29 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=41 time=221 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=41 time=236 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=41 time=232 ms
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5


Trace Test:

traceroute -n 197.242.144.102

1 192.168.0.1 7 ms 36 ms
2 105.236.9.1 35 ms 23 ms
3 41.181.178.7 22 ms
196.44.0.1 24 ms
4 196.44.0.1 41 ms
196.44.31.9 28 ms
5 196.44.31.9 47 ms
41.181.165.1 80 ms
6 196.44.31.9 41 ms 38 ms
7 196.31.220.6 25 ms
196.31.220.2 25 ms
8 196.31.220.2 33 ms
196.31.63.2 34 ms
9 196.31.63.2 54 ms
196.30.42.1 63 ms
10 197.242.144.1 25 ms 46 ms


traceroute -n 8.8.8.8

1 192.168.0.1 160 ms 1 ms
2 105.236.9.1 27 ms 20 ms
3 196.44.0.1 40 ms 43 ms
4 196.44.31.9 27 ms 36 ms
5 41.181.165.1 38 ms 24 ms
6 209.212.99.1 232 ms 236 ms
7 Request timed out * *
8 8.8.8.8 213 ms


DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 197.242.144.102


nslookup www.google.com

Name: www.google.com
Address: 74.125.230.80
Name: www.google.com
Address: 74.125.230.82
Name: www.google.com
Address: 74.125.230.83
Name: www.google.com
Address: 74.125.230.84
Name: www.google.com
Address: 74.125.230.81


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN
 
AfriMan said:
Packet loss looks like it's external to our network, but not what I'm seeing on my side. It could be internal routing within the receiving network.
Click to expand...

Sorry packet loss is only on Afrihost not on webafrica
Download Afrihost test
ImageUploadedByTapatalk1415212060.029936.jpg

Webafrica

ImageUploadedByTapatalk1415212175.868671.jpg

I have no packet loss on webafrica
I'm a network administrators I know what I'm talking

ImageUploadedByTapatalk1415212386.131763.jpg
 

Attachments

  • ImageUploadedByTapatalk1415212124.933919.jpg
    ImageUploadedByTapatalk1415212124.933919.jpg
    6.4 KB · Views: 217
Dianysis said:
Hi Afriman.

Finally managed to get the Afrihost Network Tester to work and run a test. The results are below. Would you mind looking at it and telling me if you can see anything that might suggest why my speeds are so bad?

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=57 time=34 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=57 time=28 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=57 time=47 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=57 time=43 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=57 time=29 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=41 time=221 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=41 time=236 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=41 time=232 ms
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5


Trace Test:

traceroute -n 197.242.144.102

1192.168.0.1 7 ms 36 ms
2105.236.9.1 35 ms 23 ms
341.181.178.7 22 ms
196.44.0.1 24 ms
4196.44.0.1 41 ms
196.44.31.9 28 ms
5196.44.31.9 47 ms
41.181.165.1 80 ms
6196.44.31.9 41 ms 38 ms
7196.31.220.6 25 ms
196.31.220.2 25 ms
8196.31.220.2 33 ms
196.31.63.2 34 ms
9196.31.63.2 54 ms
196.30.42.1 63 ms
10197.242.144.1 25 ms 46 ms


traceroute -n 8.8.8.8

1192.168.0.1 160 ms 1 ms
2105.236.9.1 27 ms 20 ms
3196.44.0.1 40 ms 43 ms
4196.44.31.9 27 ms 36 ms
541.181.165.1 38 ms 24 ms
6209.212.99.1 232 ms 236 ms
7Request timed out * *
88.8.8.8 213 ms


DNS Test:

nslookup www.afrihost.com

Name:www.afrihost.com
Address: 197.242.144.102


nslookup www.google.com

Name:www.google.com
Address: 74.125.230.80
Name:www.google.com
Address: 74.125.230.82
Name:www.google.com
Address: 74.125.230.83
Name:www.google.com
Address: 74.125.230.84
Name:www.google.com
Address: 74.125.230.81


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN
Click to expand...

The Afrihost network tester not showing packet loss
This tool is not accurate
 
cortexenslaver said:
You should maybe post results using Zertop's tools. They are much more comprehensive, accurate, and may help highlight where the problem is:

http://zertop.com/files/LineTool/Windows/Current/linetool.exe
http://zertop.com/files/DiagnosticsTool/Windows/Current/diagnostics.exe
Click to expand...

Please may I ask you a question - I am trying to download the Zertop Line Tool. It started to download (very slowly), then just drops to 0 B/s. That is most definitely not normal....... Or am I wrong?
 
Dianysis said:
Please may I ask you a question - I am trying to download the Zertop Line Tool. It started to download (very slowly), then just drops to 0 B/s. That is most definitely not normal....... Or am I wrong?
Click to expand...

Tried downloading again, and it just drop to 0 B/s and stopped.
 
ImageUploadedByTapatalk1415213944.320124.jpg




The packed loss is on the mtn network
| 10 | 41.181.198.188 | tb-dca-2.za--qux-c.za.mtnbusiness.net |
---------------------------------------------------------------

10 % packet loos

ImageUploadedByTapatalk1415213663.225162.jpg
 

Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 14ms
Your maximum ping was 166ms

Looking at your average ping, your line seems to be running perfectly :-)
Looking at your maximum ping, however, it seems as though there could be a serious intermittent fault on the line. This could be a cause of an issue. Please post the results (at the end of the program) into the forum for advice.


Detailed Report

Code: 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.236.13.129 with 32 bytes of data:
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=166ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=41ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=9ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254

Ping statistics for 105.236.13.129:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 7ms, Maximum = 166ms, Average = 14ms
 
2014/11/05 21:04:13.01 

Local Tracert 

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  home.gateway.pace.net [192.168.1.254] 
  2     7 ms     7 ms     6 ms  105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129] 
  3     8 ms     8 ms     8 ms  ipc-send-tb-3a.mtnbusiness.net [41.181.53.214] 
  4     9 ms    22 ms     8 ms  tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188] 
  5     8 ms     8 ms     8 ms  compj-cpt-1.mtnns.net [196.44.18.2] 
  6     9 ms     8 ms     9 ms  ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134] 
  7     8 ms     9 ms     8 ms  196.44.0.74 
  8     9 ms     9 ms     9 ms  196-28-178-141.adsl.mweb.co.za [196.28.178.141] 
  9    12 ms    12 ms    11 ms  tengig-0-0-0-1-cpt-p-1.mweb.co.za [197.84.7.1] 
 10    10 ms     9 ms     9 ms  vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254] 
 11    10 ms    10 ms    10 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
 12    10 ms     9 ms    10 ms  gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166] 
 13    10 ms     9 ms    12 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 14    11 ms    11 ms    10 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 15    10 ms    11 ms    10 ms  41-86-110-143.mweb.co.za [41.86.110.143] 

Trace complete.
  
International Tracert 

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  home.gateway.pace.net [192.168.1.254] 
  2     7 ms     7 ms     6 ms  105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129] 
  3     8 ms     8 ms     8 ms  41.181.51.182 
  4     8 ms     7 ms     8 ms  tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28] 
  5     8 ms     8 ms     9 ms  unc-cpt-1.mtnns.net [196.44.18.8] 
  6     9 ms     9 ms     8 ms  196.44.31.106 
  7   151 ms   151 ms   152 ms  am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221] 
  8   151 ms     *      152 ms  ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83] 
  9   152 ms   151 ms   151 ms  linx-gw1.thn.ncuk.net [195.66.224.240] 
 10   152 ms   152 ms   152 ms  te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17] 
 11   154 ms   153 ms   154 ms  te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85] 
 12   153 ms   151 ms   151 ms  www.thinkbroadband.com [80.249.99.130] 

Trace complete.
  
International Speedtest 
Downloaded 20.0 megabytes in 1:10 seconds. (289.20 KB/s)
  
Local Speedtest 
Downloaded 15.6 megabytes in 35 seconds. (455.63 KB/s)
  
  
  
  
Test End Timestamp 
2014/11/05 20:51:40.96

These results above show some issues with the network... NOT MY LINE
Look at the poor speeds... international is pathetic.

Oh yes, this is supposed to be a 10Mb line.
 
Last edited:
cortexenslaver said:

Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 14ms
Your maximum ping was 166ms

Looking at your average ping, your line seems to be running perfectly :-)
Looking at your maximum ping, however, it seems as though there could be a serious intermittent fault on the line. This could be a cause of an issue. Please post the results (at the end of the program) into the forum for advice.


Detailed Report

Code: 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.236.13.129 with 32 bytes of data:
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=166ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=41ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=9ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254

Ping statistics for 105.236.13.129:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 7ms, Maximum = 166ms, Average = 14ms
 
2014/11/05 21:04:13.01 

Local Tracert 

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  home.gateway.pace.net [192.168.1.254] 
  2     7 ms     7 ms     6 ms  105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129] 
  3     8 ms     8 ms     8 ms  ipc-send-tb-3a.mtnbusiness.net [41.181.53.214] 
  4     9 ms    22 ms     8 ms  tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188] 
  5     8 ms     8 ms     8 ms  compj-cpt-1.mtnns.net [196.44.18.2] 
  6     9 ms     8 ms     9 ms  ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134] 
  7     8 ms     9 ms     8 ms  196.44.0.74 
  8     9 ms     9 ms     9 ms  196-28-178-141.adsl.mweb.co.za [196.28.178.141] 
  9    12 ms    12 ms    11 ms  tengig-0-0-0-1-cpt-p-1.mweb.co.za [197.84.7.1] 
 10    10 ms     9 ms     9 ms  vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254] 
 11    10 ms    10 ms    10 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
 12    10 ms     9 ms    10 ms  gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166] 
 13    10 ms     9 ms    12 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 14    11 ms    11 ms    10 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 15    10 ms    11 ms    10 ms  41-86-110-143.mweb.co.za [41.86.110.143] 

Trace complete.
  
International Tracert 

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  home.gateway.pace.net [192.168.1.254] 
  2     7 ms     7 ms     6 ms  105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129] 
  3     8 ms     8 ms     8 ms  41.181.51.182 
  4     8 ms     7 ms     8 ms  tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28] 
  5     8 ms     8 ms     9 ms  unc-cpt-1.mtnns.net [196.44.18.8] 
  6     9 ms     9 ms     8 ms  196.44.31.106 
  7   151 ms   151 ms   152 ms  am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221] 
  8   151 ms     *      152 ms  ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83] 
  9   152 ms   151 ms   151 ms  linx-gw1.thn.ncuk.net [195.66.224.240] 
 10   152 ms   152 ms   152 ms  te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17] 
 11   154 ms   153 ms   154 ms  te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85] 
 12   153 ms   151 ms   151 ms  www.thinkbroadband.com [80.249.99.130] 

Trace complete.
  
International Speedtest 
Downloaded 20.0 megabytes in 1:10 seconds. (289.20 KB/s)
  
Local Speedtest 
Downloaded 15.6 megabytes in 35 seconds. (455.63 KB/s)
  
  
  
  
Test End Timestamp 
2014/11/05 20:51:40.96

These results above show some issues with the network... NOT MY LINE
Look at the poor speeds... international is pathetic.

Oh yes, this is supposed to be a 10Mb line.
Click to expand...

Hi.
I managed to download the Zertop Line Tool.
Here are the results:


Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 28ms
Your maximum ping was 36ms

Looking at your average ping, your line seems to be running perfectly :-)
Looking at your maximum ping, however, it seems as though there could be a slight intermittant issue on the line. If required, please post the results to a forum post.


Detailed Report

Code: 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.236.9.1 with 32 bytes of data:
Request timed out.
Reply from 105.236.9.1: bytes=32 time=32ms TTL=254
Reply from 105.236.9.1: bytes=32 time=36ms TTL=254
Reply from 105.236.9.1: bytes=32 time=30ms TTL=254
Reply from 105.236.9.1: bytes=32 time=26ms TTL=254
Reply from 105.236.9.1: bytes=32 time=34ms TTL=254
Reply from 105.236.9.1: bytes=32 time=23ms TTL=254
Reply from 105.236.9.1: bytes=32 time=28ms TTL=254
Reply from 105.236.9.1: bytes=32 time=23ms TTL=254
Reply from 105.236.9.1: bytes=32 time=24ms TTL=254
Reply from 105.236.9.1: bytes=32 time=36ms TTL=254
Reply from 105.236.9.1: bytes=32 time=33ms TTL=254
Reply from 105.236.9.1: bytes=32 time=32ms TTL=254
Reply from 105.236.9.1: bytes=32 time=35ms TTL=254
Reply from 105.236.9.1: bytes=32 time=28ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=31ms TTL=254
Reply from 105.236.9.1: bytes=32 time=23ms TTL=254
Reply from 105.236.9.1: bytes=32 time=23ms TTL=254
Reply from 105.236.9.1: bytes=32 time=23ms TTL=254
Reply from 105.236.9.1: bytes=32 time=29ms TTL=254
Reply from 105.236.9.1: bytes=32 time=36ms TTL=254
Reply from 105.236.9.1: bytes=32 time=34ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=31ms TTL=254
Reply from 105.236.9.1: bytes=32 time=35ms TTL=254
Reply from 105.236.9.1: bytes=32 time=28ms TTL=254
Reply from 105.236.9.1: bytes=32 time=30ms TTL=254
Request timed out.

Ping statistics for 105.236.9.1:
    Packets: Sent = 30, Received = 28, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 36ms, Average = 28ms
 
05/11/2014 21:15:14.87

I really appreciate the help.
 
Cortexenslaver, busy running the diagnostics tool. Using the 20 mb file for maximum information. Will pay results as soon as it is done. Very long though. Lol.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X