LATENCY!!!

Hi guys,

I've updated this thread regarding latency and speed issues on the Web Africa network.
As mentioned, we are waiting on final confirmation from our Engineering team regarding the update on the issue.

Again, we'd like to extend our apologies in the way this has been handled. I can assure everyone that we have learnt from this and will have measures in place to improve our online presence in leaps and bounds :)
 
Log a fault with Telkom and make it clear that its an exchange problem which everyone in your area is experiencing. It's not much, but its the best we can do for now. Will@MWEB should hopefully report back on what is happening.

I think raVid's suggestion is an excellent one, if you know you're affected by this then you should log a fault, but state clearly in your fault log that you want them to check the back haul links for congestion as you are having constant latency and reduced speed problems.
 
I think raVid's suggestion is an excellent one, if you know you're affected by this then you should log a fault, but state clearly in your fault log that you want them to check the back haul links for congestion as you are having constant latency and reduced speed problems.

From my experience telkom are never forth coming regarding exchange issues.
 
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 9 ms 8 ms 9 ms 196-28-178-202.adsl.mweb.co.za [196.28.178.202]
4 8 ms 11 ms 9 ms 196.41.144.36
5 10 ms 9 ms 10 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
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 9 ms 8 ms 9 ms 196-28-178-202.adsl.mweb.co.za [196.28.178.202]
4 8 ms 11 ms 9 ms 196.41.144.36
5 10 ms 9 ms 10 ms www.mweb.co.za [196.2.63.110]

Trace complete.

Stop that! You're irritating the rest of us... Average local latency today 120-150ms (Clareinch).
 
Atm, Ping is High:( Usually its only in the night, Tracert to 196.38.180.45

1 1 ms <1 ms <1 ms Billion.800VGT [10.0.0.2]
2 8 ms 7 ms 7 ms dsl-242-172-01.telkomadsl.co.za [41.242.172.1]
3 150 ms 157 ms 160 ms cdsl1-rba-vl2460.ip.isnet.net [196.38.72.217]
4 156 ms 158 ms 156 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
5 144 ms 149 ms 149 ms 196.26.0.60
6 135 ms 124 ms 120 ms 168.209.100.238
7 146 ms 149 ms 146 ms 168.209.218.22
8 160 ms 161 ms 164 ms mix.isgaming.co.za [196.38.180.45]

Trace complete.
 
I got a call from one of the Techies at my exchange (Rondebosch) this morning, he says that they are looking into the issue and its affecting him too as a online gamer. So the guys with some influence are feeling our pain too. He also said that the ISP's were giving them a hard time about it too and that they are "vigorously" looking into the issue. He said its as a result of something in the chain not being able to handle the upgrade. Its much better to speak to one of the guys on the ground, you get some straight answers.

PS dont waste your time with the call centre, they have no $#@%ing clue.
 
Last edited:
I got a call from one of the Techies at my exchange (Rondebosch) this morning, he says that they are looking into the issue and its affecting him too as a online gamer. So the guys with some influence are feeling our pain too. He also said that the ISP's were giving them a hard time about it too and that they are "vigorously" looking into the issue. He said its as a result of something in the chain not being able to handle the upgrade. Its much better to speak to one of the guys on the ground, you get some straight answers.

Thanks a lot for the heads up, it's great to think that there are people who work for Telkom who want what we want and have the ability to do something about it. Let's hope they get the issue sorted out soon.
 
I live in Melkbosstrand (021 553), 25km north of Cape Town. I've not played on any local servers in ages. my wow ping is rediculously high (900+ avg.) I was happy with 500ms on my mweb 4mb uncapped account. Sure it was not near the 230ms I got on WA unshaped + lowerping, but I could get on fine with that... ATM I can't play, my guild is a top200 guild. If this keeps up I'm going to probably just call it a day and take up golf... I have a fault logged with Telkom, phoned them again today and they told me the technician will phone me back...

Code:
noise margin: 24.9 dB
Line Attenuation: 28.5 dB
Output Power: 10 dB
Code:
Tracing route to games.saix.net [196.43.22.222]
over a maximum of 30 hops:

  1    <1 ms     1 ms     1 ms  10.0.0.2 
  2     *        *        *     Request timed out.
  3     9 ms     9 ms     9 ms  196-28-178-190.adsl.mweb.co.za [196.28.178.190] 
  4    36 ms    36 ms    36 ms  196.22.169.45 
  5   103 ms   101 ms   104 ms  196.22.169.61 
  6   133 ms   159 ms   131 ms  tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225] 
  7    44 ms    48 ms    52 ms  rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249] 
  8    40 ms    44 ms    45 ms  rrba-ip-esr-1-pos-8-0-0.telkom-ipnet.co.za [196.43.8.146] 
  9    97 ms   103 ms    96 ms  rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6] 
 10    37 ms    37 ms    36 ms  nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.30] 
 11    82 ms    80 ms    76 ms  nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222] 

Trace complete.


Tracing route to www.telkomsa.net [196.25.211.40]
over a maximum of 30 hops:

  1     1 ms     1 ms    <1 ms  10.0.0.2 
  2     *        *        *     Request timed out.
  3    11 ms    10 ms    10 ms  196-28-178-178.adsl.mweb.co.za [196.28.178.178] 
  4    34 ms    34 ms    34 ms  196.22.169.49 
  5    44 ms    45 ms    43 ms  196.22.169.61 
  6   121 ms   173 ms   129 ms  tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225] 
  7    34 ms    34 ms    34 ms  rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249] 
  8    36 ms    35 ms    37 ms  nbsc-ip-er-1-pos-8-0-0.telkom-ipnet.co.za [196.43.25.58] 
  9   114 ms    52 ms    38 ms  196.25.181.54 
 10    56 ms    59 ms    56 ms  196.25.211.40 

Trace complete.

Tracing route to wow-europe.com [80.239.186.22]
over a maximum of 30 hops:

  1     1 ms     1 ms    <1 ms  10.0.0.2 
  2     *        *        *     Request timed out.
  3     9 ms    10 ms    10 ms  196-28-178-178.adsl.mweb.co.za [196.28.178.178] 
  4    34 ms    34 ms    34 ms  196.22.169.49 
  5   123 ms   118 ms   115 ms  196.22.169.61 
  6    84 ms    79 ms    72 ms  tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225] 
  7   101 ms   105 ms    91 ms  tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211] 
  8   279 ms   280 ms   266 ms  196.22.175.218 
  9   292 ms   302 ms   307 ms  149.6.98.5 
 10   270 ms   283 ms   371 ms  te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165] 
 11   421 ms   382 ms   275 ms  te1-2.mpd01.lon01.atlas.cogentco.com [130.117.3.225] 
 12   259 ms   277 ms   298 ms  ldn-b4-link.telia.net [213.248.70.237] 
 13   289 ms   278 ms   256 ms  ldn-bb2-link.telia.net [80.91.251.14] 
 14   355 ms   354 ms   306 ms  prs-bb2-link.telia.net [80.91.247.240] 
 15   277 ms   336 ms   308 ms  prs-b7-link.telia.net [80.91.252.142] 
 16   304 ms   266 ms   266 ms  prs-sdix-i1-link.telia.net [80.91.248.113] 
 17  80-239-170-114.customer.teliacarrier.com [80.239.170.114]  reports: Destination net unreachable.

Trace complete.

Any info will be appreciated. Thanks
 
I live in Melkbosstrand (021 553), 25km north of Cape Town. I've not played on any local servers in ages. my wow ping is rediculously high (900+ avg.) I was happy with 500ms on my mweb 4mb uncapped account. Sure it was not near the 230ms I got on WA unshaped + lowerping, but I could get on fine with that... ATM I can't play, my guild is a top200 guild. If this keeps up I'm going to probably just call it a day and take up golf... I have a fault logged with Telkom, phoned them again today and they told me the technician will phone me back...

Code:
noise margin: 24.9 dB
Line Attenuation: 28.5 dB
Output Power: 10 dB
Code:
Tracing route to games.saix.net [196.43.22.222]
over a maximum of 30 hops:

  1    <1 ms     1 ms     1 ms  10.0.0.2 
  2     *        *        *     Request timed out.
  3     9 ms     9 ms     9 ms  196-28-178-190.adsl.mweb.co.za [196.28.178.190] 
  4    36 ms    36 ms    36 ms  196.22.169.45 
  5   103 ms   101 ms   104 ms  196.22.169.61 
  6   133 ms   159 ms   131 ms  tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225] 
  7    44 ms    48 ms    52 ms  rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249] 
  8    40 ms    44 ms    45 ms  rrba-ip-esr-1-pos-8-0-0.telkom-ipnet.co.za [196.43.8.146] 
  9    97 ms   103 ms    96 ms  rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6] 
 10    37 ms    37 ms    36 ms  nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.30] 
 11    82 ms    80 ms    76 ms  nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222] 

Trace complete.


Tracing route to www.telkomsa.net [196.25.211.40]
over a maximum of 30 hops:

  1     1 ms     1 ms    <1 ms  10.0.0.2 

<<snip>>

 10    56 ms    59 ms    56 ms  196.25.211.40 

Trace complete.

Tracing route to wow-europe.com [80.239.186.22]
over a maximum of 30 hops:

  1     1 ms     1 ms    <1 ms  10.0.0.2 
  2     *        *        *     Request timed out.
  3     9 ms    10 ms    10 ms  196-28-178-178.adsl.mweb.co.za [196.28.178.178] 
  4    34 ms    34 ms    34 ms  196.22.169.49 
  5   123 ms   118 ms   115 ms  196.22.169.61 
  6    84 ms    79 ms    72 ms  tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225] 
  7   101 ms   105 ms    91 ms  tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211] 
  8   279 ms   280 ms   266 ms  196.22.175.218 

<<snip>>

 16   304 ms   266 ms   266 ms  prs-sdix-i1-link.telia.net [80.91.248.113] 
 17  80-239-170-114.customer.teliacarrier.com [80.239.170.114]  reports: Destination net unreachable.

Trace complete.

Any info will be appreciated. Thanks

This probably isn't an example from when it's really busy, since the tracerts you have posted are pretty much what everybody else is getting, nothing unusual AFIAK.
 
Code:
Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.1.254
  2    22 ms    19 ms    19 ms  41-132-48-1.dsl.mweb.co.za [41.132.48.1]
  3   178 ms   171 ms   168 ms  196-28-178-166.adsl.mweb.co.za [196.28.178.166]

  4   164 ms   165 ms   166 ms  196.41.144.36
  5   145 ms   146 ms   147 ms  www.mweb.co.za [196.2.63.110]

Trace complete.

Clareinch - 384kbps. 7:12pm.
 
Just a quick update for the evening gents. The feedback I was promised today did not materialize and I will refrain from expressing an opinion about that. Needless to say I have followed up both telephonically and in writing and I can assure you that it will be taken up at a more senior level.
 
hi guys, i am new here so excuse the dumb questions!

If you say "ping" do you mean with the Command prompt if you type in e.g. ping www.myadsl.co.za - must one look at the "round trip milliseconds"?

I use www.speedtest.net to check my connection speed. It gives 3 readings namely Download Speed, Upload Speed and a Ping. Is this Ping the same as the one with the CMD prompt?

Another question: does the data supplier (I use FNB Connect) influence the download speed? I guess so? When I phoned FNB Connect today the oke (which sounds dumber than me) says it must be Telkom.

For the past week my home and work connection (both 4meg lines) have been terrible (download speed 0.40Mb/s , ping is alright i guess at 35ms). My neighbors connection is ok (he uses Mweb for data), he gets 2.3Mbs download speed. My home and work is 1km from each other and uses the same exchange (I strongly suspect). So the only common denominator is my data supplier.

I am going to test with my other (Telkom) data bundle and see what happens
 
Just a quick update for the evening gents. The feedback I was promised today did not materialize and I will refrain from expressing an opinion about that. Needless to say I have followed up both telephonically and in writing and I can assure you that it will be taken up at a more senior level.

Will@Mweb Stop Lying to user about a Telkom problems, Mweb has the problems not telkom, it is time users stand up to you(Mweb) and take a stance against you. Mweb is gonna have a big suprise in the coming days and weeks. Things have gone to far with Mweb bul****ting users. What Mweb is doing is Fraud!!!!!!
 
Will@Mweb Stop Lying to user about a Telkom problems, Mweb has the problems not telkom, it is time users stand up to you(Mweb) and take a stance against you. Mweb is gonna have a big suprise in the coming days and weeks. Things have gone to far with Mweb bul****ting users. What Mweb is doing is Fraud!!!!!!

Nicomz - if you had actually read most (or some) of the posts here before embarrassing yourself you would have seen that this is affecting several southern suburb exchanges in CT, across all ISP's. MWEB has been doing a lot of work recently to fine tune their own network but this one is definitely Telkom's problem.
 
Will@Mweb Stop Lying to user about a Telkom problems, Mweb has the problems not telkom, it is time users stand up to you(Mweb) and take a stance against you. Mweb is gonna have a big suprise in the coming days and weeks. Things have gone to far with Mweb bul****ting users. What Mweb is doing is Fraud!!!!!!

You seriously have absolutely no idea of what you are talking about. The issue is affecting all users connecting to the affected exchanges. It is a Telkom fault, pure and simple. I take my hat off to Will@MWEB and the Webafrica team who are busy trying to get to the bottom of the issue and have it resolved.

I realize you are frustrated, believe me we all are. But being rude to someone who is really trying to help is not going to get us anywhere.
 
i changed my data account (from FNB Connect) to Telkom and i get the same bad download speeds. So it has got to be Telkom. I am in the east of Pretoria. It has been a week now that we have been suffering like this.
 
In Blouberg, Cape Town (Table View exchange). Using WebAfrica

Code:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\duaN>tracert www.webafrica.co.za

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

  1     6 ms     6 ms     6 ms  dsl-185-88-1.dynamic.wa.co.za [41.185.88.1]
  2     8 ms     8 ms     8 ms  vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
  3     8 ms     8 ms     8 ms  vl36.er.gw.cpt.za.wa.co.za [41.185.0.66]
  4     8 ms     8 ms     8 ms  vl38.cr.gw.cpt.za.wa.co.za [41.185.0.73]
  5   136 ms   134 ms   137 ms  fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
  6   169 ms   169 ms   165 ms  wa-acc1.wadns.net [196.220.39.253]
  7   154 ms   152 ms   149 ms  196.220.58.66

Trace complete.

C:\Users\duaN>tracert games.saix.net

Tracing route to games.saix.net [196.43.22.222]
over a maximum of 30 hops:

  1     7 ms     6 ms     6 ms  dsl-185-88-1.dynamic.wa.co.za [41.185.88.1]
  2     9 ms     8 ms     8 ms  vl108.cr.gw.cpt.za.wa.co.za [196.220.59.238]
  3   114 ms   205 ms     8 ms  vl35.er.gw.cpt.za.wa.co.za [41.185.0.38]
  4   126 ms   127 ms   129 ms  upstream.vl102.gw.cpt.za.wa.co.za [196.220.59.23
0]
  5   194 ms   202 ms   199 ms  rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.4
3.11.166]
  6   175 ms   179 ms   186 ms  rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
  7   189 ms   185 ms   185 ms  nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
  8   183 ms   187 ms   194 ms  nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.

C:\Users\duaN>
 
Top
Sign up to the MyBroadband newsletter
X