Web Africa ADSL general feedback

Morning all,

The guys who have had issues last night on International - did anyone contact our ADSL guys for a better check? Networking graphs aren't showing any issues that I can see.

For the news server, my query that I logged with our Engineers is still pending. Will hopefully have an answer for everyone later today.

I logged a support query last night (and the night before) about bad speeds on the low priority ports (although technically priority should be all the same if you're in threshold according to what I've seen) round about 7-10pm (I havnt gone out of my threshold in 3 days), weekend and friday were fine but monday things changed. News was 25-50kb/s and dropbox sync was like 0.5kb/s, http was full speed though. Unfortunately I could only give the traceroutes after everything had come back to normal.

The only issue the support guy saw was on hop 2 8 ms 23 ms 12 ms ndnn-ip-esr-2.ipnet.wa.co.za [41.185.67.1]

Durban here if anything makes a difference
 
Anyone else battling with speeds? I am downloading and lucking to be getting much above 100 kbps on a 6 meg line. Not too sure if this is a new server issue / overload due to last day of month / uncapped. Oh well?
 
Been running fine for the last 24hours, very nice speed and latency. Until now .. 8:50pm server ping in the high 45000 ms ... eish yes 45 thousand !!! switched to Afrihost and back to 400 odd which is not bad for some TM servers. So Webafrica just not working for me again.
 
Speeds on telkom news servers are fine but WA iam lucky to get over 60kB/s, been like this for a week now.......i give up WA :(

Need some Advice, If i cancel WA do i need to phone telkom and have my line moved back to them first or can i just cancel WA and it will be moved automaticly back to telkom?

Dont want to cancel and a month later have no connectivity
 
My DL's are even slower now. Had no response from WA support bar the automated email reply, so that is not great. (About 2 1/2 hours ago)

Guess I will not be using my cap this month :(
 
I've managed to get 2Kb/s on WA's news server today. Much better than the 0Kb/s I got the other day :p
 
You'll have to butter me up way more than that first :p

Are you able to access those links?

Specifically the support one (since it's the one that has the problems).

Yup, no problems loading them from my side via my WA account.
 
Had no issues last night, still getting full speed on downloads (not using the WA newsserver though) and still getting < 200ms on WoW.
 
Also had very slow speed on the WA news server last night during DL+ hours. Not impressed so far.
 
Trying to download a 70 MB backup of our web site from the US over FTP at 5 KB/s - 3 hours to go! Wtf!
 
Current download speed: 38k on my 4mb line. I hope there's a fault on the network somewhere!

EDIT: No, it looks like 40k is my current throttled limit for downloads. I guess those 4gig I managed to squeeze in yesterday pushed me over the limit for December.
 
Last edited:
Current download speed: 38k on my 4mb line. I hope there's a fault on the network somewhere!

EDIT: No, it looks like 40k is my current throttled limit for downloads. I guess those 4gig I managed to squeeze in yesterday pushed me over the limit for December.

From what WA has told me they are looking at the network and the news server. Last night, after 9 I tested the news server and was getting well over 600K, so going max. This morning it was up and down, but lucky if I was averaging 200k.

With me, one of the biggest pluses of WA is their news server and (not recently) the fact that in DL+ times I could normally get a consistent max speeds. I guess uncapped is also playing a part, and hopefully will get addressed so that this does not become a sub par service that one can only manage to get a partial benefit from
 
Also on a WA RedAfrica account, 1Mb line and in the Pretoria area. Also having intermittent problems. Slow, fast, dead, time-outs. Thought it was the cat on the modem, but no problems there.

Repeated some of the traces mentioned above, and get results ranging from good to bad:


Tracing route to www.webafrica.com [196.220.58.66]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms tikal [192.168.1.254]
2 202 ms 220 ms 203 ms tpr-ip-esr-5.ipnet.wa.co.za [41.185.80.1]
3 * * 35 ms wnls-ipc1-vl-105.wa.co.za [196.220.59.250]
4 269 ms 316 ms 287 ms wnls-cr1-vl-801.wa.co.za [41.185.0.67]
5 227 ms 40 ms 78 ms wnls-hr2-gi-8-13.wa.co.za [41.185.1.34]
6 130 ms 134 ms 256 ms 196.220.58.66
Trace complete.

Tracing route to www.l.google.com [74.125.233.19]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms tikal [192.168.1.254]
2 53 ms 397 ms 315 ms tpr-ip-esr-5.ipnet.wa.co.za [41.185.80.1]
3 363 ms 127 ms 268 ms wnls-ipc1-vl-105.wa.co.za [196.220.59.250]
4 206 ms 210 ms 271 ms wnls-cr2-vl-801.wa.co.za [41.185.0.66]
5 373 ms 228 ms 249 ms wbrs-csw1-vl-140.wa.co.za [41.185.1.5]
6 357 ms 267 ms 326 ms google.cinx.net.za [196.223.22.41]
7 343 ms 245 ms 237 ms 64.233.174.105
8 229 ms 174 ms 218 ms cpt01s01-in-f19.1e100.net [74.125.233.19]
Trace complete.

Tracing route to www.nytimes.com [199.239.136.200]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms tikal [192.168.1.254]
2 * 2694 ms 50 ms tpr-ip-esr-5.ipnet.wa.co.za [41.185.80.1]
3 35 ms 35 ms 81 ms wnls-ipc1-vl-105.wa.co.za [196.220.59.250]
4 253 ms 211 ms 218 ms wnls-cr2-vl-801.wa.co.za [41.185.0.66]
5 150 ms 158 ms 273 ms 41-66-150-177-b1.available.africainx.net [41.66.150.177]
6 326 ms 386 ms 342 ms LD-GS-MSC-M-to-CT-RO-MSC-M-SAT3-core-p2p.africainx.net [41.66.132.49]
7 505 ms 431 ms 247 ms 195.50.122.217
8 * 292 ms 346 ms ae-21-52.car1.London1.Level3.net [4.69.139.98]
9 413 ms 544 ms 398 ms xe-0-1-0-6.r02.londen03.uk.bb.gin.ntt.net [129.250.8.137]
10 419 ms 352 ms 434 ms ae-4.r22.londen03.uk.bb.gin.ntt.net [129.250.5.24]
11 405 ms 432 ms 336 ms as-0.r22.nycmny01.us.bb.gin.ntt.net [129.250.3.254]
12 364 ms 392 ms 523 ms ae-2.r05.nycmny01.us.bb.gin.ntt.net [129.250.4.173]
13 536 ms 499 ms 341 ms ge-1-1.a01.nycmny01.us.da.verio.net [129.250.30.114]
14 * * * Request timed out.
rince repeat
etc
30 * * * Request timed out.
Trace complete.
 
Also on a WA RedAfrica account, 1Mb line and in the Pretoria area. Also having intermittent problems. Slow, fast, dead, time-outs. Thought it was the cat on the modem, but no problems there.

Repeated some of the traces mentioned above, and get results ranging from good to bad:


Tracing route to www.webafrica.com [196.220.58.66]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms tikal [192.168.1.254]
2 202 ms 220 ms 203 ms tpr-ip-esr-5.ipnet.wa.co.za [41.185.80.1]
3 * * 35 ms wnls-ipc1-vl-105.wa.co.za [196.220.59.250]
4 269 ms 316 ms 287 ms wnls-cr1-vl-801.wa.co.za [41.185.0.67]
5 227 ms 40 ms 78 ms wnls-hr2-gi-8-13.wa.co.za [41.185.1.34]
6 130 ms 134 ms 256 ms 196.220.58.66
Trace complete.

Tracing route to www.l.google.com [74.125.233.19]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms tikal [192.168.1.254]
2 53 ms 397 ms 315 ms tpr-ip-esr-5.ipnet.wa.co.za [41.185.80.1]
3 363 ms 127 ms 268 ms wnls-ipc1-vl-105.wa.co.za [196.220.59.250]
4 206 ms 210 ms 271 ms wnls-cr2-vl-801.wa.co.za [41.185.0.66]
5 373 ms 228 ms 249 ms wbrs-csw1-vl-140.wa.co.za [41.185.1.5]
6 357 ms 267 ms 326 ms google.cinx.net.za [196.223.22.41]
7 343 ms 245 ms 237 ms 64.233.174.105
8 229 ms 174 ms 218 ms cpt01s01-in-f19.1e100.net [74.125.233.19]
Trace complete.

Tracing route to www.nytimes.com [199.239.136.200]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms tikal [192.168.1.254]
2 * 2694 ms 50 ms tpr-ip-esr-5.ipnet.wa.co.za [41.185.80.1]
3 35 ms 35 ms 81 ms wnls-ipc1-vl-105.wa.co.za [196.220.59.250]
4 253 ms 211 ms 218 ms wnls-cr2-vl-801.wa.co.za [41.185.0.66]
5 150 ms 158 ms 273 ms 41-66-150-177-b1.available.africainx.net [41.66.150.177]
6 326 ms 386 ms 342 ms LD-GS-MSC-M-to-CT-RO-MSC-M-SAT3-core-p2p.africainx.net [41.66.132.49]
7 505 ms 431 ms 247 ms 195.50.122.217
8 * 292 ms 346 ms ae-21-52.car1.London1.Level3.net [4.69.139.98]
9 413 ms 544 ms 398 ms xe-0-1-0-6.r02.londen03.uk.bb.gin.ntt.net [129.250.8.137]
10 419 ms 352 ms 434 ms ae-4.r22.londen03.uk.bb.gin.ntt.net [129.250.5.24]
11 405 ms 432 ms 336 ms as-0.r22.nycmny01.us.bb.gin.ntt.net [129.250.3.254]
12 364 ms 392 ms 523 ms ae-2.r05.nycmny01.us.bb.gin.ntt.net [129.250.4.173]
13 536 ms 499 ms 341 ms ge-1-1.a01.nycmny01.us.da.verio.net [129.250.30.114]
14 * * * Request timed out.
rince repeat
etc
30 * * * Request timed out.
Trace complete.

Your problems look like it starts on the 1st hop, so either a congested DSLAM, or one that is on it's way to a congested DSLAM, or you are busy downloading at max line speed.
 
Hmm, been having a good time. About 5 hours without timeouts. and then the dreaded 'no connection' ggrrr enough to kick me off my gaming server.. back to telkom account I guess :)
 
Last edited:
Top
Sign up to the MyBroadband newsletter
X