Afrihost Capped ADSL Feedback (MTN) - New beginning

Status
Not open for further replies.
AfriMan said:
It shouldn't be the account, because I'm assuming you're an Unshaped capped client. So we don't really mind how much traffic you push and the line limit is determined by your line with Telkom.

If your line has an intermittent sync problem, you could be reaching that sync limit and seeing some packet loss or degradation on the account. So if you have say, a 10Mbps line, but your sync degrades to 5 or 6 Mbps, when you start getting close to that sort of throughput you might see performance degrade and the line might start becoming intermittent. A restart (resync) puts the line back to a better state and then it performs better until you hit traffic close to the actual sync rate again.

That's a theory though, we can run some tests together and see if this is the actual problem :(
Click to expand...

Yah its very weird hence i'm trying to pin point the issue. btw the line sync speed remains constant at 2Mbps
 
For those of you having trouble with Google services and Chrome:

open a new tab and go to chrome://flags/
Find "Experimental QUIC protocol."
Set it to "Disabled" instead of "Default"

Boom, Google services working again. This was driving me nuts the past few days, and appears to be related to Google switching this protocol on for their services and having it enabled by default in Chrome. Not sure what the benefit is supposed to be, but clearly something's buggy with it right now and disabling it has no negative effects.
 
Seeyou said:
For those of you having trouble with Google services and Chrome:

open a new tab and go to chrome://flags/
Find "Experimental QUIC protocol."
Set it to "Disabled" instead of "Default"

Boom, Google services working again. This was driving me nuts the past few days, and appears to be related to Google switching this protocol on for their services and having it enabled by default in Chrome. Not sure what the benefit is supposed to be, but clearly something's buggy with it right now and disabling it has no negative effects.
Click to expand...

QUIC have been in Chrome since 2013. Just sayin.

This is more a case of the Afrihost QoS/Shaper/Throttler potentially dropping/blocking it. And if it was busy in the Chrome client, it would be buggy on all ISPs.
 
Seeyou said:
For those of you having trouble with Google services and Chrome:

open a new tab and go to chrome://flags/
Find "Experimental QUIC protocol."
Set it to "Disabled" instead of "Default"

Boom, Google services working again. This was driving me nuts the past few days, and appears to be related to Google switching this protocol on for their services and having it enabled by default in Chrome. Not sure what the benefit is supposed to be, but clearly something's buggy with it right now and disabling it has no negative effects.
Click to expand...

Thanks for posting this, seen a few users here report this and hardware acceleration fixes a few things :)
 
Ping Test:

ping 197.242.144.102

Request timeout for icmp_seq 1
64 bytes from 197.242.144.102: icmp_req=2 ttl=57 time=30 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=57 time=18 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=57 time=20 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=57 time=20 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=53 time=32 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=53 time=31 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=53 time=39 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=53 time=43 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=53 time=28 ms


Trace Test:

traceroute -n 197.242.144.102

1 10.0.0.2 47.267 ms 2.023 ms 1.574 ms
2 Request timed out * * *
3 41.181.178.18 52.179 ms 57.098 ms 96.889 ms
4 41.181.178.17 18.699 ms 26.824 ms 21.593 ms
5 41.181.165.115 19.35 ms 17.516 ms 76.648 ms
6 196.31.180.4 18.343 ms 20.927 ms
41.181.165.114 22.709 ms
7 196.44.0.224 21.127 ms 32.942 ms 20.635 ms
8 196.44.31.99 26.565 ms 23.103 ms 20.244 ms
9 196.30.1.53 24.281 ms 21.66 ms
196.31.220.8 19.345 ms
10 196.31.220.27 21.975 ms 21.069 ms
196.31.220.23 21.597 ms
11 196.31.63.202 22.758 ms 22.873 ms 24.4 ms
12 196.30.42.133 20.532 ms 20.317 ms 20.659 ms
13 197.242.144.102 18.625 ms 18.537 ms 18.282 ms


traceroute -n 8.8.8.8

1 10.0.0.2 * * 5.701 ms
2 Request timed out * * *
3 41.181.221.245 127.796 ms 172.256 ms 136.775 ms
4 41.181.221.246 20.785 ms 17.6 ms 18.814 ms
5 41.181.165.115 17.565 ms 17.3 ms 16.687 ms
6 41.181.165.114 20.325 ms 20.024 ms 15.314 ms
7 41.181.180.10 44.947 ms
196.44.0.224 40.169 ms 34.782 ms
8 196.44.31.94 18.882 ms 19.858 ms
196.44.0.43 18.528 ms
9 41.181.139.99 20.894 ms
41.181.139.109 39.42 ms 38.136 ms
10 72.14.194.74 33.921 ms 41.384 ms 29.803 ms
11 72.14.239.33 21.918 ms
72.14.239.117 19.985 ms
72.14.239.53 17.309 ms
12 8.8.8.8 25.835 ms 20.108 ms 37.457 ms


DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 197.242.144.102


nslookup www.google.com

Name: www.google.com
Address: 216.58.223.36


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN

still getting high pings on the 3rd hop. Can any qualified person at Afrihost please explain why this is??? been like this for weeks now! Definitely not the exchange as Telkom checked my exchange on Tuesday this week.
 
same test with Web Africa account
Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=54 time=23 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=54 time=25 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=54 time=24 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=54 time=24 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=54 time=22 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=54 time=16 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=54 time=18 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=54 time=19 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=54 time=16 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=54 time=20 ms


Trace Test:

traceroute -n 197.242.144.102

1 10.0.0.2 * * 1.537 ms
2 Request timed out * * *
3 196.38.73.214 17.83 ms 20.252 ms 22.292 ms
4 196.38.73.213 16.948 ms 17.156 ms 17.774 ms
5 196.38.73.9 20.11 ms 19.73 ms 19.856 ms
6 196.26.0.63 24.178 ms 21.903 ms 23.922 ms
7 168.209.1.179 17.266 ms 17.189 ms 18.857 ms
8 41.208.29.126 21.338 ms 21.495 ms 22.531 ms
9 196.44.0.223 23.452 ms 24.043 ms 25.279 ms
10 196.44.31.99 23.165 ms 24.787 ms 23.505 ms
11 196.31.220.8 22.77 ms
196.31.220.6 28.428 ms
196.30.1.39 27.038 ms
12 196.31.220.27 21.84 ms 20.03 ms 28.426 ms
13 196.31.63.202 210.714 ms 23.507 ms
196.31.63.206 20.464 ms
14 196.30.42.133 22.579 ms 25.388 ms 24.073 ms
15 197.242.144.102 23.308 ms 22.623 ms 34.353 ms


traceroute -n 8.8.8.8

1 10.0.0.2 * * *
2 Request timed out * * *
3 196.38.73.134 20.793 ms 22.038 ms 20.776 ms
4 196.38.73.133 16.616 ms 23.761 ms 15.611 ms
5 196.38.73.17 17.733 ms 17.475 ms 18.005 ms
6 196.26.0.62 19.624 ms 18.048 ms 24.591 ms
7 168.209.1.179 15.199 ms 15.258 ms 15.696 ms
8 72.14.205.16 19.846 ms 15.682 ms 15.446 ms
9 72.14.239.35 17.338 ms 18.391 ms
72.14.239.53 19.294 ms
10 8.8.8.8 15.634 ms 16.471 ms 17.149 ms


DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 197.242.144.102


nslookup www.google.com

Name: www.google.com
Address: 216.58.223.4


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN
 
I'm getting the exact same on both my Afrihost and WebAfrica Accounts.
The JHB ping is continuously over 200.
 
I'm still not understanding the high latency on the 3rd hop. its been like this for weeks. like i asked can someone from Afrihost tell me what this is?
Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=57 time=19 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=57 time=22 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=57 time=22 ms
Request timeout for icmp_seq 4
64 bytes from 197.242.144.102: icmp_req=5 ttl=57 time=22 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=53 time=19 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=53 time=31 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=53 time=34 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=53 time=27 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=53 time=30 ms


Trace Test:

traceroute -n 197.242.144.102

1 10.0.0.2 * * 1.56 ms
2 Request timed out * * *
3 41.181.221.249 41.366 ms 125.03 ms 112.682 ms
4 41.181.221.250 20.111 ms 22.093 ms 79.826 ms
5 41.181.165.115 17.643 ms 16.855 ms 17.192 ms
6 41.181.165.114 19.754 ms 20.066 ms
196.31.180.4 21.226 ms
7 196.44.0.224 21.55 ms 22.32 ms 21.773 ms
8 196.44.31.99 19.397 ms 20.312 ms 18.567 ms
9 196.31.220.6 64.685 ms 19.862 ms
196.31.220.8 21.64 ms
10 196.31.220.27 21.201 ms
196.31.220.23 18.439 ms 18.706 ms
11 196.31.63.206 20.783 ms 21.346 ms 21.454 ms
12 196.30.42.133 21.642 ms 21.6 ms 21.273 ms
13 197.242.144.102 22.969 ms 20.3 ms 21.486 ms


traceroute -n 8.8.8.8

1 10.0.0.2 2.714 ms * *
2 Request timed out * * *
3 41.181.221.245 127.115 ms 133.305 ms 100.641 ms
4 41.181.221.246 17.755 ms 21.861 ms 17.571 ms
5 41.181.165.115 38.314 ms 16.639 ms 15.578 ms
6 41.181.165.114 16.95 ms 19.689 ms 17.982 ms
7 196.44.0.224 26.344 ms 24.613 ms
41.181.180.10 45.938 ms
8 196.44.31.170 16.589 ms
196.44.31.94 19.237 ms
196.44.0.43 17.484 ms
9 41.181.139.99 18.627 ms 26.445 ms 23.275 ms
10 72.14.194.74 19.153 ms 23.591 ms 20.433 ms
11 72.14.239.117 15.812 ms 20.01 ms
72.14.239.33 19.061 ms
12 8.8.8.8 38.245 ms 27.996 ms 29.702 ms


DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 197.242.144.102


nslookup www.google.com

Name: www.google.com
Address: 216.58.223.36


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN
 
Still having major issues with Afrihost. I tested my connection with a crystalweb account and it's working 110%.
 
Davedes said:
I'm still not understanding the high latency on the 3rd hop. its been like this for weeks. like i asked can someone from Afrihost tell me what this is?
Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=57 time=19 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=57 time=22 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=57 time=22 ms
Request timeout for icmp_seq 4
64 bytes from 197.242.144.102: icmp_req=5 ttl=57 time=22 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=53 time=19 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=53 time=31 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=53 time=34 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=53 time=27 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=53 time=30 ms


Trace Test:

traceroute -n 197.242.144.102

1 10.0.0.2 * * 1.56 ms
2 Request timed out * * *
3 41.181.221.249 41.366 ms 125.03 ms 112.682 ms
4 41.181.221.250 20.111 ms 22.093 ms 79.826 ms
5 41.181.165.115 17.643 ms 16.855 ms 17.192 ms
6 41.181.165.114 19.754 ms 20.066 ms
196.31.180.4 21.226 ms
7 196.44.0.224 21.55 ms 22.32 ms 21.773 ms
8 196.44.31.99 19.397 ms 20.312 ms 18.567 ms
9 196.31.220.6 64.685 ms 19.862 ms
196.31.220.8 21.64 ms
10 196.31.220.27 21.201 ms
196.31.220.23 18.439 ms 18.706 ms
11 196.31.63.206 20.783 ms 21.346 ms 21.454 ms
12 196.30.42.133 21.642 ms 21.6 ms 21.273 ms
13 197.242.144.102 22.969 ms 20.3 ms 21.486 ms


traceroute -n 8.8.8.8

1 10.0.0.2 2.714 ms * *
2 Request timed out * * *
3 41.181.221.245 127.115 ms 133.305 ms 100.641 ms
4 41.181.221.246 17.755 ms 21.861 ms 17.571 ms
5 41.181.165.115 38.314 ms 16.639 ms 15.578 ms
6 41.181.165.114 16.95 ms 19.689 ms 17.982 ms
7 196.44.0.224 26.344 ms 24.613 ms
41.181.180.10 45.938 ms
8 196.44.31.170 16.589 ms
196.44.31.94 19.237 ms
196.44.0.43 17.484 ms
9 41.181.139.99 18.627 ms 26.445 ms 23.275 ms
10 72.14.194.74 19.153 ms 23.591 ms 20.433 ms
11 72.14.239.117 15.812 ms 20.01 ms
72.14.239.33 19.061 ms
12 8.8.8.8 38.245 ms 27.996 ms 29.702 ms


DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 197.242.144.102


nslookup www.google.com

Name: www.google.com
Address: 216.58.223.36


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN
Click to expand...

Recently Telkom upgraded quite a few Exchanges with different equipment, these Exchanges no longer respond to ICMP requests, so that will not appear on Traceroutes nor will you be able to Ping the Exchange. I'm still not entirely sure why this is the case, the little I've been able to find out is that this change was implemented for security reasons.

This does mean that if there is latency on the Exchange - either from damage or congestion - those results will bleed over to the third hop instead of appearing on the second hop.
 
Cake_Pax said:
Still having major issues with Afrihost. I tested my connection with a crystalweb account and it's working 110%.
Click to expand...

Hi!

What sort of issues are you experiencing with your Afrihost account?
 
nakedpeanut said:
I'm getting the exact same on both my Afrihost and WebAfrica Accounts.
The JHB ping is continuously over 200.
Click to expand...

Evening!

Where are you seeing the ping of 200? On a Speedtest or a traceroute? Or is it with a specific service that is currently affected?
 
Im so fcking over my iOS downloads being shaped on a capped account! 30KB/s again tonight...
 
AfriGenie said:
Recently Telkom upgraded quite a few Exchanges with different equipment, these Exchanges no longer respond to ICMP requests, so that will not appear on Traceroutes nor will you be able to Ping the Exchange. I'm still not entirely sure why this is the case, the little I've been able to find out is that this change was implemented for security reasons.

This does mean that if there is latency on the Exchange - either from damage or congestion - those results will bleed over to the third hop instead of appearing on the second hop.
Click to expand...

So if it is an exchange issue, why is that same latency spike not present on the WebAfrica trace posted?
 
nicki said:
So if it is an exchange issue, why is that same latency spike not present on the WebAfrica trace posted?
Click to expand...

Guaranteed not to get a response from them on your question. It's everyone else's fault but their crap crumbling MTN network.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X