web africa crawling

My speed also seemed to have returned to normal (using a Titan account) and getting good <180ms to the UK. Normally by this time of day I was suffering so much packet loss that it made the account virtually unusable. So it looks like whatever was wrong has been fixed and fingers crossed it will stay this way. It would be good to get a response from WA on the root cause of this though.
 
Hi virt

That's awesome news and good to hear. :)
Just to keep everyone in the loop, we will be posting an official update here a bit later.

Thank you.
 
WAangelo said:
Hi virt

That's awesome news and good to hear. :)
Just to keep everyone in the loop, we will be posting an official update here a bit later.

Thank you.
Click to expand...

Hi Angelo,
Am seeing some improvement but still seeing high latency on the international link - do you have any published baseline figures for comparision ?

C:\Documents and Settings\mconway\Desktop>tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.246.90]
over a maximum of 30 hops:

1 3 ms 1 ms 1 ms 192.168.1.1
2 33 ms 30 ms 30 ms dsl-185-77-1.dynamic.wa.co.za [41.185.77.1]
3 58 ms 55 ms 54 ms vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
4 56 ms 54 ms 55 ms vl32.er.gw.cpt.za.wa.co.za [41.185.0.26]
5 56 ms 55 ms 54 ms upstream.vl101.gw.cpt.za.wa.co.za [196.220.59.22
6]
6 296 ms * 279 ms lon-ip-dir-telecity-pos-7-0-2.telkom-ipnet.co.za
[196.43.9.150]
7 338 ms 307 ms 306 ms 93-126-245-83.packetexchange.net [83.245.126.93]

8 265 ms 306 ms 306 ms 212.58.238.153
9 226 ms 306 ms 307 ms te12-1.hsw1.cwwtf.bbc.co.uk [212.58.239.234]
10 227 ms 306 ms 306 ms 212.58.255.12
11 296 ms 306 ms 270 ms bbc-vip011.cwwtf.bbc.co.uk [212.58.246.90]


Cheers

Mibboy
 
virt said:
My speed also seemed to have returned to normal (using a Titan account) and getting good <180ms to the UK. Normally by this time of day I was suffering so much packet loss that it made the account virtually unusable. So it looks like whatever was wrong has been fixed and fingers crossed it will stay this way. It would be good to get a response from WA on the root cause of this though.
Click to expand...

+1 working much better today!
 
Better but not great: (as it was before the shaping)

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 5 ms 5 ms 5 ms dsl-185-86-1.dynamic.wa.co.za [41.185.86.1]
3 6 ms 6 ms 12 ms vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
4 8 ms 6 ms 6 ms vl36.er.gw.cpt.za.wa.co.za [41.185.0.66]
5 7 ms 11 ms 10 ms vl38.cr.gw.cpt.za.wa.co.za [41.185.0.73]
6 15 ms 7 ms 6 ms fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
7 7 ms 19 ms 7 ms wa-acc1.wadns.net [196.220.39.253]
8 21 ms 10 ms 7 ms 196.220.58.66

Trace complete.

Tracing route to myadsl.co.za [41.203.21.137] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 5 ms 4 ms dsl-185-86-1.dynamic.wa.co.za [41.185.86.1]
3 6 ms 6 ms 6 ms vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
4 12 ms 6 ms 6 ms vl35.er.gw.cpt.za.wa.co.za [41.185.0.38]
5 7 ms 6 ms 6 ms upstream.vl102.gw.cpt.za.wa.co.za [196.220.59.230]
6 10 ms 7 ms 7 ms 196.43.11.234
7 7 ms 7 ms 8 ms 196.43.25.206
8 8 ms 9 ms 17 ms ge0-3.br2.cpt1.za.mtnbusiness.net [196.7.8.206]
9 33 ms 34 ms 34 ms ge11-0-0.gw2.jnb6.za.mtnbusiness.net [196.30.1.22]
10 30 ms 38 ms 40 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
11 32 ms 30 ms 29 ms 196.30.213.108
12 32 ms * 33 ms firewall1.jnb2.host-h.net [196.7.216.173]
13 31 ms 31 ms 29 ms mybroadband.co.za [41.203.21.137]

Trace complete.

Tracing route to solutions4it.co.za [81.95.156.42] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 5 ms 16 ms 13 ms dsl-185-86-1.dynamic.wa.co.za [41.185.86.1]
3 16 ms 6 ms 6 ms vl108.cr.gw.cpt.za.wa.co.za [196.220.59.238]
4 7 ms 6 ms 6 ms vl33.er.gw.cpt.za.wa.co.za [41.185.0.30]
5 7 ms 6 ms 6 ms upstream.vl102.gw.cpt.za.wa.co.za [196.220.59.230]
6 239 ms 239 ms 239 ms 196.43.18.134
7 240 ms 241 ms 239 ms pos2-0.cr02.ash01.pccwbtn.net [63.218.94.17]
8 239 ms 238 ms 238 ms theplanet.ge9-1.br02.ash01.pccwbtn.net [63.218.94.254]
9 250 ms 250 ms 249 ms da.ff.5746.static.theplanet.com [70.87.255.218]
10 242 ms 247 ms 241 ms 22.90.5f51.static.theplanet.com [81.95.144.34]
11 252 ms 252 ms 255 ms dolim.host4africa.com [81.95.156.42]

Trace complete.
 
Hi guys

Here is the latest update posted with regards to the current latency issue.

WAJeff said:
We have final confirmation from our Engineering team as well as Telkom that the Rondebosch exchange is congested. Other ISP’s have also mentioned this and is affected browsing around the Southern Suburbs.


Telkom have planned maintenance and the necessary bandwidth upgrades to the exchange to eliminate the congestion issues being experienced at the moment, unfortunately we have not yet been provided with an ETR on these upgrades.

To add to this, we have been and will continue to run significant network tweaks over the next two weeks to assist the issue, including expediting planned capacity upgrades - there is however no ETA on this as of yet.
We urge customers who are still experiencing poor browsing and latency issue to please send an email to [email protected] with the following information:

Client Code
ADSL Username
ADSL Password
A trace to mybroadband.co.za and one other slow website.

We will then process this information which will assist with the network tweaks as well as hopefully decrease the ETR on the Rondebosch exchange bandwidth upgrades.
Click to expand...

Thank you.
 
Better connectivity today - Angelo any idea when connectivity will normalise?


Tracing route to myadsl.co.za [41.203.21.137] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 4 ms 4 ms dsl-185-86-1.dynamic.wa.co.za [41.185.86.1]
3 11 ms 15 ms 6 ms vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
4 7 ms 6 ms 6 ms vl35.er.gw.cpt.za.wa.co.za [41.185.0.38]
5 6 ms 6 ms 6 ms upstream.vl102.gw.cpt.za.wa.co.za [196.220.59.230]
6 9 ms 6 ms 7 ms 196.43.11.234
7 8 ms 7 ms 7 ms 196.43.25.206
8 9 ms 8 ms 8 ms ge0-3.br2.cpt1.za.mtnbusiness.net [196.7.8.206]
9 28 ms 27 ms 28 ms ge11-0-0.gw2.jnb6.za.mtnbusiness.net [196.30.1.22]
10 34 ms 27 ms 27 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
11 28 ms 28 ms 27 ms 196.30.213.108
12 45 ms 27 ms 27 ms firewall1.jnb2.host-h.net [196.7.216.173]
13 28 ms 31 ms 27 ms mybroadband.co.za [41.203.21.137]


Tracing route to gam.co.za [41.0.5.47] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 4 ms 4 ms 5 ms dsl-185-86-1.dynamic.wa.co.za [41.185.86.1]
3 26 ms 8 ms 5 ms vl108.cr.gw.cpt.za.wa.co.za [196.220.59.238]
4 9 ms 6 ms 6 ms vl34.er.gw.cpt.za.wa.co.za [41.185.0.34]
5 8 ms 7 ms 6 ms upstream.vl101.gw.cpt.za.wa.co.za [196.220.59.226]
6 27 ms 27 ms 30 ms 196.43.39.18
7 34 ms 34 ms 33 ms vodacom-gw.telkom-ipnet.co.za [196.25.253.110]
8 29 ms 28 ms 29 ms 10.117.3.1
9 32 ms 28 ms 29 ms 10.117.3.1
10 35 ms 36 ms 35 ms sprintone.gam.co.za [41.0.5.47]


Tracing route to gizmag.com [174.143.45.129] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 4 ms 6 ms 16 ms dsl-185-86-1.dynamic.wa.co.za [41.185.86.1]
3 6 ms 5 ms 6 ms vl108.cr.gw.cpt.za.wa.co.za [196.220.59.238]
4 7 ms 15 ms 6 ms vl33.er.gw.cpt.za.wa.co.za [41.185.0.30]
5 7 ms 6 ms 8 ms upstream.vl102.gw.cpt.za.wa.co.za [196.220.59.230]
6 183 ms 180 ms 179 ms lon-ip-dir-telecity-pos-7-0-2.telkom-ipnet.co.za [196.43.9.150]
7 238 ms 197 ms 179 ms ldn-tch-i1-link.telia.net [213.155.141.153]
8 189 ms 189 ms 193 ms ldn-b5-link.telia.net [80.91.250.209]
9 177 ms 176 ms 181 ms ldn-bb2-link.telia.net [80.91.252.209]
10 248 ms 248 ms 248 ms ash-bb1-link.telia.net [80.91.246.66]
11 266 ms 266 ms 266 ms atl-bb1-link.telia.net [80.91.252.214]
12 291 ms 291 ms 292 ms dls-bb1-link.telia.net [80.91.246.75]
13 291 ms 288 ms 297 ms rackspace-ic-127247-dls-bb1.c.telia.net [213.248.88.174]
14 * 348 ms 407 ms core7-edge3-vlan3307.dfw1.rackspace.net [174.143.123.114]
15 292 ms 291 ms 285 ms aggr931a-1-core7.dfw1.rackspace.net [98.129.84.155]
16 353 ms 383 ms 321 ms 174.143.45.129


Tracing route to telkom.co.za [196.43.22.222] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 4 ms 5 ms 4 ms dsl-185-86-1.dynamic.wa.co.za [41.185.86.1]
3 6 ms 5 ms 6 ms vl108.cr.gw.cpt.za.wa.co.za [196.220.59.238]
4 20 ms 6 ms 11 ms vl34.er.gw.cpt.za.wa.co.za [41.185.0.34]
5 6 ms 10 ms 9 ms upstream.vl101.gw.cpt.za.wa.co.za [196.220.59.226]
6 27 ms 27 ms 26 ms rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.43.11.166]
7 27 ms 27 ms 27 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
8 40 ms 39 ms 32 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.34]
9 30 ms 39 ms 29 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]

Trace complete.
 
virt said:
My speed also seemed to have returned to normal (using a Titan account) and getting good <180ms to the UK. Normally by this time of day I was suffering so much packet loss that it made the account virtually unusable. So it looks like whatever was wrong has been fixed and fingers crossed it will stay this way. It would be good to get a response from WA on the root cause of this though.
Click to expand...

http://www.speedtest.net/result/998013452.png

4 meg line on a Titan package with WA. Seems mine is not back to "normal"...
 
Great!
Thanks for the feedback guys, nice to see some positive results cropping in :)

Please keep us updated if there are any issues or anything abnormal that occurs with speed/latency tomorrow. Fingers crossed things have patched themselves up.
 
WA connection buggered again!

Pinging myadsl.co.za [41.203.21.137] with 32 bytes of data:
Reply from 41.203.21.137: bytes=32 time=73ms TTL=51
Reply from 41.203.21.137: bytes=32 time=89ms TTL=51
Reply from 41.203.21.137: bytes=32 time=64ms TTL=51
Reply from 41.203.21.137: bytes=32 time=60ms TTL=51

Ping statistics for 41.203.21.137:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 60ms, Maximum = 89ms, Average = 71ms



Tracing route to myadsl.co.za [41.203.21.137] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 15 ms 5 ms 4 ms dsl-185-86-1.dynamic.wa.co.za [41.185.86.1]
3 15 ms 16 ms 16 ms vl108.cr.gw.cpt.za.wa.co.za [196.220.59.238]
4 44 ms 34 ms 39 ms vl35.er.gw.cpt.za.wa.co.za [41.185.0.38]
5 44 ms 46 ms 45 ms upstream.vl102.gw.cpt.za.wa.co.za [196.220.59.230]
6 8 ms 7 ms 7 ms 196.43.11.218
7 7 ms 7 ms 7 ms 196.43.25.206
8 10 ms 8 ms 8 ms ge0-3.br2.cpt1.za.mtnbusiness.net [196.7.8.206]
9 50 ms 51 ms 48 ms ge11-0-0.gw2.jnb6.za.mtnbusiness.net [196.30.1.22]
10 32 ms * 38 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
11 39 ms 39 ms 41 ms 196.30.213.108
12 34 ms 33 ms 34 ms firewall1.jnb2.host-h.net [196.7.216.173]
13 33 ms 32 ms * mybroadband.co.za [41.203.21.137]
14 38 ms * 33 ms mybroadband.co.za [41.203.21.137]

Trace complete.
 
Hi who.is.michael,

I've arranged for a DSL Consultant to contact you shortly.
 
Mine was up and down again yesterday. Early morning it was going like the proverbial Boeing, then abruptly went off the tracks. Overseas sites opened better than locals sites. Some sites like News24 pretty cruddy at times with loading, but overall there's an improvement.
 
WAJeff said:
There seems to be a noticeable decrease in latency from your post earlier on this morning. Are these results the norm or close to it, on what you usually experience?
Click to expand...

Hi WAJeff, I would say the results are norm to close to what I usually experience :D I've found that speedtest.net can vary quite bit when measuring latency (eg compared to doing a continuous ping at the same time). I guess it just depends on the exact network conditions when the test was taken.

Doing a continuous ping to the UK, latency is varying quite a bit more than usual and seem to hover between 180ms and 250ms (normally it would stay in the 180ms to 210ms range):

http://gyazo.com/714a93a72d9d47a518376dce199592f8.png

But overall, its been a huge improvement compared to the last few weeks.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X