Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
Do you use Wi-Fi to connect to your home network?
If it is a cable connection there could be a fault with your network cable or router.

Latency on your home network should be <1 ms. :)

Hop 1 is usually <1ms.

That test for some reason showed 3. Using cable. All devices in the house give similar results.

Normal Speedtest.net runs give me 40-60ms which is way higher then my usual 9-19ms.
 
Can you post your routers' SNR and Attenuation levels? It could reveal more information in finding the problem. :)

30ms-40ms above normal latency doesn't seem like much, but add that on top of international latency and it becomes very noticeable.
Normally I wouldn't bother with something like this, but considering it has been 100% for months, and only started acting up now, makes me believe that there's an actual problem somewhere.

Current Downstream Sync: 10240kbps
SNR: 14.8
Attenuation: 16.3

Current Upstream Sync: 947kbps
SNR: 16.5
Attenuation: 35.6

Things I have tried:

  • Different modem
  • Different ISP (Plugg)
  • Different filter
  • Port reset by Afrihost
  • Tried Google DNS (8.8.8.8; 8.8.4.4)


Last tracert before this post:
Code:
Tracing route to afrihost.co.za [41.86.112.68]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    36 ms    34 ms    39 ms  jhb-up3.ip.adsl.co.za [169.1.5.29]
  5    37 ms    35 ms    37 ms  jhb-in1.ip.adsl.co.za [169.1.5.42]
  6    35 ms    35 ms    36 ms  jhb-net1.ip.adsl.co.za [169.1.5.52]
  7    37 ms    41 ms    43 ms  mweb.jb1.napafrica.net [196.46.25.145]
  8    36 ms    37 ms    36 ms  201.bu-ether5.vic-pe-2.optinet.net [197.80.7.71]
  9    42 ms    38 ms    37 ms  197-81-226-81.jhb.mweb.co.za [197.81.226.81]
 10    40 ms    36 ms    36 ms  197-81-226-61.jhb.mweb.co.za [197.81.226.61]
 11    38 ms    48 ms    37 ms  197-81-229-4.jhb.mweb.co.za [197.81.229.4]
 12    36 ms    38 ms    45 ms  197-81-229-11.jhb.mweb.co.za [197.81.229.11]
 13    44 ms    47 ms    35 ms  41-86-112-68.mweb.co.za [41.86.112.68]

Trace complete.

Last Speedtest before this post:
5381287226.png
Ping: 48. | Download 9.73Mpbs | Upload 0.83Mps
 
Last edited:
From the symptoms and information you posted it would appear as if your line is managed by Telkom's new ASSIA software. It stabilizes your up and download speeds but with a cost of increased latency. :)

http://mybroadband.co.za/news/adsl/122012-adsl-problems-caused-by-new-telkom-system-isps.html



And I'm guessing there's no way around it.

Weird thing though, my stats have been give or take the same since I moved in. So if it's the ASSIA, it didn't noticeably improve my SNR's.
 


And I'm guessing there's no way around it.

Weird thing though, my stats have been give or take the same since I moved in. So if it's the ASSIA, it didn't noticeably improve my SNR's.
There is but you'll have to ask Telkom that your connection is not set to interleaved. :)
 


And I'm guessing there's no way around it.

Weird thing though, my stats have been give or take the same since I moved in. So if it's the ASSIA, it didn't noticeably improve my SNR's.
You can ask Telkom to change you back to fast, BUT if Assia sees that you line is still unstable, it will just switch it back until such a time its stable.

I dont think Assia is bad unless you are a gamer unfortunately. If your line is wobbly, then it probably would be better to let the system take over to give you something of of a better experience.
 
There is but you'll have to ask Telkom that your connection is not set to interleaved. :)
It could just be that he has a faulty cable, but if not then its just ASSIA trying to keep his line stable. Sometimes to have that is not great, because the change in line stats you will really come to hate. In time things might certainly improve, unless you pack up and move. I know that is a little extreme, but you might just get fibre, and realise your dream. Word :D
 
It could just be that he has a faulty cable, but if not then its just ASSIA trying to keep his line stable. Sometimes to have that is not great, because the change in line stats you will really come to hate. In time things might certainly improve, unless you pack up and move. I know that is a little extreme, but you might just get fibre, and realise your dream. Word :D
I'm glad I don't have to troubleshoot internet problems. There are so many things that could influence your internet experience. :)
 
I'm glad I don't have to troubleshoot internet problems. There are so many things that could influence your internet experience. :)
Lara's line is stable, and there are no issues. Its a good thing though, or else there will be plenty of tissues. Lara has never complained before, how amazing you know, we wish we had a great line like that, but ours are very slow. Word :D
 
Just thinking out loud here.
If upgrading a line from 4 to 10 MB it takes up to 10 days because a techie have to go physically move it to a faster port at the exchange, fair enough.
Later the 10 MB line gets downgraded to 8 MB, this move takes around 24 hours, so obviously done with software, line is still physically on the faster port.
Move forward a few weeks, line upgrade from 8 back to 10 MB takes longer than 48 hours, question is why, surely this should also just be a mouse click since the line is still on the faster physical port?

The 10 day thing was more due to a backlog of orders than anything else. Telkom have been doing software line upgrades for years now, and techs have not been really required for a long time. In most cases lines are being regraded quickly again, but we're still seeing some take longer - hopefully this will be resolved once Telkom catch up on their backlog :(
 
No matter whether you use afrihost or afrigreen there are FOREVER time-outs directly after this IP. Why?

IP Lookup Location For IP Address: 169.0.44.1
Continent: Africa (AF)
Country: South Africa IP Location Find In South Africa (ZA)
State: Western Cape
City Location: Cape Town
Postal: 8000
ISP: Afrihost
Organization: Afrihost
AS Number: AS37611 Afrihost

Time Zone: Africa/Johannesburg
Local Time: 18:30:38
Timezone GMT offset: 7200
Sunrise / Sunset: 07:45 / 17:44

Using Afrigreen and Afrihost.co.za should have no difference as their simply different realms. Can you please post the full traceroute?
 
Are Win10 updates set to low priority? Stuck on 0% for quite a while now.
 
Over the last few days I've been having above normal local latency. The cause of which places international games in the 250-270ms compared to 190-200 which it always has been.

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

1 1 ms 3 ms 3 ms 192.168.0.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * 37 ms jhb-up3.ip.adsl.co.za [169.1.5.29]
5 38 ms 36 ms 35 ms jhb-in2.ip.adsl.co.za [169.1.5.30]
6 36 ms 37 ms 35 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
7 38 ms 37 ms 37 ms mweb.jb1.napafrica.net [196.46.25.145]
8 79 ms 38 ms 37 ms 202.bu-ether5.vic-pe-2.optinet.net [197.80.7.103]
9 91 ms 94 ms 58 ms 197-81-226-81.jhb.mweb.co.za [197.81.226.81]
10 39 ms 40 ms 37 ms 197-81-226-61.jhb.mweb.co.za [197.81.226.61]
11 85 ms 71 ms 38 ms 197-81-229-4.jhb.mweb.co.za [197.81.229.4]
12 47 ms 36 ms 35 ms 197-81-229-15.jhb.mweb.co.za [197.81.229.15]
13 86 ms 72 ms 37 ms 41-86-112-68.mweb.co.za [41.86.112.68]

Trace complete.

Normally I'd see these pings in the 9-15ms region.

Anything that can be done?

It's possible that you're on interleaved error correction method, but I wouldn't jump to that conclusion immediately cos the latency is very intermittent in this test. We should see a small rise in latency but I would expect it to be consistent if the line is stable :(
 
30ms-40ms above normal latency doesn't seem like much, but add that on top of international latency and it becomes very noticeable.
Normally I wouldn't bother with something like this, but considering it has been 100% for months, and only started acting up now, makes me believe that there's an actual problem somewhere.

Current Downstream Sync: 10240kbps
SNR: 14.8
Attenuation: 16.3

Current Upstream Sync: 947kbps
SNR: 16.5
Attenuation: 35.6

Things I have tried:

  • Different modem
  • Different ISP (Plugg)
  • Different filter
  • Port reset by Afrihost
  • Tried Google DNS (8.8.8.8; 8.8.4.4)


Last tracert before this post:
Code:
Tracing route to afrihost.co.za [41.86.112.68]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    36 ms    34 ms    39 ms  jhb-up3.ip.adsl.co.za [169.1.5.29]
  5    37 ms    35 ms    37 ms  jhb-in1.ip.adsl.co.za [169.1.5.42]
  6    35 ms    35 ms    36 ms  jhb-net1.ip.adsl.co.za [169.1.5.52]
  7    37 ms    41 ms    43 ms  mweb.jb1.napafrica.net [196.46.25.145]
  8    36 ms    37 ms    36 ms  201.bu-ether5.vic-pe-2.optinet.net [197.80.7.71]
  9    42 ms    38 ms    37 ms  197-81-226-81.jhb.mweb.co.za [197.81.226.81]
 10    40 ms    36 ms    36 ms  197-81-226-61.jhb.mweb.co.za [197.81.226.61]
 11    38 ms    48 ms    37 ms  197-81-229-4.jhb.mweb.co.za [197.81.229.4]
 12    36 ms    38 ms    45 ms  197-81-229-11.jhb.mweb.co.za [197.81.229.11]
 13    44 ms    47 ms    35 ms  41-86-112-68.mweb.co.za [41.86.112.68]

Trace complete.

Last Speedtest before this post:
View attachment 366819
Ping: 48. | Download 9.73Mpbs | Upload 0.83Mps

It does make a difference but it should not be enough to radically change your experience. So if you are routing to UK, you should still get sub 200ms latency, which should be OK for gaming. You might see it more on US pings :(
 
Are Win10 updates set to low priority? Stuck on 0% for quite a while now.

Not as far as I know. We generally want to prioritise OS updates because of the critical nature, but as far as I know we don't treat them differently to other non-realtime services
 
You can ask Telkom to change you back to fast, BUT if Assia sees that you line is still unstable, it will just switch it back until such a time its stable.

I dont think Assia is bad unless you are a gamer unfortunately. If your line is wobbly, then it probably would be better to let the system take over to give you something of of a better experience.

I don't think ASSIA is involved, Telkom are doing this by exchange, based on the subscription and performance. This is why it's difficult to change individuals back to fast path, but I believe in certain extreme cases where Telkom can see evidence that line performance is worse, they can look into doing that where possible :(
 
It does make a difference but it should not be enough to radically change your experience. So if you are routing to UK, you should still get sub 200ms latency, which should be OK for gaming. You might see it more on US pings :(

I'd be more than happy with 200ms. That's what I always had. Its now in the 250+ region which is very noticeable.
 
I'd be more than happy with 200ms. That's what I always had. Its now in the 250+ region which is very noticeable.

Can you drop me a PM with some of your traceroutes? I'd like to compare with our results to get an idea of what the difference is :(
 
Can you drop me a PM with some of your traceroutes? I'd like to compare with our results to get an idea of what the difference is :(

Sure thing.

What should I trace? EU gaming servers?
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X