web africa crawling

WAJeff said:
Looking a lot better who.is.michael!
What do your international results look like this morning?
Click to expand...

Hi Jeff

Yes, thank you – much better, however a few issues still persist.

Noticed odd throughput (speed) fluctuations (local network idle) - could possibly be due to shaping or that it is end of month rush to utilise all remaining bandwidth?

Also international websites (USA /UK) that makes intense use of images does not load completely, with some smaller images missing.

Also, browsing is not as snappy as it was in the past, with a second or two delay in loading once the domain name has been resolved.

Also experiencing corrupted downloads.

Lastly you might want to investigate; IP 196.220.59.238 as packet loss is currently occurring at this IP address and IP 41.185.0.26 is behaving erratically with RTT fluctuating from 6 ms to 204 ms.

Hope this helps

Regards

M

Speedtest.net
41.185.124.XXX 10/22/2010 6:50 AM GMT 7.92 0.77 12 Newlands
41.185.124.XXX 10/31/2010 11:34 AM GMT 8.44 0.72 9 Cape Town
41.185.124.XXX 10/31/2010 11:40 AM GMT 8.45 0.66 195 London 6000
41.185.124.XXX 10/31/2010 11:48 AM GMT 8.29 0.64 244 New York, NY
41.185.124.XXX 10/31/2010 12:05 PM GMT 8.28 0.56 188 Paris
41.185.124.XXX 10/31/2010 12:07 PM GMT 8.26 0.57 234 Istanbul
41.185.124.XXX 10/31/2010 12:13 PM GMT 8.24 0.6 198 Frankfurt
41.185.124.XXX 10/31/2010 12:16 PM GMT 8.27 0.52 182 Rotterdam



Ping statistics for 70.87.6.117:
Packets: Sent = 2091, Received = 2089, Lost = 2 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 265ms, Maximum = 485ms, Average = 270ms


Tracing route to teamviewer.com [87.230.73.24] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 5 ms 4 ms 5 ms wbs-ip-esr-4.ipnet.wa.co.za [41.185.86.1]
3 7 ms 6 ms 6 ms vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
4 6 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 168 ms 168 ms 167 ms 196.43.9.54
7 187 ms 211 ms 200 ms ge-6-2-903.car5.London1.Level3.net [212.113.10.69]
8 194 ms 188 ms 187 ms ae-34-52.ebr2.London1.Level3.net [4.69.139.97]
9 177 ms 176 ms 177 ms ae-47-47.ebr2.Amsterdam1.Level3.net [4.69.143.77]
10 189 ms 188 ms 188 ms ae-1-100.ebr1.Amsterdam1.Level3.net [4.69.141.169]
11 191 ms 191 ms 191 ms ae-45-45.ebr2.Dusseldorf1.Level3.net [4.69.143.198]
12 182 ms 181 ms 181 ms ae-21-52.car1.Dusseldorf1.Level3.net [4.69.139.34]
13 * * * Request timed out.
14 193 ms 193 ms 194 ms www.teamviewer.com [87.230.73.24]

Trace complete.


Tracing route to theplanet.com [70.87.6.117] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 4 ms 4 ms 4 ms wbs-ip-esr-4.ipnet.wa.co.za [41.185.86.1]
3 7 ms 6 ms 6 ms vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
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 235 ms 235 ms 235 ms ash-ip-dir-equinix-pos-4-0.telkom-ipnet.co.za [196.43.18.30]
7 235 ms 244 ms 236 ms pos2-0.cr02.ash01.pccwbtn.net [63.218.94.17]
8 234 ms 233 ms 233 ms theplanet.ge9-1.br02.ash01.pccwbtn.net [63.218.94.254]
9 267 ms 267 ms 267 ms bd.fd.5746.static.theplanet.com [70.87.253.189]
10 269 ms 268 ms 268 ms te3-5.dsr02.dllstx3.theplanet.com [70.87.253.90]
11 268 ms 268 ms 268 ms 82.ff.5746.static.theplanet.com [70.87.255.130]
12 267 ms 266 ms 266 ms theplanet.com [70.87.6.117]

Trace complete.

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 5 ms 5 ms 4 ms wbs-ip-esr-4.ipnet.wa.co.za [41.185.86.1]
3 6 ms 6 ms 6 ms vl108.cr.gw.cpt.za.wa.co.za [196.220.59.238]
4 7 ms 7 ms 6 ms vl34.er.gw.cpt.za.wa.co.za [41.185.0.34]
5 6 ms 6 ms 6 ms upstream.vl101.gw.cpt.za.wa.co.za [196.220.59.226]
6 7 ms 7 ms 7 ms wblv-ip-essr-1-atm-2-0-0-1.telkom-ipnet.co.za [196.43.11.22]
7 7 ms 7 ms 7 ms wblv-ip-www-1.saix.net [196.25.1.200]

Trace complete.

Tracing route to dyndns.com [204.13.248.117] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 5 ms 4 ms 4 ms wbs-ip-esr-4.ipnet.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 7 ms 6 ms 6 ms vl33.er.gw.cpt.za.wa.co.za [41.185.0.30]
5 6 ms 6 ms 6 ms upstream.vl102.gw.cpt.za.wa.co.za [196.220.59.230]
6 179 ms 180 ms 179 ms lon-ip-dir-telecity-pos-1-1-0.telkom-ipnet.co.za [196.43.9.50]
7 176 ms 168 ms 168 ms gi4-8.ccr01.lon05.atlas.cogentco.com [149.6.2.193]
8 181 ms 179 ms 179 ms te4-7.mpd01.lon01.atlas.cogentco.com [130.117.49.93]
9 180 ms 180 ms 179 ms te3-2.ccr01.lon01.atlas.cogentco.com [130.117.1.73]
10 241 ms 241 ms 241 ms te0-0-0-1.ccr21.jfk02.atlas.cogentco.com [130.117.0.46]
11 240 ms 239 ms 239 ms te4-2.ccr01.jfk08.atlas.cogentco.com [154.54.27.214]
12 260 ms 260 ms 259 ms 38.104.190.54
13 259 ms 259 ms 260 ms dyndns.com [204.13.248.117]

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 5 ms 4 ms 5 ms wbs-ip-esr-4.ipnet.wa.co.za [41.185.86.1]
3 6 ms 6 ms 6 ms vl108.cr.gw.cpt.za.wa.co.za [196.220.59.238]
4 7 ms 6 ms 6 ms vl34.er.gw.cpt.za.wa.co.za [41.185.0.34]
5 7 ms 6 ms 6 ms upstream.vl101.gw.cpt.za.wa.co.za [196.220.59.226]
6 8 ms 7 ms 7 ms 196.43.11.234
7 7 ms 7 ms 9 ms 196.43.25.206
8 9 ms 7 ms 9 ms ge0-3.br2.cpt1.za.mtnbusiness.net [196.7.8.206]
9 30 ms 30 ms 42 ms 196.30.1.21
10 30 ms 29 ms 29 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
11 28 ms 27 ms 61 ms 196.30.213.108
12 29 ms 30 ms 29 ms firewall1.jnb2.host-h.net [196.7.216.173]
13 29 ms 29 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 4 ms 4 ms 4 ms wbs-ip-esr-4.ipnet.wa.co.za [41.185.86.1]
3 6 ms 6 ms 5 ms vl108.cr.gw.cpt.za.wa.co.za [196.220.59.238]
4 6 ms 6 ms 6 ms vl32.er.gw.cpt.za.wa.co.za [41.185.0.26]
5 7 ms 6 ms 7 ms upstream.vl101.gw.cpt.za.wa.co.za [196.220.59.226]
6 235 ms 234 ms 235 ms ash-ip-dir-equinix-pos-4-0.telkom-ipnet.co.za [196.43.18.30]
7 236 ms 236 ms 235 ms pos2-0.cr02.ash01.pccwbtn.net [63.218.94.17]
8 234 ms 233 ms 233 ms theplanet.ge9-1.br02.ash01.pccwbtn.net [63.218.94.254]
9 253 ms 250 ms 249 ms da.ff.5746.static.theplanet.com [70.87.255.218]
10 239 ms 239 ms 239 ms 22.90.5f51.static.theplanet.com [81.95.144.34]
11 251 ms 250 ms 250 ms dolim.host4africa.com [81.95.156.42]

Trace complete.
 
Heya Michael,

Thanks for the info provided here! As mentioned in my PM, I'll have this forwarded to the engineers asap.
Please look forward to a conclusive, hopefully final, update on this issue sometime tomorrow.
 
Morning guys,

Please see update below:

waServerStatus said:
With regards to the increased latency and Packet Loss experienced by our ADSL customers, please see our updated response below:

1. The packet Loss and congestion on the Telkom ADSL Exchanges, specifically in the Southern Suburbs and Cape Town Areas seem to have been resolved by Telkom: If you feel that this is not the case please let us know - so that we can follow up and get the issue resolved.

2. The increased levels of traffic traversing our network, have been addressed with the planned upgrades being brought forward, and finally implemented. We will be monitoring these capacities over the next few weeks, and adding additional capacity if required.

3. The Latency specifically being experienced by our gaming customers will be receiving our utmost attention over the next few days, we are working closely with Vendors to get our traffic management system to correctly match the new gaming protocols, therefore allowing them to be correctly prioritised, improving the traffic flows and therefore your gaming experience.

If anyone is still experiencing issues please contact support, forwarding any supporting documentation as this will help our support staff during the investigation and resolution process.
This should include:

* Telephone number

* DSL Username

* Either an in-game or cmd traceroute to a slow website


Thank you to everyone who has given their feedback, as always, it is extremely
useful.

We will continue to provide information as we progress.
Click to expand...
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X