Afrihost Business Uncapped Feedback

[AfriGuy]

Thanks, this would answer the PM I sent, however, not to stir or anything, but a reply (which never happened) would have been the right thing to do.

Sorry
I still have 20 odd PMs that are pending from Thursday/ Friday last week.

 

[wingnut771]

Yes it's the same on all accounts I've tested. I don't understand, then why did more than one Telkom tech inform me that everything was peachy at the exchange? And the reply I got from TelkomZA "As per our ADSl test tools, we checked the exchange you are attached to - Congella 4 - the utilization graph shows no errors, the Bandwidth Uplink is only operating at 14%, which means this exchange isn't being utilized during office and peak times. more than enough capacity available." Is that also bull****?

I suspect a faulty line as your upload SNR stats are not good.

EDIT: Out of interest, what does test my line say?

 

[Mypro-D]

Still baaaad!

 

[PurSpyk!!]

Spoke too soon, speed crap again. 8mb Business Uncapped .

Last Result:
Download Speed: 2014 kbps (251.8 KB/sec transfer rate)
Upload Speed: 859 kbps (107.4 KB/sec transfer rate)
Latency: 17 ms
Monday, 14 April 2014 19:44

 

[Zertop]

Wow Guys, if you ever want an example of intermittent line issues:

Tracing route to google.co.za [173.194.113.183]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.1
2 2111 ms 2099 ms 2155 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 1981 ms 1810 ms 1568 ms 41.181.51.182
4 1927 ms 943 ms 702 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 665 ms 557 ms 316 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 236 ms 152 ms 163 ms ls-cr-2.uk--tb-cr-1.za.mtnns.net [196.44.31.113]
7 198 ms 173 ms 211 ms am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.183]
8 163 ms 170 ms 195 ms am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.141]
9 219 ms 176 ms 161 ms core2.ams.net.google.com [195.69.145.100]
10 259 ms 285 ms 297 ms 209.85.254.90
11 289 ms 315 ms 289 ms 72.14.238.153
12 168 ms 184 ms 177 ms 209.85.254.233
13 232 ms 211 ms 258 ms 209.85.255.61
14 198 ms 294 ms 290 ms 72.14.233.217

Sigh... this usually fixes itself in an hour.


Z

 

[Mypro-D]

Well thankfully it is not my line.

 

[mugikhan]

Noise Margin and Attenuation are usually a function of the quality of the cabling in your area and the distance from the exchange. In some cases, replacing cabling, or upgrading fibre to the exchange or DP does make a huge improvement, but that's generally scheduled by Telkom - not in response to a fault.

General fixes implemented by technicians only usually marginally improve these stats. Also, if distance is the determining factor - you may need to wait until Telkom build more infrastructure in your area.

So basically I am screwed until Telkom decides to do something...My problem is that it was running fine two months ago and now all of a sudden my noise margin has become really bad :/

 

[Zertop]

I'm sorted again

 

[Zertop]

So basically I am screwed until Telkom decides to do something...My problem is that it was running fine two months ago and now all of a sudden my noise margin has become really bad :/

Hmm... Do you have line filters on everything? Those things are like the devil to ADSL if they break.

Also - how hard has it been raining in your area? Rain can cause issues on a line if its prolonged.

I wish you luck! Telkom can be a pain, but sometimes they really know what they are doing!

Z

 

[mugikhan]

Got new filters only have one phone connected and it was raining for that 'one' week and not very hard but after that no rain. I have had a fault open for about two weeks now without any resolution in sight *sigh*

 

[Zertop]

Got new filters only have one phone connected and it was raining for that 'one' week and not very hard but after that no rain. I have had a fault open for about two weeks now without any resolution in sight *sigh*

And alarm?

 

[mugikhan]

I don't know where to put it for the alarm...

 

[cortexenslaver]

These tests don't really show how bad my line is at the moment

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=10ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Reply from 105.236.13.129: bytes=32 time=9ms TTL=254
Reply from 105.236.13.129: bytes=32 time=10ms 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=54ms 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=42ms TTL=254
Reply from 105.236.13.129: bytes=32 time=13ms TTL=254
Reply from 105.236.13.129: bytes=32 time=9ms TTL=254
Reply from 105.236.13.129: bytes=32 time=55ms TTL=254
Reply from 105.236.13.129: bytes=32 time=52ms 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=22ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=10ms TTL=254
Reply from 105.236.13.129: bytes=32 time=24ms TTL=254
Reply from 105.236.13.129: bytes=32 time=54ms TTL=254
Reply from 105.236.13.129: bytes=32 time=33ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=30ms TTL=254
Reply from 105.236.13.129: bytes=32 time=48ms TTL=254
Reply from 105.236.13.129: bytes=32 time=11ms TTL=254
Reply from 105.236.13.129: bytes=32 time=39ms TTL=254
Reply from 105.236.13.129: bytes=32 time=28ms TTL=254
Reply from 105.236.13.129: bytes=32 time=30ms 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 = 55ms, Average = 22ms

2014/04/14 20:37:28.04

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 7 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129]
3 8 ms 8 ms 9 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
4 18 ms 13 ms 12 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 17 ms 14 ms 12 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 11 ms 11 ms 10 ms 196.44.0.74
8 10 ms 9 ms 9 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 17 ms 15 ms 13 ms 197-84-7-2.cpt.mweb.co.za [197.84.7.2]
10 9 ms 10 ms 10 ms 197-84-5-254.cpt.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 10 ms 10 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
13 11 ms 10 ms 9 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
14 10 ms 10 ms 11 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
15 10 ms 10 ms 9 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 7 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129]
3 9 ms 8 ms 7 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
4 * 8 ms 74 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 8 ms 196.44.31.106
7 152 ms 153 ms 153 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221]
8 159 ms 154 ms 152 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
9 152 ms 152 ms 152 ms linx-gw1.thn.ncuk.net [195.66.224.240]
10 154 ms 163 ms 154 ms gi1-24-10-star1.core-rs2.thdo.ncuk.net [80.249.97.9]
11 153 ms 152 ms 153 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest
Downloaded 20.0 megabytes in 33 seconds. (615.53 KB/s)

Local Speedtest
Downloaded 15.6 megabytes in 1:58 seconds. (135.01 KB/s)

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=58 time=29 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=58 time=29 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=58 time=30 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=58 time=28 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=58 time=29 ms


ping 8.8.8.8

Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
64 bytes from 8.8.8.8: icmp_req=3 ttl=45 time=181 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=45 time=180 ms
Request timeout for icmp_seq 5


Trace Test:

traceroute -n 197.242.144.102

1 192.168.1.2 1 ms 1 ms
2 105.236.13.1 12 ms 7 ms
3 41.181.198.1 11 ms
41.181.201.9 8 ms
4 196.44.31.1 12 ms
41.181.198.1 8 ms
5 196.44.31.6 30 ms
196.44.18.2 8 ms
6 196.44.0.2 26 ms
196.44.31.1 8 ms
7 196.30.1.5 28 ms
196.44.31.6 29 ms
8 196.31.220.2 29 ms
196.44.0.2 32 ms
9 196.31.63.2 29 ms
196.30.1.5 31 ms
10 196.30.42.1 30 ms
196.31.220.2 32 ms
11 197.242.144.1 29 ms
196.31.63.2 29 ms
12 197.242.144.1 29 ms


traceroute -n 8.8.8.8

1 192.168.1.2 1 ms 1 ms
2 105.236.13.1 7 ms 7 ms
3 41.181.53.1 10 ms 8 ms
4 41.181.198.1 17 ms 11 ms
5 196.44.18.2 8 ms 20 ms
6 196.44.31.1 9 ms 14 ms
7 196.44.31.6 53 ms 28 ms
8 41.181.139.1 27 ms 34 ms
9 Request timed out *
72.14.194.7 59 ms
10 66.249.95.8 170 ms
11 Request timed out *


DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 197.242.144.102


nslookup www.google.com

Name: www.google.com
Address: 173.194.41.179
Name: www.google.com
Address: 173.194.41.176
Name: www.google.com
Address: 173.194.41.178
Name: www.google.com
Address: 173.194.41.177
Name: www.google.com
Address: 173.194.41.180


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN


My speeds are choppy and downloads mostly don't complete, or get stuck... plus, I get a lot of corrupt files, and torrents are non-existent - still no word from Telkom on my open call

 

[LegionECX]

2mb business uncapped with Afrihost:



Usually tested to CT, all of a sardine to Jhb...

 

[zyro]

I'm guessing this isn't good.. Line issue?

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

1 <1 ms <1 ms <1 ms 192.168.1.254
2 * * * Request timed out.
3 1232 ms 935 ms 1168 ms 41.181.53.149
4 467 ms 454 ms 497 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150
]
5 1110 ms 1018 ms 1098 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
6 998 ms 820 ms 742 ms compj-cpt-1.mtnns.net [196.44.18.2]
7 1091 ms 1042 ms 998 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

8 1029 ms 1090 ms 904 ms 196.44.0.74
9 1006 ms 993 ms 1035 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]

10 936 ms 1038 ms 957 ms 197-84-7-2.cpt.mweb.co.za [197.84.7.2]
11 1079 ms 1161 ms 1074 ms 197-84-5-254.cpt.mweb.co.za [197.84.5.254]
12 1003 ms 1189 ms 959 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
13 1241 ms 1243 ms 816 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]

14 908 ms 1023 ms 1058 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
15 1154 ms 1264 ms 907 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
16 * 1101 ms 1181 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.

 

[Zertop]

I don't know where to put it for the alarm...

Is your alarm connected to the phone line? If so, you should just be able to stick one on the end

However, if you have a radio alarm, it isn't needed.

 

[Zertop]

I'm guessing this isn't good.. Line issue?

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

1 <1 ms <1 ms <1 ms 192.168.1.254
2 * * * Request timed out.
3 1232 ms 935 ms 1168 ms 41.181.53.149
4 467 ms 454 ms 497 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150
]
5 1110 ms 1018 ms 1098 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
6 998 ms 820 ms 742 ms compj-cpt-1.mtnns.net [196.44.18.2]
7 1091 ms 1042 ms 998 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

8 1029 ms 1090 ms 904 ms 196.44.0.74
9 1006 ms 993 ms 1035 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]

10 936 ms 1038 ms 957 ms 197-84-7-2.cpt.mweb.co.za [197.84.7.2]
11 1079 ms 1161 ms 1074 ms 197-84-5-254.cpt.mweb.co.za [197.84.5.254]
12 1003 ms 1189 ms 959 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
13 1241 ms 1243 ms 816 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]

14 908 ms 1023 ms 1058 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
15 1154 ms 1264 ms 907 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
16 * 1101 ms 1181 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.

Doesn't look good

Please run my second tool in my sig

 

[PurSpyk!!]

Getting and 8th of my speed

Last Result:
Download Speed: 1061 kbps (132.6 KB/sec transfer rate)
Upload Speed: 847 kbps (105.9 KB/sec transfer rate)
Latency: 35 ms
Monday, 14 April 2014 21:46

 

[zyro]

Doesn't look good

Please run my second tool in my sig

Hasn't been a good year for internet ><

Tried your app, but doesn't seem to like me.

Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)
Bad parameter *.

2014-04-14 21:44:59,14


EDIT: "80 was unexpected at this time." appears on the screen after "Press any key to continue..."

 

[skoenman]

Guys not to be a DOOM sayer but the 18th is a holiday??? wont this affect the install??? some feedback??