Afrihost Business Uncapped Feedback - 2

Status
Not open for further replies.
Line Tool on test account (Wired):

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

Your average ping was 23ms
Your maximum ping was 33ms

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:
Reply from 105.236.9.1: bytes=32 time=29ms TTL=254
Reply from 105.236.9.1: bytes=32 time=27ms TTL=254
Reply from 105.236.9.1: bytes=32 time=31ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=28ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=33ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=24ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=23ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=29ms TTL=254
Reply from 105.236.9.1: bytes=32 time=33ms TTL=254
Reply from 105.236.9.1: bytes=32 time=23ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=26ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254

Ping statistics for 105.236.9.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 33ms, Average = 23ms
 
05/11/2014 22:24:26.72


Diagnostics Tool on test account (Wired):

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 192.168.0.1
2 18 ms 18 ms 18 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.1]
3 20 ms 20 ms 20 ms ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178.89]
4 32 ms 26 ms 21 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 22 ms 20 ms 20 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 20 ms 20 ms 21 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 45 ms 22 ms 23 ms jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]
8 22 ms 22 ms 22 ms postfix.wipronet.co.za [196.22.161.133]
9 51 ms 51 ms 51 ms tengig-0-7-0-3-vic-p-1.mweb.co.za [197.80.7.1]
10 48 ms 47 ms 47 ms tengig-0-0-0-0-cpt-p-2.mweb.co.za [197.84.4.46]
11 48 ms 47 ms 46 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
12 47 ms 47 ms 47 ms 196.28.178.66
13 47 ms 46 ms 47 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
14 48 ms 47 ms 46 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
15 48 ms 48 ms 47 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
16 51 ms 47 ms 48 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 192.168.0.1
2 19 ms 18 ms 19 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.1]
3 21 ms 21 ms 21 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178.77]
4 23 ms 21 ms 22 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 22 ms 40 ms 22 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 25 ms 21 ms 20 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 225 ms 219 ms 220 ms ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.31.114]
8 218 ms 219 ms 218 ms ls-cr-1.uk--ls-cr-2.uk-a.mtnns.net [196.44.31.156]
9 219 ms 218 ms 219 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
10 305 ms 227 ms 222 ms linx-gw1.thn.ncuk.net [195.66.224.240]
11 202 ms 212 ms 216 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
12 220 ms 220 ms 220 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
13 203 ms 202 ms 208 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest
Downloaded 20.0 megabytes in 4:21 seconds. (78.25 KB/s)

Local Speedtest
Downloaded 15.6 megabytes in 43 seconds. (364.35 KB/s)




Test End Timestamp
05/11/2014 22:32:33.54


What a difference!!

I'd say this is proof that even though your line may be a bit wonky, the one common faulty thread here is Afrihost. There are many of us here that have the same problem.... Capped account flies, but our Business accounts are in the dumps. And, this is the case ALL OVER, no matter where you live in SA. It also seems to hve gotten worse after the "upgrades" :(
 
Busy trying wireless on the capped account.

Well all my **** started on Saturday 25th of October - two days after the IPC upgrades in the North.
So ja......

Before that my speeds were awesome (most of the time). Got nearly full line speeds some days.
 
Busy trying wireless on the capped account.

Well all my **** started on Saturday 25th of October - two days after the IPC upgrades in the North.
So ja......

Before that my speeds were awesome (most of the time). Got nearly full line speeds some days.

My speeds returned to what they used be from November last year to March this year... and then, after the upgrade in the SOUTH, in the toilet again. I don't think these guys (MTN) have a clue on how to affect a trouble free upgrade. Common sense says, that if your initial problems were caused by capacity shortage, then increasing capacity "should" eliminate the problems, not make them worse.
Yeah right :whistle: way to go AH and MTN :whistle:
 
Exactly. And what really grinds my gears- when you tell them you have a problem they say "there its reason for this to happen. We are seeing improved performance blah blah blah". Maybe in general there is improved performance but that doesn't change the fact that i have a problem.
 
Sorry. Meant to say "there isn't reason for this to happen...."
 
Line Tool with test (ie 1 gb capped account from AH) account (Wireless):


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

Your average ping was 23ms
Your maximum ping was 33ms

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:
Reply from 105.236.9.1: bytes=32 time=22ms 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=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=23ms TTL=254
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=27ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=28ms TTL=254
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=30ms TTL=254
Reply from 105.236.9.1: bytes=32 time=23ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Request timed out.
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=33ms TTL=254
Reply from 105.236.9.1: bytes=32 time=26ms TTL=254
Reply from 105.236.9.1: bytes=32 time=23ms TTL=254
Request timed out.
Request timed out.
Reply from 105.236.9.1: bytes=32 time=26ms TTL=254
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254

Ping statistics for 105.236.9.1:
    Packets: Sent = 30, Received = 27, Lost = 3 (10% loss),
Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 33ms, Average = 23ms
 
05/11/2014 22:35:25.40

Diagnostics tool with test account (Wireless):

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 192.168.0.1
2 19 ms 19 ms 19 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.1]
3 26 ms 29 ms 30 ms ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178.89]
4 22 ms 23 ms 22 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 * * 38 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 24 ms 22 ms 23 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 37 ms 33 ms 34 ms jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]
8 32 ms 36 ms 32 ms postfix.wipronet.co.za [196.22.161.133]
9 51 ms 54 ms 56 ms tengig-0-7-0-3-vic-p-1.mweb.co.za [197.80.7.1]
10 68 ms 56 ms 55 ms tengig-0-0-0-0-cpt-p-2.mweb.co.za [197.84.4.46]
11 48 ms 58 ms 47 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
12 50 ms 50 ms 48 ms 196.28.178.66
13 49 ms 47 ms 52 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
14 51 ms 48 ms 50 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
15 49 ms 49 ms 49 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
16 48 ms 51 ms 48 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 192.168.0.1
2 19 ms 22 ms 20 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.1]
3 33 ms 26 ms 38 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178.77]
4 24 ms 26 ms 25 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 24 ms 27 ms 32 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 25 ms 30 ms 37 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 220 ms 222 ms 228 ms ls-cr-2.uk--rb-cr-1.za-g.mtnns.net [196.44.31.114]
8 219 ms 229 ms 233 ms ls-cr-1.uk--ls-cr-2.uk-a.mtnns.net [196.44.31.156]
9 225 ms 224 ms 220 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
10 220 ms 219 ms 219 ms linx-gw1.thn.ncuk.net [195.66.224.240]
11 207 ms 203 ms 204 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
12 267 ms 220 ms 220 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
13 206 ms 205 ms 205 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest
Downloaded 20.0 megabytes in 5:07 seconds. (66.54 KB/s)

Local Speedtest
Downloaded 15.6 megabytes in 2:35 seconds. (102.78 KB/s)




Test End Timestamp
05/11/2014 22:45:12.19


Better than the first wireless test on my business account.
 
And also did a speedtest on saix.net using the capped account- 3.22 mbps download speed and 0.43 mbps upload speed.
 
Line Tool with test (ie 1 gb capped account from AH) account (Wireless):


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

Your average ping was 23ms
Your maximum ping was 33ms

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:
Reply from 105.236.9.1: bytes=32 time=22ms 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=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=23ms TTL=254
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=27ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=28ms TTL=254
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=30ms TTL=254
Reply from 105.236.9.1: bytes=32 time=23ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Request timed out.
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=33ms TTL=254
Reply from 105.236.9.1: bytes=32 time=26ms TTL=254
Reply from 105.236.9.1: bytes=32 time=23ms TTL=254
Request timed out.
Request timed out.
Reply from 105.236.9.1: bytes=32 time=26ms TTL=254
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254

Ping statistics for 105.236.9.1:
    Packets: Sent = 30, Received = 27, Lost = 3 (10% loss),
Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 33ms, Average = 23ms
 
05/11/2014 22:35:25.40

Diagnostics tool with test account (Wireless):

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 192.168.0.1
2 19 ms 19 ms 19 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.1]
3 26 ms 29 ms 30 ms ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178.89]
4 22 ms 23 ms 22 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 * * 38 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 24 ms 22 ms 23 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 37 ms 33 ms 34 ms jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]
8 32 ms 36 ms 32 ms postfix.wipronet.co.za [196.22.161.133]
9 51 ms 54 ms 56 ms tengig-0-7-0-3-vic-p-1.mweb.co.za [197.80.7.1]
10 68 ms 56 ms 55 ms tengig-0-0-0-0-cpt-p-2.mweb.co.za [197.84.4.46]
11 48 ms 58 ms 47 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
12 50 ms 50 ms 48 ms 196.28.178.66
13 49 ms 47 ms 52 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
14 51 ms 48 ms 50 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
15 49 ms 49 ms 49 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
16 48 ms 51 ms 48 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 192.168.0.1
2 19 ms 22 ms 20 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.1]
3 33 ms 26 ms 38 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178.77]
4 24 ms 26 ms 25 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 24 ms 27 ms 32 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 25 ms 30 ms 37 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 220 ms 222 ms 228 ms ls-cr-2.uk--rb-cr-1.za-g.mtnns.net [196.44.31.114]
8 219 ms 229 ms 233 ms ls-cr-1.uk--ls-cr-2.uk-a.mtnns.net [196.44.31.156]
9 225 ms 224 ms 220 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
10 220 ms 219 ms 219 ms linx-gw1.thn.ncuk.net [195.66.224.240]
11 207 ms 203 ms 204 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
12 267 ms 220 ms 220 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
13 206 ms 205 ms 205 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest
Downloaded 20.0 megabytes in 5:07 seconds. (66.54 KB/s)

Local Speedtest
Downloaded 15.6 megabytes in 2:35 seconds. (102.78 KB/s)




Test End Timestamp
05/11/2014 22:45:12.19


Better than the first wireless test on my business account.

Might be a good plan to try another ISP account, maybe WebAfrica?
If the stats are roughly as good as the Capped AH, then getting Telkom to stabilise your line a bit will help a lot ;)
 
Thank you. Will look into getting a free account with web Africa to test. Thanks for your help. You the real mvp.
 
Thank you. Will look into getting a free account with web Africa to test. Thanks for your help. You the real mvp.

Anytime.... spent a lot of time here this year on this thread. Glad I could help, and maybe steer you in the right direction. We all know how annoying it is when you know there's a problem, but keep getting told to prove it over and over again ;)
 
I have just switched back to my business account and bam - 0.97 mbps download speed. And that is on a wired connection. Something is F***ED UP!
 
So I decided to stay up a little later tonight to test my theory, as soon as the network presumably becomes less contended due to people going to sleep and not using their internet, my speeds go back to how they should be

3886860537.png

Compared to the usual

3883927613.png
 
Hmm, yeah I tested on a capped Plugg account this evening and it ran everything I threw at it beautifully, with no issues whatsoever. Switch back and forth between Plugg account and AH business uncapped acc and it becomes obvious the issue is not with my line. The speedtests and ping on AH account look like this: /\/\/\/\/\/\ and the plugg account was nice and smooth throughout. Flat, constant speed and ping.

Afripeople, I have PM'd as requested. No reply yet.
 
Ok cool. Thank you. Will try get hold of a router and do the tests again to see. And thanks again for all your help. Feel like i am at least getting somewhere now.

Have you had these results passed onto our team too?
 
So I decided to stay up a little later tonight to test my theory, as soon as the network presumably becomes less contended due to people going to sleep and not using their internet, my speeds go back to how they should be

View attachment 164595

Compared to the usual

View attachment 164603

The network was definitely quieter at the time of posting. Did you manage to run any other tests? Perhaps with a different ISP?
 
Hmm, yeah I tested on a capped Plugg account this evening and it ran everything I threw at it beautifully, with no issues whatsoever. Switch back and forth between Plugg account and AH business uncapped acc and it becomes obvious the issue is not with my line. The speedtests and ping on AH account look like this: /\/\/\/\/\/\ and the plugg account was nice and smooth throughout. Flat, constant speed and ping.

Afripeople, I have PM'd as requested. No reply yet.

Sorry to hear this :(
We're usually only around until 8pm or so. I don't have a PM from you, did you maybe PM AfriMan?
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X