LATENCY!!!

Mine were low for a short time this afternoon, but other than that have been hight the whole day.
 
The tracert I was running (normally 10-18) peaked at an average 150 between 2-5 and then again between 7-10, otherwise it averaged about 50 for the rest of the day. By 11pm it had dropped back to normal.
I'm trying to get some of my friends in various suburbs to test during the peak times to see if their exchanges are also buggared. So at least we can narrow it down a bit more.
 
I'm not going to read all the posts in this thread... just don't have enough time right now. Telkom techies though have told me that my adsl problem (very slow speeds, high latency ie pings of over a 1000) is because of congestion. It's always the worst at night and over weekends.

They can't fix it and they don't know when it will be upgraded. :( Telkom sucks so much.
 
The good thing about all this is that Telkom has a policy which states that they will only upgrade their network (or sections of it) once it reaches 80% capacity.

A few years back one of the hops on route to the SGS servers was lagging. It took them about six months, but that exchange was then upgraded and my ping dropped down to 10.
 
Something weird was going on last night.... I only managed to download about 3 - 4 Gigs on my OpenWeb Uncapped Express+ ... where normally I am able to grab about 11 to 15 Gigs a night.
 
inferno said:
The good thing about all this is that Telkom has a policy which states that they will only upgrade their network (or sections of it) once it reaches 80% capacity.
Click to expand...

That would be intresting, but does it mean 80% of average capacity, or 80% of peak capacity? There is a huge difference between these two values...

Edit: A glance at the JINX traffic graph over a week shows the huge jumps in utilisation:
http://stats.jinx.net.za/showtotal.php?img=week

Edit: Given the current user feedback, I would say that capacity is better than 80% on average, but well over 100% during peak-periods.
 
Last edited:
So what would you guys say is the answer... stop uncapped accounts... give some suggestions to solutions!!

Would be good to see some good ideas popping up...
 
WebAfrica extremely slow browsing during office hours (Leeusig Exchange, Cape Town), switching to Telkom account and connection is brilliant!

Smells like contention ratios to me…
 
lordnokon said:
So what would you guys say is the answer... stop uncapped accounts... give some suggestions to solutions!!

Would be good to see some good ideas popping up...
Click to expand...

ADSL is a shared and best-effort service. Short of increasing the price (or making it time-of-day dependent like cellphone calls) there is no magic solution...
 
lordnokon said:
So what would you guys say is the answer... stop uncapped accounts... give some suggestions to solutions!!

Would be good to see some good ideas popping up...
Click to expand...

You either need to convince the other people on your exchange to use less data, or Telkom/ISP needs to upgrade their links.

And if you come to me with such a suggestion, I would be rude, so option 2 is the only viable one, really. Good luck getting that implemented, though.
 
who.is.michael said:
WebAfrica extremely slow browsing during office hours (Leeusig Exchange, Cape Town), switching to Telkom account and connection is brilliant!

Smells like contention ratios to me…
Click to expand...

Hi who.is.michael,

I believe that Angelo is already dealing with your slow connection issues, as I see he has a few PM's from you regarding this today and yesterday. Can you please confirm that this is in fact the case? If not, I'll be more than willing to log another query for our Engineers for you.
Thanks.




Johand said:
This is super annoying. It must be a Telkom fault. I am a WebAfrica subscriber and have been experiencing the same problem.

Traceroute through webafrica account:
1 <1 ms <1 ms <1 ms 192.168.66.1
2 6 ms 6 ms 6 ms dsl-185-88-1.dynamic.wa.co.za [41.185.88.1]
3 8 ms 7 ms 8 ms vl108.cr.gw.cpt.za.wa.co.za [196.220.59.238]
4 8 ms 8 ms 8 ms vl34.er.gw.cpt.za.wa.co.za [41.185.0.34]
5 154 ms 150 ms 148 ms upstream.vl101.gw.cpt.za.wa.co.za [196.220.59.226]
6 168 ms 161 ms 164 ms rrba-ip-esr-1-pos-8-0-0.telkom-ipnet.co.za [196.43.8.146]
7 177 ms 171 ms 165 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
8 179 ms 178 ms 174 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.30]
9 157 ms 153 ms 154 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]

And then a traceroute through an Axxess prepaid account:

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 196-210-152-1.dynamic.isadsl.co.za [196.210.152.1]
3 143 ms 141 ms 136 ms cdsl2-rba-vl2663.ip.isnet.net [196.38.73.25]
4 158 ms 161 ms 164 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 176 ms 162 ms 155 ms 168.209.1.140
6 125 ms 128 ms 128 ms 168.209.1.170
7 178 ms 181 ms 177 ms rrba-ip-spe-2-wan.telkom-ipnet.co.za [196.25.127.181]
8 156 ms 156 ms 156 ms 196.43.25.137
9 171 ms 163 ms 158 ms rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.43.11.166]
10 155 ms 161 ms 167 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
11 176 ms 165 ms 158 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.34]
12 165 ms 164 ms 172 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]

It is also very time-dependent. Late at night it is fine - have not been able to test it throughout the day.
Click to expand...


Hey Johand,

Thanks for the above provided results. To add extra information for the escalation to the Engineers, can you please run the following two tracert's using both your Web Africa and Axxess account to the following destinations:
cnn.com
wa.co.za

You are more than welcome to PM me these results so I can escalate and look into this further for you.
Thanks :)
 
Another tracert

I've also been experiencing the terrible latency (on mweb uncapped 384k, although I know its not an ISP issue):

Code: 
Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    23 ms    25 ms    22 ms  41-133-112-1.dsl.mweb.co.za [41.133.112.1]
  3   168 ms   176 ms   183 ms  196-28-178-202.adsl.mweb.co.za [196.28.178.202]

  4   160 ms   150 ms   138 ms  196.41.144.36
  5   190 ms   175 ms   181 ms  www.mweb.co.za [196.2.63.110]

I'm in Rondebosch 021 685, let me know if the full phone number will be helpful and I'll PM it to you, Will.
 
rsd said:
I've also been experiencing the terrible latency (on mweb uncapped 384k, although I know its not an ISP issue):

Code: 
Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    23 ms    25 ms    22 ms  41-133-112-1.dsl.mweb.co.za [41.133.112.1]
  3   168 ms   176 ms   183 ms  196-28-178-202.adsl.mweb.co.za [196.28.178.202][/QUOTE]

That's not terrible ;-) That's what everybody else in the Southern Suburbs has been posting on this thread...
Click to expand...
 
From here its ok (021785****)

Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway [10.0.0.2]
2 * * * Request timed out.
3 8 ms 9 ms 8 ms 196-28-178-202.adsl.mweb.co.za [196.28.178.202]
4 9 ms 9 ms 9 ms 196.41.144.36
5 10 ms 10 ms 10 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
Then this will bring tears to your eyes:

Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 10 ms 9 ms 41-133-112-1.dsl.mweb.co.za [41.133.112.1]
3 161 ms 159 ms 157 ms 196-28-178-166.adsl.mweb.co.za [196.28.178.166]

4 157 ms 152 ms 155 ms 196.41.144.36
5 149 ms 148 ms 146 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
506easyEASY said:
From here its ok (021785****)

Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway [10.0.0.2]
2 * * * Request timed out.
3 8 ms 9 ms 8 ms 196-28-178-202.adsl.mweb.co.za [196.28.178.202]
4 9 ms 9 ms 9 ms 196.41.144.36
5 10 ms 10 ms 10 ms www.mweb.co.za [196.2.63.110]

Trace complete.
Click to expand...

Is that for real (like not 7am in the morning)? If so then Fishoek must be on a different ESR, since most of the Southern Suburbs (plus parts of the CBD) seem to be having the same problem. Will@MWeb has been trying to escalate this issue with Telkom, but no response so far.

teRRRier said:
Then this will bring tears to your eyes:

Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 10 ms 9 ms 41-133-112-1.dsl.mweb.co.za [41.133.112.1]
3 161 ms 159 ms 157 ms 196-28-178-166.adsl.mweb.co.za [196.28.178.166]
Click to expand...

I've got exactly the same 3rd hop time, the ESR is in between the 2nd and 3rd hop somewhere...
 
Last edited:
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X