Afrihost Business Uncapped Feedback - 2

Status
Not open for further replies.
Judging by the myadsl forums and your facebook page I doubt that its a small amount of people. I think its just people that know what to look for that report the packet loss and poor latency.
 
why is it always after hours and over weekends when nobody is around is this when you do your testing and upgrades without notifying the customers
 
Mypro-D said:
Judging by the myadsl forums and your facebook page I doubt that its a small amount of people. I think its just people that know what to look for that report the packet loss and poor latency.
Click to expand...

While there are clients talking about this, it's still a really small group of users though. If there was a major outage we'd be much, much busier.
 
MonkeysUncle said:
Mine is also down the drain.

Speedtest:


Traceroute:

PS C:\Users\HomePC> tracert afrihost.com

Tracing route to afrihost.com [197.242.144.102]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * 18 ms 19 ms ipc-recieve-jh-2a.za.mtnbusiness.net [41.181.178.17]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * 20 ms 196.31.220.8
10 * * * Request timed out.
11 * 19 ms 20 ms 196.31.63.206
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 21 ms * * cms-gm.afrihost.com [197.242.144.102]
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
Click to expand...
Just to add. This is a 6Mbps account
 
Hey guys

Just a quick update, the changes made should take about an hour or two to reflect across the network - please re-test then :) I'm confident that things will be sorted by then. Really sorry about the slow throughput now, I know it sucks.
 
But thats around the time when the issues resolve themself? Then it will be weekend. Generally there are no issues on weekends, I would imagine because the network wouldn't be under pressure.
 
Ping is quite erratic atm:

Tracing route to afrihost.com [197.242.144.102]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms dsldevice.domain.name [192.168.0.2]
2 10 ms 9 ms 8 ms 105-236-10-129-esr-lo.mtnbusiness.co.za [105.236.10.129]
3 21 ms 17 ms 16 ms 41.181.51.182
4 42 ms 25 ms 21 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 31 ms 19 ms 40 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 43 ms 38 ms 35 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]

7 54 ms 39 ms 35 ms jh-cr-2.za--jh-cr-1.za-a.mtnns.net [196.44.31.255]
8 39 ms 64 ms 36 ms 196.44.31.99
9 57 ms 47 ms 35 ms 196.30.1.39
10 34 ms 64 ms 33 ms 196.31.220.21
11 39 ms 54 ms 46 ms 196.31.63.202
12 33 ms 44 ms 50 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
13 46 ms 35 ms 55 ms cms-gm.afrihost.com [197.242.144.102]


Pinging ipc-recieve-tb-3a.mtnbusiness.net [41.181.53.214] with 32 bytes of data:

Reply from 41.181.53.214: bytes=32 time=23ms TTL=59
Reply from 41.181.53.214: bytes=32 time=15ms TTL=59
Reply from 41.181.53.214: bytes=32 time=32ms TTL=59
Reply from 41.181.53.214: bytes=32 time=13ms TTL=59
Reply from 41.181.53.214: bytes=32 time=40ms TTL=59
Reply from 41.181.53.214: bytes=32 time=15ms TTL=59
Reply from 41.181.53.214: bytes=32 time=26ms TTL=59
Reply from 41.181.53.214: bytes=32 time=22ms TTL=59
Reply from 41.181.53.214: bytes=32 time=15ms TTL=59
Reply from 41.181.53.214: bytes=32 time=19ms TTL=59
Reply from 41.181.53.214: bytes=32 time=24ms TTL=59
Reply from 41.181.53.214: bytes=32 time=12ms TTL=59
Reply from 41.181.53.214: bytes=32 time=15ms TTL=59
Reply from 41.181.53.214: bytes=32 time=99ms TTL=59
Reply from 41.181.53.214: bytes=32 time=44ms TTL=59
Reply from 41.181.53.214: bytes=32 time=47ms TTL=59
Reply from 41.181.53.214: bytes=32 time=36ms TTL=59
Reply from 41.181.53.214: bytes=32 time=39ms TTL=59
Reply from 41.181.53.214: bytes=32 time=43ms TTL=59
Reply from 41.181.53.214: bytes=32 time=37ms TTL=59
Reply from 41.181.53.214: bytes=32 time=25ms TTL=59
Reply from 41.181.53.214: bytes=32 time=32ms TTL=59
Reply from 41.181.53.214: bytes=32 time=53ms TTL=59
 
East region .... Browsing all over the show.

Not too sure what to make of it all ATM

Pinging www.afrihost.com [197.242.144.102] with 32 bytes of da
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=17ms TTL=58
Reply from 197.242.144.102: bytes=32 time=17ms TTL=58
Reply from 197.242.144.102: bytes=32 time=19ms TTL=58
Reply from 197.242.144.102: bytes=32 time=18ms TTL=58
Reply from 197.242.144.102: bytes=32 time=23ms TTL=58
Reply from 197.242.144.102: bytes=32 time=20ms TTL=58
Reply from 197.242.144.102: bytes=32 time=19ms TTL=58
Reply from 197.242.144.102: bytes=32 time=19ms TTL=58
Reply from 197.242.144.102: bytes=32 time=18ms TTL=58
Reply from 197.242.144.102: bytes=32 time=61ms TTL=58
Reply from 197.242.144.102: bytes=32 time=22ms TTL=58
Reply from 197.242.144.102: bytes=32 time=18ms TTL=58
Reply from 197.242.144.102: bytes=32 time=22ms TTL=58
Reply from 197.242.144.102: bytes=32 time=20ms TTL=58
Reply from 197.242.144.102: bytes=32 time=22ms TTL=58
Reply from 197.242.144.102: bytes=32 time=19ms TTL=58
Reply from 197.242.144.102: bytes=32 time=18ms TTL=58
Reply from 197.242.144.102: bytes=32 time=18ms TTL=58


Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 61ms, Average = 22ms
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X