Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
@Afripeople

I have asked this before without a real answer. Please explain the traces below, this was done right after another and both on Afrihost. Why does it take 20ms longer to a server on your own network, than to another ISP's server? The reason why it matters is that 20ms between local sites are massive!



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

1 <1 ms <1 ms <1 ms 10.0.0.2
2 13 ms 13 ms 12 ms 105-236-0-1-esr-lo.mtnbusiness.co.za [105.236.0.1]
3 30 ms 31 ms 30 ms 41.181.201.94
4 37 ms 81 ms 36 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 30 ms 31 ms 31 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 62 ms 52 ms 52 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
7 54 ms 54 ms 54 ms jh-cr-2.za--jh-cr-1.za-a.mtnns.net [196.44.31.255]
8 54 ms 55 ms 57 ms 196.44.31.99
9 71 ms 60 ms 58 ms 196.30.1.39
10 54 ms 54 ms 55 ms 196.31.220.21
11 58 ms 65 ms 58 ms 196.31.63.202
12 54 ms 54 ms 57 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
13 53 ms 53 ms 55 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

C:\>tracert webafrica.co.za

Tracing route to webafrica.co.za [41.185.61.34]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms 10.0.0.2
2 18 ms 29 ms 16 ms 105-236-0-1-esr-lo.mtnbusiness.co.za [105.236.0.1]
3 35 ms 28 ms 23 ms 41.181.201.94
4 31 ms 29 ms 30 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 25 ms 32 ms 30 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 34 ms 31 ms 31 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 58 ms 53 ms 32 ms 196.44.0.74
8 38 ms 31 ms 31 ms 41-208-29-209.mtnns.net [41.208.29.209]
9 36 ms 32 ms 36 ms css2-ctn-gi0-1.ip.isnet.net [168.209.2.15]
10 41 ms 36 ms 39 ms mi-za-cpt-br1-gi0-3-108.ip.isnet.net [168.209.28.42]
11 32 ms 38 ms 32 ms 197.96.154.190
12 29 ms 34 ms 25 ms 197.96.154.191
13 29 ms 24 ms 25 ms wnls-whmcs-web01.wadns.net [41.185.61.34]

Trace complete.

Then a trace to a UK server is actually one hope less than to one of your own servers! (Also note the packet loss on the last hop!)

Tracing route to bbc.co.uk [212.58.246.104]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 10.0.0.2
2 17 ms 15 ms 29 ms 105-236-0-1-esr-lo.mtnbusiness.co.za [105.236.0.1]
3 74 ms 69 ms 60 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 59 ms 65 ms 75 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 72 ms 54 ms 54 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 213 ms 220 ms 196 ms ls-cr-2.uk--tb-cr-1.za.mtnns.net [196.44.31.113]
7 194 ms 212 ms 216 ms ls-pr-1.uk--ls-cr-2.uk-a.mtn.net [209.212.111.201]
8 207 ms 205 ms 204 ms bbc-linx.pr01.thdow.bbc.co.uk [195.66.224.103]
9 * * * Request timed out.
10 187 ms 218 ms 209 ms ae0.er02.cwwtf.bbc.co.uk [132.185.254.90]
11 215 ms 214 ms 184 ms 132.185.255.165
12 212 ms * 223 ms fmt-vip133.cwwtf.bbc.co.uk [212.58.246.104]

I know a healthy local RTT should be less than 40ms and a decent RTT for European servers should be about 200ms! Afrihosts network (although working) is not healthy!
 
hi Afripeople

I am having problems from last week...i have attached two trace routes 15 min apart.
please help

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.9.100
2 * * * Request timed out.
3 9 ms 9 ms 9 ms 41.181.178.53
4 10 ms 9 ms 9 ms 196.44.31.120
5 * * 56 ms 196.44.0.42
6 * * * Request timed out.
7 * * * Request timed out.
8 * 10 ms 11 ms 196.31.220.8
9 * 11 ms 11 ms 196.31.220.25
10 * 10 ms 9 ms 196.31.63.206
11 * * * Request timed out.
12 11 ms 10 ms 10 ms 197.242.144.102

Trace complete


>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.9.100
2 * * 7 ms 105.236.13.65
3 * 8 ms 9 ms 41.181.178.53
4 9 ms 10 ms 9 ms 196.44.31.120
5 10 ms 9 ms 9 ms 196.44.0.42
6 * 9 ms 8 ms 41.181.165.115
7 * * * Request timed out.
8 14 ms 10 ms 10 ms 196.31.220.8
9 11 ms 10 ms 10 ms 196.31.220.25
10 * * 10 ms 196.31.63.206
11 10 ms 10 ms 11 ms 196.30.42.133
12 10 ms 10 ms 10 ms 197.242.144.102

Trace complete.
 
Aquiva said:
@Afripeople

I have asked this before without a real answer. Please explain the traces below, this was done right after another and both on Afrihost. Why does it take 20ms longer to a server on your own network, than to another ISP's server? The reason why it matters is that 20ms between local sites are massive!



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

1 <1 ms <1 ms <1 ms 10.0.0.2
2 13 ms 13 ms 12 ms 105-236-0-1-esr-lo.mtnbusiness.co.za [105.236.0.1]
3 30 ms 31 ms 30 ms 41.181.201.94
4 37 ms 81 ms 36 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 30 ms 31 ms 31 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 62 ms 52 ms 52 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
7 54 ms 54 ms 54 ms jh-cr-2.za--jh-cr-1.za-a.mtnns.net [196.44.31.255]
8 54 ms 55 ms 57 ms 196.44.31.99
9 71 ms 60 ms 58 ms 196.30.1.39
10 54 ms 54 ms 55 ms 196.31.220.21
11 58 ms 65 ms 58 ms 196.31.63.202
12 54 ms 54 ms 57 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
13 53 ms 53 ms 55 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

C:\>tracert webafrica.co.za

Tracing route to webafrica.co.za [41.185.61.34]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms 10.0.0.2
2 18 ms 29 ms 16 ms 105-236-0-1-esr-lo.mtnbusiness.co.za [105.236.0.1]
3 35 ms 28 ms 23 ms 41.181.201.94
4 31 ms 29 ms 30 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 25 ms 32 ms 30 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 34 ms 31 ms 31 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 58 ms 53 ms 32 ms 196.44.0.74
8 38 ms 31 ms 31 ms 41-208-29-209.mtnns.net [41.208.29.209]
9 36 ms 32 ms 36 ms css2-ctn-gi0-1.ip.isnet.net [168.209.2.15]
10 41 ms 36 ms 39 ms mi-za-cpt-br1-gi0-3-108.ip.isnet.net [168.209.28.42]
11 32 ms 38 ms 32 ms 197.96.154.190
12 29 ms 34 ms 25 ms 197.96.154.191
13 29 ms 24 ms 25 ms wnls-whmcs-web01.wadns.net [41.185.61.34]

Trace complete.

Then a trace to a UK server is actually one hope less than to one of your own servers! (Also note the packet loss on the last hop!)

Tracing route to bbc.co.uk [212.58.246.104]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 10.0.0.2
2 17 ms 15 ms 29 ms 105-236-0-1-esr-lo.mtnbusiness.co.za [105.236.0.1]
3 74 ms 69 ms 60 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 59 ms 65 ms 75 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 72 ms 54 ms 54 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 213 ms 220 ms 196 ms ls-cr-2.uk--tb-cr-1.za.mtnns.net [196.44.31.113]
7 194 ms 212 ms 216 ms ls-pr-1.uk--ls-cr-2.uk-a.mtn.net [209.212.111.201]
8 207 ms 205 ms 204 ms bbc-linx.pr01.thdow.bbc.co.uk [195.66.224.103]
9 * * * Request timed out.
10 187 ms 218 ms 209 ms ae0.er02.cwwtf.bbc.co.uk [132.185.254.90]
11 215 ms 214 ms 184 ms 132.185.255.165
12 212 ms * 223 ms fmt-vip133.cwwtf.bbc.co.uk [212.58.246.104]

I know a healthy local RTT should be less than 40ms and a decent RTT for European servers should be about 200ms! Afrihosts network (although working) is not healthy!
Click to expand...

I see spikes on the second hop, so possibly it's your exchange.

Do a "ping -n 100 105.236.0.1" to see.
 
wingnut771 said:
I see spikes on the second hop, so possibly it's your exchange.

Do a "ping -n 100 105.236.0.1" to see.
Click to expand...

You asked for it ;-)

Pinging 105.236.0.1 with 32 bytes of data:
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=24ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=25ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=25ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=24ms TTL=254
Reply from 105.236.0.1: bytes=32 time=24ms TTL=254
Reply from 105.236.0.1: bytes=32 time=24ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=24ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=24ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=27ms TTL=254
Reply from 105.236.0.1: bytes=32 time=30ms TTL=254
Reply from 105.236.0.1: bytes=32 time=26ms TTL=254
Reply from 105.236.0.1: bytes=32 time=30ms TTL=254
Reply from 105.236.0.1: bytes=32 time=24ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=24ms TTL=254
Reply from 105.236.0.1: bytes=32 time=24ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=42ms TTL=254
Reply from 105.236.0.1: bytes=32 time=38ms TTL=254
Reply from 105.236.0.1: bytes=32 time=62ms TTL=254
Reply from 105.236.0.1: bytes=32 time=28ms TTL=254
Reply from 105.236.0.1: bytes=32 time=28ms TTL=254
Reply from 105.236.0.1: bytes=32 time=26ms TTL=254
Reply from 105.236.0.1: bytes=32 time=25ms TTL=254
Reply from 105.236.0.1: bytes=32 time=28ms TTL=254
Reply from 105.236.0.1: bytes=32 time=27ms TTL=254
Reply from 105.236.0.1: bytes=32 time=27ms TTL=254
Reply from 105.236.0.1: bytes=32 time=24ms TTL=254
Reply from 105.236.0.1: bytes=32 time=28ms TTL=254
Reply from 105.236.0.1: bytes=32 time=24ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=24ms TTL=254
Reply from 105.236.0.1: bytes=32 time=24ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=24ms TTL=254
Reply from 105.236.0.1: bytes=32 time=37ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=25ms TTL=254
Reply from 105.236.0.1: bytes=32 time=24ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=24ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=24ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=24ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254
Reply from 105.236.0.1: bytes=32 time=23ms TTL=254

Ping statistics for 105.236.0.1:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 62ms, Average = 24ms
 
Aquiva said:
You asked for it ;-)

Ping statistics for 105.236.0.1:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 62ms, Average = 24ms
Click to expand...

1 or 2 spikes but that's acceptable in my book :), here's mine:

Pinging 105.236.7.129 with 32 bytes of data:
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=16ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=18ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=16ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=18ms TTL=255
Reply from 105.236.7.129: bytes=32 time=18ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=18ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=16ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=16ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=18ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=18ms TTL=255
Reply from 105.236.7.129: bytes=32 time=23ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=18ms TTL=255
Reply from 105.236.7.129: bytes=32 time=18ms TTL=255
Reply from 105.236.7.129: bytes=32 time=19ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=18ms TTL=255
Reply from 105.236.7.129: bytes=32 time=18ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=18ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=18ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=16ms TTL=255
Reply from 105.236.7.129: bytes=32 time=18ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=18ms TTL=255
Reply from 105.236.7.129: bytes=32 time=18ms TTL=255
Reply from 105.236.7.129: bytes=32 time=16ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255
Reply from 105.236.7.129: bytes=32 time=17ms TTL=255

Ping statistics for 105.236.7.129:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 23ms, Average = 17ms
 
Mine is dead slow... I only really use it for Torrents, but JOH! Slow slow slow slow... and I have 4GB left.
Here is a joke for you today!
My OpenWeb uncapped account is faster than my Afrihost capped account...
 
gdiza said:
Mine is dead slow... I only really use it for Torrents, but JOH! Slow slow slow slow... and I have 4GB left.
Here is a joke for you today!
My OpenWeb uncapped account is faster than my Afrihost capped account...
Click to expand...

Your account sharer must still be on holiday :p
 
So my internet light just went red for a second then came back on again. All internet traffic obviously died. Same thing happened last night though around the same time.

I remember reading a while back someone else had this issue with Afrihost, where every night at around 12 the session would drop and then reconnect. What is going on?
 
Hmm I wonder if this disconnect isn't their new network management stuff putting me into a different resource pool.
 
caroper said:
I finally received my SIM for the PLUS+ data today, put it in the phone and all was well.
Later I tried to access the internet and it didn't work, I assumed it was a bad spot as MTN Coverage is not great arround here at the best of times.
Got home and tried again and still nothing. So I tried my tablet, also with an Afrihost SIM and all was well.
Looking at the Client zone I see it says the account status is CAPPED and the use data is:

3561010509706478 105.208.59.164 473.0 KB 2015-01-09 12:25:46 2015-01-09 12:33:04

My math may be rusty but as far as I am aware 473.0 KB is not greater than 500MB.
This PLUS+ is turning out to be a damn expensive farce
Click to expand...


I saw that you later posted that this was resolved. I am still interested as to why this took so long to get sorted out though, should have been a pretty straightforward query :(
 
cpbotha said:
A Telkom tech called Anthony called me this morning at 8:00 to ask me about the fault that was logged.

I explained the whole thing (line used to be rock solid at 7 Mbps / 1 Mbps but has now been put an the 7 Mbps / 632 Kbps profile, whilst I really need that little bit of extra upstream and I'm paying for 10 Mbps ADSL). He then claimed that *that* was my problem, my line really can't handle 10. When I said that my line had been operating rock solidly at 7 / 1 for a year and that I really had wanted to keep it at 7 / 1 and not 7 / .6 something, he then said that the line profiles weren't his domain, he dealt more with physical line faults. End of call.

Bottom-line: I'm crossing my fingers that Afrihost regain their access to the back end so that they can put my profile back on 10, and my modem can then do what it was designed to do, because Telkom prefers not to help.
Click to expand...

Let's hope so, we're getting many clients now being put on sync profiles they're not happy so we're also putting pressure to get this back up :(
 
balky said:
A Telkom techie once told me that you have to have an SNR of at least 10db. That's probably what they are taught. My SNR is currently 6 - 7 db and for the past 4 weeks everything has been streaming and downloading really well.
Click to expand...

I usually like to see at least 12dB for a healthy line, but we see some lines sitting on 6dB still running. It really depends on the actual values, because remember this is a ration between two values and not an absolute measurement.
 
Brennan123 said:
I normally buy 1gig (R5) at a time when my capped is finished, but today I realized that for each gig I buy i am paying R5 + R11.50 in debit order fees.
Click to expand...

That seems a little excessive. Some banks don't charge that much for debits or have higher plans, but maybe it's time to consider a higher package to save on the end cost :(
 
Aquiva said:
@Afripeople

I have asked this before without a real answer. Please explain the traces below, this was done right after another and both on Afrihost. Why does it take 20ms longer to a server on your own network, than to another ISP's server? The reason why it matters is that 20ms between local sites are massive!



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

1 <1 ms <1 ms <1 ms 10.0.0.2
2 13 ms 13 ms 12 ms 105-236-0-1-esr-lo.mtnbusiness.co.za [105.236.0.1]
3 30 ms 31 ms 30 ms 41.181.201.94
4 37 ms 81 ms 36 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 30 ms 31 ms 31 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 62 ms 52 ms 52 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
7 54 ms 54 ms 54 ms jh-cr-2.za--jh-cr-1.za-a.mtnns.net [196.44.31.255]
8 54 ms 55 ms 57 ms 196.44.31.99
9 71 ms 60 ms 58 ms 196.30.1.39
10 54 ms 54 ms 55 ms 196.31.220.21
11 58 ms 65 ms 58 ms 196.31.63.202
12 54 ms 54 ms 57 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
13 53 ms 53 ms 55 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

C:\>tracert webafrica.co.za

Tracing route to webafrica.co.za [41.185.61.34]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms 10.0.0.2
2 18 ms 29 ms 16 ms 105-236-0-1-esr-lo.mtnbusiness.co.za [105.236.0.1]
3 35 ms 28 ms 23 ms 41.181.201.94
4 31 ms 29 ms 30 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 25 ms 32 ms 30 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 34 ms 31 ms 31 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 58 ms 53 ms 32 ms 196.44.0.74
8 38 ms 31 ms 31 ms 41-208-29-209.mtnns.net [41.208.29.209]
9 36 ms 32 ms 36 ms css2-ctn-gi0-1.ip.isnet.net [168.209.2.15]
10 41 ms 36 ms 39 ms mi-za-cpt-br1-gi0-3-108.ip.isnet.net [168.209.28.42]
11 32 ms 38 ms 32 ms 197.96.154.190
12 29 ms 34 ms 25 ms 197.96.154.191
13 29 ms 24 ms 25 ms wnls-whmcs-web01.wadns.net [41.185.61.34]

Trace complete.

Then a trace to a UK server is actually one hope less than to one of your own servers! (Also note the packet loss on the last hop!)

Tracing route to bbc.co.uk [212.58.246.104]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 10.0.0.2
2 17 ms 15 ms 29 ms 105-236-0-1-esr-lo.mtnbusiness.co.za [105.236.0.1]
3 74 ms 69 ms 60 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 59 ms 65 ms 75 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 72 ms 54 ms 54 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 213 ms 220 ms 196 ms ls-cr-2.uk--tb-cr-1.za.mtnns.net [196.44.31.113]
7 194 ms 212 ms 216 ms ls-pr-1.uk--ls-cr-2.uk-a.mtn.net [209.212.111.201]
8 207 ms 205 ms 204 ms bbc-linx.pr01.thdow.bbc.co.uk [195.66.224.103]
9 * * * Request timed out.
10 187 ms 218 ms 209 ms ae0.er02.cwwtf.bbc.co.uk [132.185.254.90]
11 215 ms 214 ms 184 ms 132.185.255.165
12 212 ms * 223 ms fmt-vip133.cwwtf.bbc.co.uk [212.58.246.104]

I know a healthy local RTT should be less than 40ms and a decent RTT for European servers should be about 200ms! Afrihosts network (although working) is not healthy!
Click to expand...

Th results are inconsistent right from the 2nd hop, so I would suspect this is starting at the exchange or on your line :(
 
analytical said:
hi Afripeople

I am having problems from last week...i have attached two trace routes 15 min apart.
please help

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.9.100
2 * * * Request timed out.
3 9 ms 9 ms 9 ms 41.181.178.53
4 10 ms 9 ms 9 ms 196.44.31.120
5 * * 56 ms 196.44.0.42
6 * * * Request timed out.
7 * * * Request timed out.
8 * 10 ms 11 ms 196.31.220.8
9 * 11 ms 11 ms 196.31.220.25
10 * 10 ms 9 ms 196.31.63.206
11 * * * Request timed out.
12 11 ms 10 ms 10 ms 197.242.144.102

Trace complete


>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.9.100
2 * * 7 ms 105.236.13.65
3 * 8 ms 9 ms 41.181.178.53
4 9 ms 10 ms 9 ms 196.44.31.120
5 10 ms 9 ms 9 ms 196.44.0.42
6 * 9 ms 8 ms 41.181.165.115
7 * * * Request timed out.
8 14 ms 10 ms 10 ms 196.31.220.8
9 11 ms 10 ms 10 ms 196.31.220.25
10 * * 10 ms 196.31.63.206
11 10 ms 10 ms 11 ms 196.30.42.133
12 10 ms 10 ms 10 ms 197.242.144.102

Trace complete.
Click to expand...

These timeouts appear all over the place, although your latency when it goes through seems normal. I would suspect that this is an intermittent line fault. Have you reported this to Telkom or to us to log with Telkom?
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X