Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
I personally haven't seen an influx of DNS issues.
If you switch to Googles DNS do you guys still see the same issues?

Unlike "caroper" I was pointed to Google's DNS. Also can you please explain why there are so many hops when tracing to afrihost.com? It is litterally double that when I am on WebAfrica and tracing to their servers. Could this not be why any realtime international traffic experiences packet loss (streaming, gaming etc.)??
 
I am currently set on Get From ISP but have these taht I can switch too, not sure where they are from:
Primary DNS 208.67.222.222
Secondary DNS 208.67.220.220

I will switch if I get the errors again.

These are OpenDNS' servers, can you try assigning the following to see if you still have issues:

196.7.7.7
196.7.8.9
 
Unlike "caroper" I was pointed to Google's DNS. Also can you please explain why there are so many hops when tracing to afrihost.com? It is litterally double that when I am on WebAfrica and tracing to their servers. Could this not be why any realtime international traffic experiences packet loss (streaming, gaming etc.)??

Do you have an example traceroute to post?
Tracing to our site, everything looks normal here

Code:
traceroute to afrihost.com (197.242.144.102), 64 hops max, 52 byte packets
 1  router.asus.com (192.168.1.1)  1.077 ms  1.839 ms  0.965 ms
 2  105-236-12-65-esr-lo.mtnbusiness.co.za (105.236.12.65)  17.504 ms  17.548 ms  16.759 ms
 3  ipc-recieve-tb-2a.mtnbusiness.net (41.181.54.86)  18.075 ms  19.723 ms  17.664 ms
 4  tb-dca-2.za--qux-c.za.mtnbusiness.net (41.181.198.188)  17.275 ms  20.336 ms  18.666 ms
 5  unc-cpt-1.mtnns.net (196.44.18.8)  19.177 ms
    compj-cpt-1.mtnns.net (196.44.18.2)  20.010 ms  18.611 ms
 6  jh-cr-1.za--tb-cr-2.za.mtnns.net (196.44.31.66)  42.494 ms
    ct-cr-2.za--tb-cr-1.za.mtnns.net (196.44.31.134)  20.529 ms  19.585 ms
 7  jh-cr-2.za--jh-cr-1.za-a.mtnns.net (196.44.31.255)  43.106 ms  43.784 ms  42.366 ms
 8  196.44.31.99 (196.44.31.99)  42.737 ms  42.504 ms
    jh-dca-2.za--jh-cr-1.za-a.mtnns.net (196.44.0.221)  40.421 ms
 9  196.30.1.53 (196.30.1.53)  42.605 ms
    196.30.1.39 (196.30.1.39)  57.732 ms  41.799 ms
10  196.31.220.21 (196.31.220.21)  41.851 ms  43.447 ms  42.554 ms
11  196.31.63.206 (196.31.63.206)  41.206 ms  43.028 ms  41.845 ms
12  vl9-ah-ha-2.za.mtnbusiness.net (196.30.42.133)  51.066 ms  43.103 ms  42.961 ms
13  cms-gm.afrihost.com (197.242.144.102)  41.925 ms !Z  42.387 ms !Z  41.778 ms !Z
 
Mine looks better than yours excluding the timeout (Which I have always had) on the first hop.

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

1 3 ms <1 ms <1 ms www.routerlogin.com [192.168.0.200]
2 * * * Request timed out.
3 10 ms 8 ms 9 ms 41.181.201.93
4 9 ms 8 ms 9 ms 41.181.201.94
5 9 ms 8 ms 8 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
6 9 ms 9 ms 8 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 33 ms 37 ms 33 ms pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66]

8 33 ms 33 ms 33 ms jh-cr-2.za--jh-cr-1.za-a.mtnns.net [196.44.31.255]
9 32 ms 32 ms 31 ms 196.44.31.99
10 32 ms 31 ms 32 ms 196.31.220.6
11 31 ms 31 ms 31 ms 196.31.220.23
12 32 ms 32 ms 32 ms 196.31.63.206
13 39 ms 31 ms 32 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
14 33 ms 33 ms 32 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.
 
Hey Afriman, still no eta from Telkom. Here the numbers again:

Afrihost ticket: EKA-585-90922
Telkom fault: 34BRK050115

Could you escalate the escalation tmrw morning if possible.

Currently connected(ish) but my 4meg line looks like this:

Upstream 512 kbps
Downstream 864 kbps
SNR Margin (Upstream) 9.0 db
SNR Margin (Downstream) 9.0 db
Line Attenuation (Upstream) 31.5 db
Line Attenuation (Downstream) 54.0 db

Which is actually by far and away the most stable I've gotten over the past 2 days, clearly my fault with packet loss(for the last 2 years) whenever it rains has escalated:/ argh bloody telskum...
 
Do you have an example traceroute to post?
Tracing to our site, everything looks normal here

Code:
traceroute to afrihost.com (197.242.144.102), 64 hops max, 52 byte packets
 1  router.asus.com (192.168.1.1)  1.077 ms  1.839 ms  0.965 ms
 2  105-236-12-65-esr-lo.mtnbusiness.co.za (105.236.12.65)  17.504 ms  17.548 ms  16.759 ms
 3  ipc-recieve-tb-2a.mtnbusiness.net (41.181.54.86)  18.075 ms  19.723 ms  17.664 ms
 4  tb-dca-2.za--qux-c.za.mtnbusiness.net (41.181.198.188)  17.275 ms  20.336 ms  18.666 ms
 5  unc-cpt-1.mtnns.net (196.44.18.8)  19.177 ms
    compj-cpt-1.mtnns.net (196.44.18.2)  20.010 ms  18.611 ms
 6  jh-cr-1.za--tb-cr-2.za.mtnns.net (196.44.31.66)  42.494 ms
    ct-cr-2.za--tb-cr-1.za.mtnns.net (196.44.31.134)  20.529 ms  19.585 ms
 7  jh-cr-2.za--jh-cr-1.za-a.mtnns.net (196.44.31.255)  43.106 ms  43.784 ms  42.366 ms
 8  196.44.31.99 (196.44.31.99)  42.737 ms  42.504 ms
    jh-dca-2.za--jh-cr-1.za-a.mtnns.net (196.44.0.221)  40.421 ms
 9  196.30.1.53 (196.30.1.53)  42.605 ms
    196.30.1.39 (196.30.1.39)  57.732 ms  41.799 ms
10  196.31.220.21 (196.31.220.21)  41.851 ms  43.447 ms  42.554 ms
11  196.31.63.206 (196.31.63.206)  41.206 ms  43.028 ms  41.845 ms
12  vl9-ah-ha-2.za.mtnbusiness.net (196.30.42.133)  51.066 ms  43.103 ms  42.961 ms
13  cms-gm.afrihost.com (197.242.144.102)  41.925 ms !Z  42.387 ms !Z  41.778 ms !Z

I meant looking at the amount of hops for a local server Afrihost vs WebAfrica: (Also notice the final RTT between the last hops - 15ms difference for local traffic!!

C:\>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 10.0.0.2
2 13 ms 13 ms 13 ms 196-210-128-1.dynamic.isadsl.co.za [196.210.128.1]
3 30 ms 30 ms 30 ms vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
4 24 ms 24 ms 24 ms 196.35.115.136
5 24 ms 24 ms 24 ms 168.209.6.13
6 25 ms 24 ms 24 ms 168.209.2.130
7 31 ms 32 ms 30 ms 41-208-29-210.mtnns.net [41.208.29.210]
8 24 ms 45 ms 24 ms 196.44.0.75
9 53 ms 55 ms 53 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]
10 50 ms 43 ms 43 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.221]
11 53 ms 58 ms 53 ms 196.30.1.39
12 52 ms 53 ms 52 ms 196.31.220.21
13 50 ms 50 ms 50 ms 196.31.63.202
14 53 ms 54 ms 53 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
15 45 ms 45 ms 46 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

C:\>tracert webafrica.com

Tracing route to webafrica.com [196.220.58.66]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 13 ms 12 ms 13 ms 196-210-128-1.dynamic.isadsl.co.za [196.210.128.1]
3 31 ms 31 ms 30 ms vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
4 24 ms 24 ms 24 ms 196.35.115.136
5 31 ms 31 ms 30 ms 196.26.78.33
6 24 ms 24 ms 24 ms wa-is.isdsl.net [196.38.72.84]
7 24 ms 24 ms 24 ms wnls-hr1-vl-140.wa.co.za [41.185.1.2]
8 30 ms 37 ms 31 ms 196.220.58.66

Trace complete.
 
Hey Afriman, still no eta from Telkom. Here the numbers again:

Afrihost ticket: EKA-585-90922
Telkom fault: 34BRK050115

Could you escalate the escalation tmrw morning if possible.

Currently connected(ish) but my 4meg line looks like this:

Upstream 512 kbps
Downstream 864 kbps
SNR Margin (Upstream) 9.0 db
SNR Margin (Downstream) 9.0 db
Line Attenuation (Upstream) 31.5 db
Line Attenuation (Downstream) 54.0 db

Which is actually by far and away the most stable I've gotten over the past 2 days, clearly my fault with packet loss(for the last 2 years) whenever it rains has escalated:/ argh bloody telskum...

I've shot a mail through to Telkom requesting an escalation :)
 
I meant looking at the amount of hops for a local server Afrihost vs WebAfrica: (Also notice the final RTT between the last hops - 15ms difference for local traffic!!

C:\>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 10.0.0.2
2 13 ms 13 ms 13 ms 196-210-128-1.dynamic.isadsl.co.za [196.210.128.1]
3 30 ms 30 ms 30 ms vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
4 24 ms 24 ms 24 ms 196.35.115.136
5 24 ms 24 ms 24 ms 168.209.6.13
6 25 ms 24 ms 24 ms 168.209.2.130
7 31 ms 32 ms 30 ms 41-208-29-210.mtnns.net [41.208.29.210]
8 24 ms 45 ms 24 ms 196.44.0.75
9 53 ms 55 ms 53 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]
10 50 ms 43 ms 43 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.221]
11 53 ms 58 ms 53 ms 196.30.1.39
12 52 ms 53 ms 52 ms 196.31.220.21
13 50 ms 50 ms 50 ms 196.31.63.202
14 53 ms 54 ms 53 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
15 45 ms 45 ms 46 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

C:\>tracert webafrica.com

Tracing route to webafrica.com [196.220.58.66]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 13 ms 12 ms 13 ms 196-210-128-1.dynamic.isadsl.co.za [196.210.128.1]
3 31 ms 31 ms 30 ms vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
4 24 ms 24 ms 24 ms 196.35.115.136
5 31 ms 31 ms 30 ms 196.26.78.33
6 24 ms 24 ms 24 ms wa-is.isdsl.net [196.38.72.84]
7 24 ms 24 ms 24 ms wnls-hr1-vl-140.wa.co.za [41.185.1.2]
8 30 ms 37 ms 31 ms 196.220.58.66

Trace complete.

It could be the way the different IPC networks are setup, the differences won't make a massive amount of difference though.
Setups vary around edge, core routers, switches etc etc. You're probably routing through stacks more switches around the network, but they won't show on a traceroute.
 
Hey Afriman, still no eta from Telkom. Here the numbers again:

Afrihost ticket: EKA-585-90922
Telkom fault: 34BRK050115

Could you escalate the escalation tmrw morning if possible.

Currently connected(ish) but my 4meg line looks like this:

Upstream 512 kbps
Downstream 864 kbps
SNR Margin (Upstream) 9.0 db
SNR Margin (Downstream) 9.0 db
Line Attenuation (Upstream) 31.5 db
Line Attenuation (Downstream) 54.0 db

Which is actually by far and away the most stable I've gotten over the past 2 days, clearly my fault with packet loss(for the last 2 years) whenever it rains has escalated:/ argh bloody telskum...

That is a telkom issue, your line is syncing at less than 1mb, you have really bad SNR for your attentuation as well.
Hope you have a line fault open, good luck.
 
That's weird, around 11pm demand was dropping off pretty fast so speeds should have been perfect. Latency looks normal, but we'll need to troubleshoot further - our own tests in Cape last night were looking pretty good :(

I shutdowned my pc at 10:57pm

Coincidence?
 
Hi Afriman, I see that the double adsl data continues for a while regardless of the Afrihost Plus. If this is the case then I should be getting an extra 50GB on my account considering that I am on Afrihost Plus. Why is this allocation not showing when I log into the client zone?
 
Hi Afriman, I see that the double adsl data continues for a while regardless of the Afrihost Plus. If this is the case then I should be getting an extra 50GB on my account considering that I am on Afrihost Plus. Why is this allocation not showing when I log into the client zone?

It won't count as triple data I'm afraid.
 
Why do I not get a reply on hop 2 and a increase in Ping time

Hey Afriman

Why do I not get a reply on hop 2?
tracert_ah.jpg

Also my ping used to be +-16mS but has increased to ave 25mS a bit better this am.

SAIX Speedtest
Last Result:
Download Speed: 8774 kbps (1096.8 KB/sec transfer rate)
Upload Speed: 862 kbps (107.8 KB/sec transfer rate)
Latency: 22 ms
2015/01/07, 10:23:36 AM

10Meg line
 
Ok, so then Afrihost Plus really adds no real value at the moment considering that the double data was the main benefit?

There are stacks more benefits on Plus+ though, double data is just one of them.
There's double data for Mobile, Simfy streaming, 500MB free Mobile data, 2 for 1 topups, double turbocharges for Uncapped and softcapping for Capped DSL.
 
Hey Afriman

Why do I not get a reply on hop 2?
View attachment 180664

Also my ping used to be +-16mS but has increased to ave 25mS a bit better this am.

SAIX Speedtest
Last Result:
Download Speed: 8774 kbps (1096.8 KB/sec transfer rate)
Upload Speed: 862 kbps (107.8 KB/sec transfer rate)
Latency: 22 ms
2015/01/07, 10:23:36 AM

10Meg line

The timeouts on the exchange mean that it isn't accepting ICMP, shouldn't be anything to worry about.
22ms for local latency is quite respectable :)
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X