LATENCY!!!

Joker said:
You won't get that in other countries - it's all relative man.
Click to expand...

Have you lived abroad?

You won't get these issues in the First World; as companies that deliver this type of connectivity and service will not exist - as people vote with their wallets, but locals feel they must support companies no matter what – I guess this is what you get for consumer apathy.
 
Pity this is what it takes to pull fingers out asses though.
Click to expand...

Unless we get some actual real press about this issue we can only rely on Jeff and Will to take the fight to Telkom. Considering the ridiculous amounts of hits and replies to this thread you think that one of the guys who writes for this site would be like "I smell a story here!" But we seem to be getting ignored...

I'm a qualified journalist, if one of the owners of MYBB tells me to write the story and they will put it up, believe me, I will do it in a flash.
 
Im in Newlands (021685) and im on a 10 meg and im having the same problem, 150ms during the day, back to 10ms after 11.30 pm....
 
who.is.michael said:
Have you lived abroad?

You won't get these issues in the First World; as companies that deliver this type of connectivity and service will not exist - as people vote with their wallets, but locals feel they must support companies no matter what – I guess this is what you get for consumer apathy.
Click to expand...

Apparently you haven't lived abroad either since "First World" ISPs are notorious for being just as bad as ours.

Also I noticed this notice and I wonder if it's related somehow:
http://mybroadband.co.za/vb/showthr...on-the-Telkom-Network-at-NNOC-(Western-Region)
mybb.bot said:
Basic issue: Link - To perform Planned Maintenance on the Telkom Network at NNOC (Western Region)

Time Down: Sat, 23 Oct 2010 22:00:00 +0200

Full Problem Description

Ref: NN0005932Category Planned Work Type: Planned Work Status: New
TimeDown: Sat, 23 Oct 2010 22:00:00 +0200 ETTR: 8 Hours
Areas affected: DSLAM Affected: BERGVLIET 1 DSLAM Affected: BERGVLIET 2 DSLAM Affected: BERGVLIET 3 DSLAM Affected: BERGVLIET 4 DSLAM Affected: BERGVLIET 5 DSLAM Affected: BERGVLIET 6 DSLAM Affected: BERGVLIET 8 IMAX_2 DSLAM Affected: BLUE VALLEY DSLAM Affected: CONSTANTIA 1 DSLAM Affected: CONSTANTIA 2 DSLAM Affected: CONSTANTIA 3 DSLAM Affected: CONSTANTIA 4 DSLAM Affected: CONSTANTIA NOVA DSLAM Affected: DELFORD RD FI04 DSLAM Affected: FISHHOEK 1 DSLAM Affected: FISHHOEK 2 DSLAM Affected: FISHHOEK 3 IMAX_1 DSLAM Affected: GLEN ALPINE DSLAM Affected: HOMESTEAD (W) DSLAM Affected: HOUTBAAI 1 DSLAM Affected: HOUTBAAI 2 DSLAM Affected: HOUTBAAI 4 DSLAM Affected: HOUTBAAI 5 DSLAM Affected: KENILWORTH RACE COURSE DSLAM Affected: KOMMETJIE DSLAM Affected: LAKESIDE A22 DSLAM Affected: LLANDUDNO-GULLY DSLAM Affected: LLANDUDNO-OAKBURN DSLAM Affected: MUIZENBERG 1 DSLAM Affected: MUIZENBERG 2 DSLAM Affected: MUIZENBERG 3 DSLAM Affected: NOORDHOEK DSLAM Affected: NOORDHOEK 2 DSLAM Affected: OTTERY 1 DSLAM Affected: OTTERY 2 DSLAM Affected: OTTERY 3 IMAX_1 DSLAM Affected: PETER CLOETE DSLAM Affected: REGENT SQUARE DSLAM Affected: RUITERPLAATS 2 D7 DSLAM Affected: SCARBOROUGH DSLAM Affected: SPAANSCHEMAT C19 DSLAM Affected: STEENBERG DSLAM Affected: STEENBERG 2 DSLAM Affected: STEENBERG 3 DSLAM Affected: STEURHOF D25A1 DSLAM Affected: SUNNYDALE 1 DSLAM Affected: SUNNYDALE 2 DSLAM Affected: UPPER RECREATION FI05 DSLAM Affected: WATERFALL LANE A27B2 DSLAM Affected: WESTLAKE SQUARE DSLAM Affected: WETTON STATION B31A3 DSLAM Affected: WYNBERG 1 DSLAM Affected: WYNBERG 10 IMAX_1 DSLAM Affected: WYNBERG 2 DSLAM Affected: WYNBERG 3 DSLAM Affected: WYNBERG 5 DSLAM Affected: WYNBERG 6 DSLAM Affected: WYNBERG 7 DSLAM Affected: WYNBERG 8 DSLAM Affected: ZWAANSWYK E17
Progress:
Click to expand...
 
Last edited:
Last edited:
The domestic worker unplugged the phone cable this morning so unfortunately my ping stats are lacking :(

I'll let it run through the night and post / email the results tomorrow
 
Tracing route to mix.isgaming.co.za [196.38.180.45]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Billion.800VGT [10.0.0.2]
2 8 ms 9 ms 8 ms dsl-242-172-01.telkomadsl.co.za [41.2
3 185 ms 179 ms 174 ms 196.38.73.113
4 162 ms 153 ms 150 ms cdsl2-rba-vl150.ip.isnet.net [196.38.
5 135 ms 134 ms 141 ms 196.26.0.61
6 168 ms 170 ms 175 ms 168.209.100.242
7 169 ms 163 ms 152 ms 168.209.217.22
8 163 ms 152 ms 150 ms mix.isgaming.co.za [196.38.180.45]

Trace complete.
 
Just so happens that none of our affected Dslams are on that list. hehehe.

Hopefully those Dslams were the ones affected and it was rerouted to us hence the congestion. Holding thumbs.
 
Well... this sucks...

I'm back on the lag bus with you guys :(
 
Gordon_R said:
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...
Click to expand...

I was just thinking in more detail about this idea that I posted earlier, and the conclusions are scary! If average latency increases to over 250ms, then every packet will be lost (100%) due to the fact that TTL can only be set to 255ms (binary 2 ^ 8).

If this happened the TCP/IP throughput would effectively be zero (all packets would be continually sent and retransmitted). That would really be fun! I wonder if Telkom realises how close we are to that situation now...
 
Gordon_R said:
I was just thinking in more detail about this idea that I posted earlier, and the conclusions are scary! If average latency increases to over 250ms, then every packet will be lost (100%) due to the fact that TTL can only be set to 255ms (binary 2 ^ 8).

If this happened the TCP/IP throughput would effectively be zero (all packets would be continually sent and retransmitted). That would really be fun! I wonder if Telkom realises how close we are to that situation now...
Click to expand...

I wish! If it is not working Telkom would be obliged to fix it :-) Unfortunately your argument holds no water - TTL is the number of hops and not time. They have renamed it in IPv6 to make it a bit clearer.
 
Gordon_R said:
I was just thinking in more detail about this idea that I posted earlier, and the conclusions are scary! If average latency increases to over 250ms, then every packet will be lost (100%) due to the fact that TTL can only be set to 255ms (binary 2 ^ 8).

If this happened the TCP/IP throughput would effectively be zero (all packets would be continually sent and retransmitted). That would really be fun! I wonder if Telkom realises how close we are to that situation now...
Click to expand...

TTL is hop count not actual time.
 
384Kbps line limping along at (021) 683-87**. ISP is Been-Fishing and trying to get any work done online has been a mission over the past 6 weeks. At least now I know to blame Telkom...
 
Lobesy said:
TTL is hop count not actual time.
Click to expand...

True, but if the 2nd hop is 6-8ms (which it always is), and the 3rd hop is 265ms (which is not that unrealistic given the current trend), then the packet will be lost.

It's only a 'thought-experiment', but interesting to take the situation to its logical conclusion...

If you look at one of my min/max graphs, there are plenty of cases with 3rd hop latency around 170ms.

Edit: http://www.imagehost.co.za/image-2CC7_4CC1D365.gif
 
Last edited:
Gordon_R said:
True, but if the 2nd hop is 6-8ms (which it always is), and the 3rd hop is 265ms (which is not that unrealistic given the current trend), then the packet will be lost.

It's only a 'thought-experiment', but interesting to take the situation to its logical conclusion...

If you look at one of my min/max graphs, there are plenty of cases with 3rd hop latency around 170ms.

Edit: http://www.imagehost.co.za/image-2CC7_4CC1D365.gif
Click to expand...

Latency and TTL have nothing to do with each other, a high latency will not cause the packet to be dropped from TTL.
 
Gordon_R said:
True, but if the 2nd hop is 6-8ms (which it always is), and the 3rd hop is 265ms (which is not that unrealistic given the current trend), then the packet will be lost.

It's only a 'thought-experiment', but interesting to take the situation to its logical conclusion...

If you look at one of my min/max graphs, there are plenty of cases with 3rd hop latency around 170ms.
Click to expand...

When accessing the internet with satellite (yes - I have done so from one of our neighboring countries) latency can typically go over 2 seconds (2000ms). When you have a VPN you can do the following route in a single hop - middle of Africa-Houston, Texas, To London, To Cape Town, To Johannesburg). Obviously useless for playing games, but fine for servers to route e-mail. Pings do time-out but you can always increase the time-out values on your OS. So we can have to a lot more latency than we have now and still have some form of connection.

What I find interesting about our current situation is the fact that certain destinations seems unaffected on certain ISPs - e.g. mtn servers on mtn based ADSL, SAIX game servers on SAIX connections. I wonder whether they prioritize traffic to certain destinations.
 
Sorry, my bad! I genuinely thought TTL was the expiry time between hops (edit) in miliseconds (edit).

Edit: Wikipedia explains the hop decrement process fairly well:
http://en.wikipedia.org/wiki/Time_to_live

I am fully aware that the total latency can exceed 1000ms (I have seen plenty of tracerts that do that...)
 
Last edited:
Well the TTL is the limit really but if congestion is occurring on a router then less important packets could get dropped.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X