Afrihost Business Uncapped Feedback - 2

Status
Not open for further replies.
There are no timeframes confirmed at this stage, any updates will be communicated as soon as they're available.
When will they be confirmed?

*Edit: Actually one of your support staff has told me "[...] So as of next week things should be back to normal."
 
Last edited:
It can only get better from here :)

It has been getting worse in terms of network reliability... when I had latency issues at least my packets arrived at their destinations.

*Edit: kinda reminds me of our lovely postal services lol.
Afrihost.com
Pure Internet Joy!
 
Last edited:
3 oçlock in the am

Pinging www.afrihost.com [41.181.185.18] with 32 bytes of da
Reply from 41.181.185.18: bytes=32 time=488ms TTL=56
Reply from 41.181.185.18: bytes=32 time=361ms TTL=56
Request timed out.
Request timed out.
Reply from 41.181.185.18: bytes=32 time=288ms TTL=56
Reply from 41.181.185.18: bytes=32 time=435ms TTL=56
Reply from 41.181.185.18: bytes=32 time=315ms TTL=56
Reply from 41.181.185.18: bytes=32 time=390ms TTL=56
Reply from 41.181.185.18: bytes=32 time=305ms TTL=56
Reply from 41.181.185.18: bytes=32 time=400ms TTL=56
Reply from 41.181.185.18: bytes=32 time=410ms TTL=56
Reply from 41.181.185.18: bytes=32 time=413ms TTL=56

Ping statistics for 41.181.185.18:
Packets: Sent = 12, Received = 10, Lost = 2 (16% loss),
Approximate round trip times in milli-seconds:
Minimum = 288ms, Maximum = 488ms, Average = 380ms

_____________________________________________________________________

Tracing route to www.afrihost.co.za [41.181.185.18]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.1.1
2 358 ms 374 ms 421 ms 105-236-1-1-esr-lo.mtnbusiness.co.za [105.236.1.
1]
3 414 ms 353 ms 364 ms 41.181.221.214
4 214 ms 387 ms 293 ms rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.118]
5 375 ms 224 ms 432 ms rb-cr-2.za--rb-dca-2.za-b.mtnns.net [196.44.0.15
5]
6 332 ms 400 ms 447 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
7 479 ms * 328 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.21
7]
8 389 ms 355 ms 365 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18
]

Trace complete.


Please don't ask me to do further testing ......... not going to happen.

I assume by the time I get back home at 18H00 Friday, this wont be an issue.
 
3 oçlock in the am

Pinging www.afrihost.com [41.181.185.18] with 32 bytes of da
Reply from 41.181.185.18: bytes=32 time=488ms TTL=56
Reply from 41.181.185.18: bytes=32 time=361ms TTL=56
Request timed out.
Request timed out.
Reply from 41.181.185.18: bytes=32 time=288ms TTL=56
Reply from 41.181.185.18: bytes=32 time=435ms TTL=56
Reply from 41.181.185.18: bytes=32 time=315ms TTL=56
Reply from 41.181.185.18: bytes=32 time=390ms TTL=56
Reply from 41.181.185.18: bytes=32 time=305ms TTL=56
Reply from 41.181.185.18: bytes=32 time=400ms TTL=56
Reply from 41.181.185.18: bytes=32 time=410ms TTL=56
Reply from 41.181.185.18: bytes=32 time=413ms TTL=56

Ping statistics for 41.181.185.18:
Packets: Sent = 12, Received = 10, Lost = 2 (16% loss),
Approximate round trip times in milli-seconds:
Minimum = 288ms, Maximum = 488ms, Average = 380ms

_____________________________________________________________________

Tracing route to www.afrihost.co.za [41.181.185.18]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.1.1
2 358 ms 374 ms 421 ms 105-236-1-1-esr-lo.mtnbusiness.co.za [105.236.1.
1]
3 414 ms 353 ms 364 ms 41.181.221.214
4 214 ms 387 ms 293 ms rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.118]
5 375 ms 224 ms 432 ms rb-cr-2.za--rb-dca-2.za-b.mtnns.net [196.44.0.15
5]
6 332 ms 400 ms 447 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
7 479 ms * 328 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.21
7]
8 389 ms 355 ms 365 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18
]

Trace complete.


Please don't ask me to do further testing ......... not going to happen.

I assume by the time I get back home at 18H00 Friday, this wont be an issue.

Latency on the graphs shows normal around that time - very weird. Perhaps it was limited to certain areas, so it averages out on high level report :(
 
When will they be confirmed?

*Edit: Actually one of your support staff has told me "[...] So as of next week things should be back to normal."

Gian's latest post on his thread says that we hope to give out usernames early next week, which will in the two week time period he had initially mentioned.
 
Latency very inconsistent. One moment being thrown off a Skype call, the next all fine.

Afrihost Trace:
Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms wall.exa [10.0.0.254]
2 6 ms 7 ms 25 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129]
3 123 ms 53 ms 79 ms 41.181.201.94
4 7 ms 7 ms 17 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 8 ms 7 ms 22 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 15 ms 22 ms 7 ms 196.44.31.106
7 8 ms 18 ms 21 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 42 ms 89 ms 170 ms 1122.te0-0-0.cpt-pr-1.optinet.net [196.28.178.141]
9 22 ms 12 ms 11 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]
10 9 ms 17 ms 8 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
11 19 ms 25 ms 16 ms 196.28.178.66
12 19 ms 12 ms 9 ms cte-core-sw2.vwol.net [196.41.144.35]
13 19 ms 9 ms 9 ms www.mweb.co.za [196.2.63.110]

Trace complete.

Telkom Trace:
Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms wall.exa [10.0.0.254]
2 6 ms 6 ms 6 ms wblv-ip-bng-1.south.dsl.telkomsa.net [105.224.220.1]
3 7 ms 7 ms 8 ms ipc-4-up.south.dsl.telkomsa.net [105.226.0.30]
4 9 ms 8 ms 6 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]
5 9 ms 9 ms 7 ms blv-pr-02-be200-vl1.net.telkomsa.net [105.226.0.54]
6 7 ms 8 ms 12 ms ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
7 11 ms 8 ms 10 ms mweb.ct1.napafrica.net [196.10.140.15]
8 35 ms 54 ms 31 ms bu-ether1.cpt-p-1.optinet.net [197.84.7.33]
9 29 ms 28 ms 28 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
10 42 ms 30 ms 29 ms 196.28.178.66
11 33 ms 30 ms 31 ms cte-core-sw2.vwol.net [196.41.144.35]
12 33 ms 30 ms 30 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
Latency very inconsistent. One moment being thrown off a Skype call, the next all fine.

Afrihost Trace:
Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms wall.exa [10.0.0.254]
2 6 ms 7 ms 25 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129]
3 123 ms 53 ms 79 ms 41.181.201.94
4 7 ms 7 ms 17 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 8 ms 7 ms 22 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 15 ms 22 ms 7 ms 196.44.31.106
7 8 ms 18 ms 21 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 42 ms 89 ms 170 ms 1122.te0-0-0.cpt-pr-1.optinet.net [196.28.178.141]
9 22 ms 12 ms 11 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]
10 9 ms 17 ms 8 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
11 19 ms 25 ms 16 ms 196.28.178.66
12 19 ms 12 ms 9 ms cte-core-sw2.vwol.net [196.41.144.35]
13 19 ms 9 ms 9 ms www.mweb.co.za [196.2.63.110]

Trace complete.

Telkom Trace:
Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms wall.exa [10.0.0.254]
2 6 ms 6 ms 6 ms wblv-ip-bng-1.south.dsl.telkomsa.net [105.224.220.1]
3 7 ms 7 ms 8 ms ipc-4-up.south.dsl.telkomsa.net [105.226.0.30]
4 9 ms 8 ms 6 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]
5 9 ms 9 ms 7 ms blv-pr-02-be200-vl1.net.telkomsa.net [105.226.0.54]
6 7 ms 8 ms 12 ms ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
7 11 ms 8 ms 10 ms mweb.ct1.napafrica.net [196.10.140.15]
8 35 ms 54 ms 31 ms bu-ether1.cpt-p-1.optinet.net [197.84.7.33]
9 29 ms 28 ms 28 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
10 42 ms 30 ms 29 ms 196.28.178.66
11 33 ms 30 ms 31 ms cte-core-sw2.vwol.net [196.41.144.35]
12 33 ms 30 ms 30 ms www.mweb.co.za [196.2.63.110]

Trace complete.

I can see that in your results. Definitely looks like what you're describing :(

What region are you connecting from?
 
Just to illustrate the point even further. There traces were done 1 minute apart both on Afrihost account.
At this stage I'm switching over to Telkom every time I need to do Remote Desktop or Skype support

Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 4 ms <1 ms <1 ms wall.exa [10.0.0.254]
2 6 ms 6 ms 6 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129]
3 * * * Request timed out.
4 * 11 ms 10 ms 41.181.222.102
5 * 10 ms 10 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
6 12 ms 10 ms 11 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 * 48 ms 11 ms 196.44.31.106
8 11 ms 10 ms 10 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
9 12 ms 11 ms 12 ms 1122.te0-0-0.cpt-pr-1.optinet.net [196.28.178.141]
10 17 ms 13 ms 15 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]
11 15 ms 12 ms 12 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
12 44 ms 11 ms 12 ms 196.28.178.66
13 29 ms 12 ms 14 ms cte-core-sw2.vwol.net [196.41.144.35]
14 12 ms 12 ms 12 ms www.mweb.co.za [196.2.63.110]

Trace complete.

Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms wall.exa [10.0.0.254]
2 6 ms 6 ms 6 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129]
3 * * 11 ms 41.181.222.101
4 11 ms 10 ms 10 ms 41.181.222.102
5 15 ms 11 ms 10 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
6 20 ms 11 ms 14 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 11 ms 11 ms 11 ms 196.44.31.106
8 671 ms 649 ms 636 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
9 625 ms 674 ms 834 ms 1122.te0-0-0.cpt-pr-1.optinet.net [196.28.178.141]
10 869 ms 741 ms 848 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]
11 918 ms 770 ms 41 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
12 41 ms 12 ms 12 ms 196.28.178.66
13 22 ms 14 ms * cte-core-sw2.vwol.net [196.41.144.35]
14 13 ms 14 ms 15 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
Poor speeds from Afrihost on the 4Mbps business account:

http://netgauge.ookla.com/share/228158191.png

I've asked for a refund and will pause the account until Afrihost can sort out the issues, in the interim I will sign up for a temporary solution with another ISP.

@Afriman what would be the costs if I pause the data connection from next month (the business account is bundled)?
 
Poor speeds from Afrihost on the 4Mbps business account:

http://netgauge.ookla.com/share/228158191.png

I've asked for a refund and will pause the account until Afrihost can sort out the issues, in the interim I will sign up for a temporary solution with another ISP.

@Afriman what would be the costs if I pause the data connection from next month (the business account is bundled)?

Once you pause the account, you don't pay for the period that you are paused for, unless you unpause, in which case there should be a pro-rata calculation for the remainder of that month.
 
Just to illustrate the point even further. There traces were done 1 minute apart both on Afrihost account.
At this stage I'm switching over to Telkom every time I need to do Remote Desktop or Skype support

Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 4 ms <1 ms <1 ms wall.exa [10.0.0.254]
2 6 ms 6 ms 6 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129]
3 * * * Request timed out.
4 * 11 ms 10 ms 41.181.222.102
5 * 10 ms 10 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
6 12 ms 10 ms 11 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 * 48 ms 11 ms 196.44.31.106
8 11 ms 10 ms 10 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
9 12 ms 11 ms 12 ms 1122.te0-0-0.cpt-pr-1.optinet.net [196.28.178.141]
10 17 ms 13 ms 15 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]
11 15 ms 12 ms 12 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
12 44 ms 11 ms 12 ms 196.28.178.66
13 29 ms 12 ms 14 ms cte-core-sw2.vwol.net [196.41.144.35]
14 12 ms 12 ms 12 ms www.mweb.co.za [196.2.63.110]

Trace complete.

Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms wall.exa [10.0.0.254]
2 6 ms 6 ms 6 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129]
3 * * 11 ms 41.181.222.101
4 11 ms 10 ms 10 ms 41.181.222.102
5 15 ms 11 ms 10 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
6 20 ms 11 ms 14 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 11 ms 11 ms 11 ms 196.44.31.106
8 671 ms 649 ms 636 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
9 625 ms 674 ms 834 ms 1122.te0-0-0.cpt-pr-1.optinet.net [196.28.178.141]
10 869 ms 741 ms 848 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]
11 918 ms 770 ms 41 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
12 41 ms 12 ms 12 ms 196.28.178.66
13 22 ms 14 ms * cte-core-sw2.vwol.net [196.41.144.35]
14 13 ms 14 ms 15 ms www.mweb.co.za [196.2.63.110]

Trace complete.

Definitely look pretty horrible there. Not sure why we're seeing latency looking better on our reports, but I'll have our guy in CT test as well. He was also seeing packet loss on his side yesterday :(
 
will the internet work this weekend or will it be a nightmare again as soon as the weekend starts
i hope ah will have some special rebate for the customers that we don't have to insist on next week when the problems are supposed to be sorted out
 
I'm guessing they someone used to work in customs before and old habits die hard :P

We're reserving some packets for the NSA today.






Seriously though, this should have been sorted out :( Will follow up with our guys on the progress of this.
 
We're reserving some packets for the NSA today.






Seriously though, this should have been sorted out :( Will follow up with our guys on the progress of this.

Still getting that bad latency in minecraft :(

hp8Ksc3.png
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X