-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: Did you buy your last car with cash or on a finance plan?
LATENCY!!!
- Thread starter Pooky
- Start date
teRRRier
Active Member
Unbelievable!. I'm running HLSW as well. That first server on your first pic - I'm running at a ping of around 200 to it. Mweb account. Clarinche.
That does not make any sense tbh. Although a friend of mine on ClareInch was getting 30-50ms tonite on SGS TF2 Servers and the 196.38.180.26 IS TF2 server, but 200ms on 196.38.180.45 which is also a TF2 server, he is using Afrhost Unshaped.
Hello,
I tried something new tonight... I suspect congestion on Rondebosch might not be the only problem. I tried my FNB Connect account. Here is prelimenary traceroutes - I am busy plotting more comprehensive stats - but maybe somebody else can verify this:
Tracing route to www.mtn.co.za [196.11.240.17]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.66.1
2 7 ms 6 ms 6 ms 41.183.28.1
3 31 ms 28 ms 28 ms 41.183.132.6
4 28 ms 29 ms 28 ms 41.183.132.68
5 28 ms 28 ms 28 ms 41.183.132.82
6 29 ms 29 ms 30 ms ge0-2sub110.gw10.jnb6.za.mtnbusiness.net [196.31.44.185]
7 30 ms 30 ms 30 ms rb-dca-1.za--rb-cr-1.za-a.mtnns.net [196.44.0.147]
8 30 ms 30 ms 30 ms mtn-rb-1--rb-ad-1-a.mtnns.net [196.44.8.211]
9 * * * Request timed out.
10 30 ms 30 ms 30 ms 196-11-240-17.mtn.co.za [196.11.240.17]
Trace complete.
Tracing route to www.telkom.co.za [196.43.22.222]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.66.1
2 6 ms 6 ms 6 ms 41.183.28.1
3 28 ms 28 ms 28 ms 41.183.132.6
4 29 ms 29 ms 28 ms 41.183.132.68
5 33 ms 28 ms 35 ms 41.183.132.82
6 29 ms 31 ms 29 ms ge0-2sub110.gw10.jnb6.za.mtnbusiness.net [196.31.44.185]
7 163 ms 151 ms 141 ms ge0-1.br1.jnb6.za.mtnbusiness.net [196.30.1.221]
8 116 ms 108 ms 108 ms 196.30.16.182
9 167 ms 163 ms 163 ms 196.43.25.137
10 188 ms 185 ms 186 ms rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.43.11.166]
11 149 ms 142 ms 142 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
12 184 ms 178 ms 186 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.34]
13 * 172 ms * nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]
14 192 ms 195 ms * nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]
15 201 ms 196 ms 196 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]
Trace complete.
Tracing route to www.telkom.co.za [196.43.22.222]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.66.1
2 6 ms 6 ms 6 ms 41.183.28.1
3 28 ms 28 ms 28 ms 41.183.132.6
4 29 ms 29 ms 28 ms 41.183.132.68
5 33 ms 28 ms 35 ms 41.183.132.82
6 29 ms 31 ms 29 ms ge0-2sub110.gw10.jnb6.za.mtnbusiness.net [196.31.44.185]
7 163 ms 151 ms 141 ms ge0-1.br1.jnb6.za.mtnbusiness.net [196.30.1.221]
8 116 ms 108 ms 108 ms 196.30.16.182
9 167 ms 163 ms 163 ms 196.43.25.137
10 188 ms 185 ms 186 ms rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.43.11.166]
11 149 ms 142 ms 142 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
12 184 ms 178 ms 186 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.34]
13 * 172 ms * nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]
14 192 ms 195 ms * nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]
15 201 ms 196 ms 196 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]
Trace complete.
I tried something new tonight... I suspect congestion on Rondebosch might not be the only problem. I tried my FNB Connect account. Here is prelimenary traceroutes - I am busy plotting more comprehensive stats - but maybe somebody else can verify this:
Tracing route to www.mtn.co.za [196.11.240.17]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.66.1
2 7 ms 6 ms 6 ms 41.183.28.1
3 31 ms 28 ms 28 ms 41.183.132.6
4 28 ms 29 ms 28 ms 41.183.132.68
5 28 ms 28 ms 28 ms 41.183.132.82
6 29 ms 29 ms 30 ms ge0-2sub110.gw10.jnb6.za.mtnbusiness.net [196.31.44.185]
7 30 ms 30 ms 30 ms rb-dca-1.za--rb-cr-1.za-a.mtnns.net [196.44.0.147]
8 30 ms 30 ms 30 ms mtn-rb-1--rb-ad-1-a.mtnns.net [196.44.8.211]
9 * * * Request timed out.
10 30 ms 30 ms 30 ms 196-11-240-17.mtn.co.za [196.11.240.17]
Trace complete.
Tracing route to www.telkom.co.za [196.43.22.222]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.66.1
2 6 ms 6 ms 6 ms 41.183.28.1
3 28 ms 28 ms 28 ms 41.183.132.6
4 29 ms 29 ms 28 ms 41.183.132.68
5 33 ms 28 ms 35 ms 41.183.132.82
6 29 ms 31 ms 29 ms ge0-2sub110.gw10.jnb6.za.mtnbusiness.net [196.31.44.185]
7 163 ms 151 ms 141 ms ge0-1.br1.jnb6.za.mtnbusiness.net [196.30.1.221]
8 116 ms 108 ms 108 ms 196.30.16.182
9 167 ms 163 ms 163 ms 196.43.25.137
10 188 ms 185 ms 186 ms rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.43.11.166]
11 149 ms 142 ms 142 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
12 184 ms 178 ms 186 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.34]
13 * 172 ms * nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]
14 192 ms 195 ms * nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]
15 201 ms 196 ms 196 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]
Trace complete.
Tracing route to www.telkom.co.za [196.43.22.222]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.66.1
2 6 ms 6 ms 6 ms 41.183.28.1
3 28 ms 28 ms 28 ms 41.183.132.6
4 29 ms 29 ms 28 ms 41.183.132.68
5 33 ms 28 ms 35 ms 41.183.132.82
6 29 ms 31 ms 29 ms ge0-2sub110.gw10.jnb6.za.mtnbusiness.net [196.31.44.185]
7 163 ms 151 ms 141 ms ge0-1.br1.jnb6.za.mtnbusiness.net [196.30.1.221]
8 116 ms 108 ms 108 ms 196.30.16.182
9 167 ms 163 ms 163 ms 196.43.25.137
10 188 ms 185 ms 186 ms rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.43.11.166]
11 149 ms 142 ms 142 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
12 184 ms 178 ms 186 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.34]
13 * 172 ms * nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]
14 192 ms 195 ms * nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]
15 201 ms 196 ms 196 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]
Trace complete.
I am glad that there are many willing participants with patience to post graphs etc and a willing ISP rep to take that evidence and go straight to the people that matter. It's nice to see this in a public forum instead of having individuals fobbed off by low level call centre guys.
With any luck, this will get sorted soon!
With any luck, this will get sorted soon!
Gordon_R
Honorary Master
I've thought about this statement a lot, and come to the conclusion that it is fundamentally wrong from two points of view:
1. Of all the tracerts posted by me, and many other people, not one has any significant problem with hop 2, which is where the DSLAM is on the tracert, the problem is always on the hop 3 stage.
2. To produce such a steady latency as shown by the graphs of teRRRier and others (plus mine), requires a very large volume of traffic going through a single router.
I can't prove it mathematically, but if the congestion were at the DSLAM level, the latency would be spiking all over the place, instead of an almost straight line, for a very extended period...
Edit: No amount of obfuscation or denial is going to change those basic facts. Trying to imagine otherwise makes me think very unkind thoughts. Captain of the Titanic: "Oh its just some isolated patches of ice..."
Last edited:
Latency is a whole lot better after 12.00AM for me
021557xxxx (Table View exchange) - Web Africa account
Pinging www.webafrica.co.za [196.220.58.66] with 32 bytes of data:
Reply from 196.220.58.66: bytes=32 time=9ms TTL=121
Reply from 196.220.58.66: bytes=32 time=8ms TTL=121
Reply from 196.220.58.66: bytes=32 time=9ms TTL=121
Reply from 196.220.58.66: bytes=32 time=9ms TTL=121
Ping statistics for 196.220.58.66:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 9ms, Average = 8ms
Pinging www.telkom.co.za [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=35ms TTL=246
Reply from 196.43.22.222: bytes=32 time=35ms TTL=246
Reply from 196.43.22.222: bytes=32 time=35ms TTL=246
Request timed out.
Ping statistics for 196.43.22.222:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 35ms, Average = 35ms
Lets hope it stays like this
I'll continue plotting throughout the day to see what happens
021557xxxx (Table View exchange) - Web Africa account
Pinging www.webafrica.co.za [196.220.58.66] with 32 bytes of data:
Reply from 196.220.58.66: bytes=32 time=9ms TTL=121
Reply from 196.220.58.66: bytes=32 time=8ms TTL=121
Reply from 196.220.58.66: bytes=32 time=9ms TTL=121
Reply from 196.220.58.66: bytes=32 time=9ms TTL=121
Ping statistics for 196.220.58.66:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 9ms, Average = 8ms
Pinging www.telkom.co.za [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=35ms TTL=246
Reply from 196.43.22.222: bytes=32 time=35ms TTL=246
Reply from 196.43.22.222: bytes=32 time=35ms TTL=246
Request timed out.
Ping statistics for 196.43.22.222:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 35ms, Average = 35ms
Lets hope it stays like this
I'll continue plotting throughout the day to see what happens
Last edited:
yup, my latency improves at 12am every night... and this has been the case for the last month. so expect it to rise again after 8am when people start to wake up and use their lines (this is congestion). telkom just phoned me awake at 7:30 to check on the problem. but ofcoarse my ping is stable now... ****ers!
who.is.michael
Expert Member
Gordon_R
Honorary Master
Latency is a whole lot better after 12.00AM for me
The trend is clear, but the graph is a little hard to read. You can 'stretch' the chart in PingPlotter to make it larger (click on the dividing line and drag upwards). Also focus on the 3rd hop (not the first hop), since this is where the congestion is.
I didn't do an overnight run, but my latency has started to creep up to 50ms this morning. (I will post once it gets to 150ms).
Surv0
Executive Member
- Joined
- Jan 7, 2006
- Messages
- 5,742
- Reaction score
- 539
yup its on the climb again
Yup around 11:15pm the latency generally drops suddenly from 160ms to 30ms, its amazing actually.
Gordon is correct it is not at the Dslams, the 2nd hop is within 7ms generally, its the 3rd where the problem occurs. I am not sure how they would work, but I think it would be the router that a handfull of dslams connect to before hitting the data center.
We also need to realise when this all started, 2/2.5 months ago, this was happening maybe twice a week, and slowly it became a daily feature. Now most of the day, not just 6:30-11:30pm. So it could very likely be extra traffic or a faulty part somewhere along the line.
In my opinion, Initially it was less of a problem so gamers played games, as it got worse, gamers stopped playing games because it clearly makes us go em0 and rAGE and started leaving there massive downloads on just like me, meaning congestion has just gotten Worse per day and now there is no return unless they invest a bit of money in something.
NB: I actually just got a call from telkom and the guy said the reason my latency and speed is not at 3/4mb is coz i am too far from the exchange, so I asked how far, he sed 2Km, I started laughing, so I said, so explain to me how during the day my latency is at 30ms and speed is at full 4mb and in the night it changes, he said we were told to phone the guys that logged the calls in these areas and tell them this. Hahaha. That made my day.lol. Cancelling Telkom/WA/Axxess/ All/ Over it
Gordon is correct it is not at the Dslams, the 2nd hop is within 7ms generally, its the 3rd where the problem occurs. I am not sure how they would work, but I think it would be the router that a handfull of dslams connect to before hitting the data center.
We also need to realise when this all started, 2/2.5 months ago, this was happening maybe twice a week, and slowly it became a daily feature. Now most of the day, not just 6:30-11:30pm. So it could very likely be extra traffic or a faulty part somewhere along the line.
In my opinion, Initially it was less of a problem so gamers played games, as it got worse, gamers stopped playing games because it clearly makes us go em0 and rAGE and started leaving there massive downloads on just like me, meaning congestion has just gotten Worse per day and now there is no return unless they invest a bit of money in something.
NB: I actually just got a call from telkom and the guy said the reason my latency and speed is not at 3/4mb is coz i am too far from the exchange, so I asked how far, he sed 2Km, I started laughing, so I said, so explain to me how during the day my latency is at 30ms and speed is at full 4mb and in the night it changes, he said we were told to phone the guys that logged the calls in these areas and tell them this. Hahaha. That made my day.lol. Cancelling Telkom/WA/Axxess/ All/ Over it
Gordon_R
Honorary Master
This is what I have so far, pretty much the norm:
That trace looks like the Clareinch exchange (same 2nd hop as mine 41.132.48.1). It makes sense that our graphs are similar. TeRRRier is on a completely different 2nd hop (41.133.112.1 probably Rondebosch).
More graphs would help, but this is really just pounding the nail in the coffin. The evidence is clearly there for anybody who wants to 'see' it, and not deny it...
JP: The congestion theory makes sense. The 3rd hop includes what Will says is the ERS stage. I'm not a gamer, so I didn't notice until recently (assuming it was just SAIX/MWeb/SEACOM or whatever). LOL at the techie BS ;-)
I'm just wondering: Is this congestion forcibly lowering the throughput of ADSL, by continually delaying packets, so that users get discouraged and do something else...
Last edited:
http://i.imgur.com/9RKm7.png
heres the graph of the last 12 hours for me... as you can see its creeping back up. im not going to email this one to [email protected] ill rather wait till i have a 24hour graph showing the full extent of the problem.
notice the EXTREME packet loss! is it this bad for anyone else?
heres the graph of the last 12 hours for me... as you can see its creeping back up. im not going to email this one to [email protected] ill rather wait till i have a 24hour graph showing the full extent of the problem.
notice the EXTREME packet loss! is it this bad for anyone else?