Jase
Executive Member
DL+ was terrible last night. The torrent I was d/loading struggled to hit 30kB/s. That same torrent is now cruising at around 300-350.
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Still absolutely horrible speeds and latency and I'm not even close to being shaped. Only used about 7gigs for the month...
Considering changing ISP at this point.
I would strongly advise against anyone considering WebAfrica as their uncapped ISP. Its definitely the most unreliable internet connection I've ever used.
Maybe there is something else wrong with your line. No problems for me with downloads, perfect lat on WoW.
Anyone else still having issues with Web Africa Uncapped. Its been super slow the whole day. I've tried everything. Router restart, telkom support etc etc. Getting horrible latency and DL speeds.
Here is the speedtest and tracert to www.google.co.za:
![]()
![]()
As you can see the speeds are horrible considering i have a 4meg uncapped line and account. It been going on like this the whole week.
OK guys, I've been told that some changes have been made. What is browsing looking like for now?
Another user also mentioned it in an earlier post that he got 700Mb+ in 1 hour for a 1Mb line.
I saw on the 7th Jan my usage
03:00 - 04:00 760 895 153 bytes 725.65 MB
This cant be possible on 1Mb line. So the reliability of WA monitoring software is questionable
Our developers have managed to look into this and can confirm all to be in order with the spikes included in our initial response.
This being said, we can confirm that our usage tracker is accurately working.
Tracing route to 159.153.92.41 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 23 ms 20 ms 21 ms esdw-ip-esr-3.ipnet.wa.co.za [41.185.64.1]
3 31 ms 35 ms 31 ms wnls-ipc1-vl-108.wa.co.za [196.220.59.238]
4 32 ms 31 ms 31 ms wnls-cr2-vl-801.wa.co.za [41.185.0.66]
5 39 ms 87 ms 41 ms 41.185.1.49
6 32 ms 62 ms 48 ms 41-66-150-177-b1.available.africainx.net [41.66.
150.177]
7 208 ms 184 ms 183 ms 41-84-12-87-57.available.africainx.net [41.84.12
.87]
8 214 ms 181 ms 181 ms 195.50.122.217
9 182 ms 220 ms 187 ms ae-12-51.car2.London1.Level3.net [4.69.139.67]
10 182 ms 182 ms 181 ms xe-3-2-0.mpr1.lhr1.uk.above.net [64.125.14.17]
11 214 ms 191 ms 190 ms xe-0-0-0.mpr2.lhr3.uk.above.net [64.125.27.162]
12 190 ms 218 ms 190 ms ge-5-1-0.mpr1.lhr3.uk.above.net [64.125.28.94]
13 281 ms 259 ms 267 ms xe-4-3-0.cr2.dca2.us.above.net [64.125.24.41]
14 290 ms 266 ms 265 ms xe-0-0-0.cr1.dca2.us.above.net [64.125.28.241]
15 299 ms 264 ms 266 ms xe-1-0-1.er1.iad10.us.above.net [64.125.26.238]
16 311 ms 260 ms 259 ms 64.125.199.186.t00673-01.above.net [64.125.199.1
86]
17 301 ms 273 ms 265 ms 159.153.92.82
18 259 ms 258 ms 259 ms 159.153.92.41
Trace complete.
ping 159.153.92.41 -n 30
Pinging 159.153.92.41 with 32 bytes of data:
Reply from 159.153.92.41: bytes=32 time=290ms TTL=233
Reply from 159.153.92.41: bytes=32 time=259ms TTL=233
Reply from 159.153.92.41: bytes=32 time=259ms TTL=233
Reply from 159.153.92.41: bytes=32 time=258ms TTL=233
Reply from 159.153.92.41: bytes=32 time=259ms TTL=233
Reply from 159.153.92.41: bytes=32 time=258ms TTL=233
Reply from 159.153.92.41: bytes=32 time=259ms TTL=233
Reply from 159.153.92.41: bytes=32 time=259ms TTL=233
Reply from 159.153.92.41: bytes=32 time=260ms TTL=233
Reply from 159.153.92.41: bytes=32 time=258ms TTL=233
Reply from 159.153.92.41: bytes=32 time=258ms TTL=233
Reply from 159.153.92.41: bytes=32 time=260ms TTL=233
Reply from 159.153.92.41: bytes=32 time=258ms TTL=233
Reply from 159.153.92.41: bytes=32 time=259ms TTL=233
Reply from 159.153.92.41: bytes=32 time=258ms TTL=233
Reply from 159.153.92.41: bytes=32 time=259ms TTL=233
Reply from 159.153.92.41: bytes=32 time=258ms TTL=233
Reply from 159.153.92.41: bytes=32 time=259ms TTL=233
Reply from 159.153.92.41: bytes=32 time=258ms TTL=233
Reply from 159.153.92.41: bytes=32 time=259ms TTL=233
Reply from 159.153.92.41: bytes=32 time=259ms TTL=233
Reply from 159.153.92.41: bytes=32 time=262ms TTL=233
Reply from 159.153.92.41: bytes=32 time=258ms TTL=233
Reply from 159.153.92.41: bytes=32 time=261ms TTL=233
Reply from 159.153.92.41: bytes=32 time=259ms TTL=233
Reply from 159.153.92.41: bytes=32 time=262ms TTL=233
Reply from 159.153.92.41: bytes=32 time=261ms TTL=233
Reply from 159.153.92.41: bytes=32 time=263ms TTL=233
Reply from 159.153.92.41: bytes=32 time=259ms TTL=233
Reply from 159.153.92.41: bytes=32 time=260ms TTL=233
Ping statistics for 159.153.92.41:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 258ms, Maximum = 290ms, Average = 260ms
Hi guys,
I am currently on a wireless package, but looking to move back to dsl where (under normal circumstance) the latency is excellent and jitter is near zero. I play local FPS and download +-200gb/m
Can you guys reccomend WA? I will be going to them with line and bandwidth, so I want to make sure I'm going to experience the best possible service based on what I've read on the KB.
Thanks in advance!
In short, No.Hi guys,
I am currently on a wireless package, but looking to move back to dsl where (under normal circumstance) the latency is excellent and jitter is near zero. I play local FPS and download +-200gb/m
Can you guys reccomend WA? I will be going to them with line and bandwidth, so I want to make sure I'm going to experience the best possible service based on what I've read on the KB.
Thanks in advance!
Did some testing last nite, from midnite to 8am. Monitored my traffic, uTorrent says 2.15GB downloaded and the WA usage panel says 2.48 GB.the uploaded shows the same number at least
It could have been anything updating on your pc - rather use a program which monitors all your connections and not just your torrents, like netlimiter or something.