Johnatan56
Honorary Master
Online games use hardly any traffic. Can play LoL on my phones' mobile data for an hour and it uses maybe 40MB. Have you checked to see if using another provider results in lower latency? Just to rule out Afrihost.
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: If you were buying a TV today, which brand would you choose?
- Status
Online games use hardly any traffic. Can play LoL on my phones' mobile data for an hour and it uses maybe 40MB. Have you checked to see if using another provider results in lower latency? Just to rule out Afrihost.
LaraC
Honorary Master
- Joined
- Mar 11, 2014
- Messages
- 42,673
- Reaction score
- 1,847
No issues for me. 
Code:
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Users\Lara>tracert www.google.com
Tracing route to www.google.com [216.58.223.4]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 17 ms 16 ms 17 ms cpt-tx2.ip.adsl.co.za [169.1.5.81]
4 17 ms 17 ms 17 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
5 17 ms 17 ms 16 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 43 ms 42 ms 44 ms 41.164.52.40
7 38 ms 38 ms 37 ms 172.18.1.162
8 41 ms 42 ms 42 ms 72.14.194.206
9 38 ms 38 ms 38 ms 72.14.237.239
10 38 ms 38 ms 38 ms jnb01s07-in-f4.1e100.net [216.58.223.4]
Trace complete.
C:\Users\Lara>ping bras.afrihost.com
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 6ms, Average = 6msnan0s0ldier
Well-Known Member
- Joined
- Sep 19, 2013
- Messages
- 190
- Reaction score
- 24
high latency to local game servers again... Not only high latency but the ping is so unstable on second its back to normal and boom its above 100ms in the next. When i switch to telkom it solves the problem.
AFRIHOST
C:\Users\Cameron>tracert 196.28.169.67
Tracing route to 196-28-169-67.adsl.mweb.co.za [196.28.169.67]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms login.router [10.0.0.2]
2 * * * Request timed out.
3 9 ms 9 ms 16 ms jhb-up1.ip.adsl.co.za [169.1.5.5]
4 10 ms 9 ms 8 ms jhb-rx1.ip.adsl.co.za [169.1.5.18]
5 9 ms 10 ms 8 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 11 ms 10 ms 12 ms mweb.jb1.napafrica.net [196.46.25.145]
7 32 ms 31 ms 31 ms te0-0-0-3.vic-p-1.optinet.net [197.80.7.65]
8 70 ms 64 ms 76 ms te0-0-0-0.cpt-p-2.optinet.net [197.84.4.46]
9 30 ms 30 ms 33 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
10 50 ms 49 ms 49 ms 196.28.178.66
11 32 ms 30 ms 31 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
12 31 ms 30 ms 30 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
13 31 ms 31 ms 32 ms 197-84-199-18.cpt.mweb.co.za [197.84.199.18]
14 87 ms 90 ms 93 ms 196-28-169-67.adsl.mweb.co.za [196.28.169.67]
TELKOM
1 <1 ms <1 ms <1 ms login.router [10.0.0.2]
2 * * * Request timed out.
3 11 ms 10 ms 10 ms ipc-3-up.north.dsl.telkomsa.net [105.224.0.49]
4 11 ms 10 ms 10 ms ipc-3-up.north.dsl.telkomsa.net [105.224.0.50]
5 10 ms 10 ms 10 ms ipc-aggr-1.north.telkomsa.net [105.224.0.13]
6 31 ms 32 ms 31 ms ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
7 31 ms 30 ms 30 ms ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
8 32 ms 32 ms 32 ms optinet.ct1.napafrica.net [196.10.140.15]
9 33 ms 33 ms 34 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]
10 32 ms 32 ms 32 ms vl12.cpt-hscore-2.optinet.net [197.84.5.254]
11 33 ms 32 ms 32 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
12 33 ms 32 ms 32 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
13 32 ms 32 ms 31 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
14 33 ms 33 ms 32 ms 197-84-199-18.cpt.mweb.co.za [197.84.199.18]
15 33 ms 33 ms 32 ms 196-28-169-67.adsl.mweb.co.za [196.28.169.67]
AFRIHOST
C:\Users\Cameron>tracert 196.28.169.67
Tracing route to 196-28-169-67.adsl.mweb.co.za [196.28.169.67]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms login.router [10.0.0.2]
2 * * * Request timed out.
3 9 ms 9 ms 16 ms jhb-up1.ip.adsl.co.za [169.1.5.5]
4 10 ms 9 ms 8 ms jhb-rx1.ip.adsl.co.za [169.1.5.18]
5 9 ms 10 ms 8 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 11 ms 10 ms 12 ms mweb.jb1.napafrica.net [196.46.25.145]
7 32 ms 31 ms 31 ms te0-0-0-3.vic-p-1.optinet.net [197.80.7.65]
8 70 ms 64 ms 76 ms te0-0-0-0.cpt-p-2.optinet.net [197.84.4.46]
9 30 ms 30 ms 33 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
10 50 ms 49 ms 49 ms 196.28.178.66
11 32 ms 30 ms 31 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
12 31 ms 30 ms 30 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
13 31 ms 31 ms 32 ms 197-84-199-18.cpt.mweb.co.za [197.84.199.18]
14 87 ms 90 ms 93 ms 196-28-169-67.adsl.mweb.co.za [196.28.169.67]
TELKOM
1 <1 ms <1 ms <1 ms login.router [10.0.0.2]
2 * * * Request timed out.
3 11 ms 10 ms 10 ms ipc-3-up.north.dsl.telkomsa.net [105.224.0.49]
4 11 ms 10 ms 10 ms ipc-3-up.north.dsl.telkomsa.net [105.224.0.50]
5 10 ms 10 ms 10 ms ipc-aggr-1.north.telkomsa.net [105.224.0.13]
6 31 ms 32 ms 31 ms ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
7 31 ms 30 ms 30 ms ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
8 32 ms 32 ms 32 ms optinet.ct1.napafrica.net [196.10.140.15]
9 33 ms 33 ms 34 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]
10 32 ms 32 ms 32 ms vl12.cpt-hscore-2.optinet.net [197.84.5.254]
11 33 ms 32 ms 32 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
12 33 ms 32 ms 32 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
13 32 ms 32 ms 31 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
14 33 ms 33 ms 32 ms 197-84-199-18.cpt.mweb.co.za [197.84.199.18]
15 33 ms 33 ms 32 ms 196-28-169-67.adsl.mweb.co.za [196.28.169.67]
Last edited:
Geoff.D
Honorary Master
IT is quite difficult to understand what is going on. A friend of mine in the same exchange area as me gets very poor results on his Afrihost account. Yet I get very good results on my Telkom account and I do not see the same poor performance. IF he comes and connects at my place, his results show the same poor performance.
So Afrihost have to work out what is going on. Exchange congestion either exists for everyone in an exchange area or not ....
So Afrihost have to work out what is going on. Exchange congestion either exists for everyone in an exchange area or not ....
Last edited:
electrofreeze
Expert Member
browsing and latency is bad tonight
We've run a few CS:GO Lan nights here at our office (running via our IPC) and we're definitely seeing good performance when we do.
Have you got any tests that I can take a look? Even a slow 40Mbps should be sufficient for good gaming performance
I totally understand your frustration here. Let's see what we can do from this side for you
This definitely seems to point to congestion, but the best way to confirm is to test another ISP network on your line and see if the results are the same.
Unfortunately, if that is the case, there is no escalation procedure with Telkom. Their infrastructure division schedules backhaul and capacity upgrades. The best we can hope for is some sort of timeframe of when they could look at upgrades
The only way to confirm is to test with different ISP accounts. Becuase of where the latency occurs, it is still definitely on Telkom's BRAS/Exchange kit, but we can try to work with them if other ISP accounts work better so they can investigate the routing and kit they have assigned to Afrihost traffic
I'd need to look closer into that - it definitely seems a little odd.
Can you show me the results that he's getting? Is this a Home or Premium Uncapped account that could be throttled (Home) or shaped (Premium)?
Looks like the latency is on Optinet/Mweb's side
Why does it disappear when he changes to his telkom account? The latency I am getting is also on optinet and mweb hops. Change to vox and the latency i was getting from optinet disappears on their network?
Btw - if you run tests make sure to run them during peak period because thats when it starts
Last edited:
I can see that we are peering with Mweb at NapAfrica, which is the best peering point for low latency. So we're carrying the traffic on the best route possible. From there it's Optinet's network so I couldn't say what could be happening. Have you reported this to Mweb?
Geoff.D
Honorary Master
Today, running a trace route to www.afrihost.com (190.93.241.183) avoids mweb's and optinet's network, and the results are excellent!
13 ms from PTA via cloudfare .
Yesterday, the routing was via mweb and optinet and the minimum latency from PTA to the exact same IP address above never dropped below 34ms and went up to >2000 ms when the network became busy.
This issue has been around for more than 2 years, and affects just about every service provider that make use for the above two networks.
I went so far as to analyse it down to which hop and which routers were involved in may 2015, down to providing detailed information on what was wrong with the configuration on the devices I was able to access, and blow all was done about it. ....
13 ms from PTA via cloudfare .
Yesterday, the routing was via mweb and optinet and the minimum latency from PTA to the exact same IP address above never dropped below 34ms and went up to >2000 ms when the network became busy.
This issue has been around for more than 2 years, and affects just about every service provider that make use for the above two networks.
I went so far as to analyse it down to which hop and which routers were involved in may 2015, down to providing detailed information on what was wrong with the configuration on the devices I was able to access, and blow all was done about it. ....
That's odd, as far as I know we only started peering at NapAfrica when we moved over to our new network late last year.
Maybe I need to get a better idea of what you are pointing to. Can you mail me the results you are comparing on [email protected]?
Icemanbrfc
Honorary Master
Im downloading 1 torrent and its going at 1.0kB/s 
oh well im at 99% so nearly there
oh well im at 99% so nearly there
Im downloading 1 torrent and its going at 1.0kB/s
- Status