Web Africa ADSL general feedback

Can not log into ABSA, housemate can't email her CV using a webmail site. Guess both are https.
 
My WA account is completely DEAD!!! I'm AGAIN on different ISP. What is wrong WA? You guys are up and down for more than two months now.
 
Beylie said:
Out of curiosity, why are you editing Eugene's posts?

Slow as hell here. If it wasn't for freezone, I'd leave.

EDIT

To be fair, files from a filesharing sites are coming down at 500kB/s +.
Click to expand...

Eugene's responsibility isn't primarily the forums. I edited the post to add a signature for him.

Fayera said:
My WA account is completely DEAD!!! I'm AGAIN on different ISP. What is wrong WA? You guys are up and down for more than two months now.
Click to expand...

I wouldn't say months. Agreeably, this week has been particular bad however factors have contributed to this. Hopefully issues are sorted out ASAP :)
 
WAJeff said:
I wouldn't say months. Agreeably, this week has been particular bad however factors have contributed to this. Hopefully issues are sorted out ASAP :)
Click to expand...

Jeff, this thread alone has been going for close on two months and was started because of ongoing issues. Anyway, this just highlights issues and frustrations that do not seem to be going away as we are seeing repeats of the same problem and after a while one just starts to feel despondent as it is one thing after another with the end not in sight.
 
Really getting tired of SA's best ADSL ISP delivering these bad results:



Single PC on 4Mb/s line @ 11pm.
 
Last edited:
no issues last night on my side ,

@Roadrunner Did u test with another account ?
It could be your exchange...
 
Roadrunner said:
Really getting tired of SA's best ADSL ISP delivering these bad results:



Single PC on 4Mb/s line @ 11pm.
Click to expand...

Please post up a tracert to see if we can identify any issues here.
Have you contacted support about this?
 
My wife's nagging prompted me to run a trace route for facebook:

Traceroute has started…

traceroute: Warning: facebook.com has multiple addresses; using 66.220.149.11
traceroute to facebook.com (66.220.149.11), 64 hops max, 72 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 www-10-02-snc5.facebook.com (66.220.149.11) 468.160 ms 574.766 ms 614.352 ms
 
Definitely something up with facebook, linkedin, and a couple of other sites this morning. Other sites (including international) are performing normally. Speedtest is normal too. I haven't tried any account other than my WA account.

Edit: It's intermittent though. Sometimes it's fine... Worst thing for tech support to solve, I know!!
 
Last edited:
Sadly secure sites are still not working. I play league of legends with a webafrica account cause they give me a ping of 200ms in leagueoflegends which is kinda cool. I find it unfair that I need to look around for another account with another ISP cause webafrica is not working for couple of days now in fact. sigh

League of legends seems to work fine on my IS uncapped account though. The only reason I use webafrica is cause IS shape all traffic which is not lekker for gaming.
 
Hi ... my normal browsing on WA was so bad I had to change accounts to Afrihost. This was normal browsing ... the secure sites do not work. I had to register a domain on Godaddy and it didn't work.

Normal browsing and downloading (not torrents), OS updates are crawling. It's very frustrating.

My Afrihost account on the Seacom network seems fine. It works much better.

Come on WA, what's the problem?

I will be cancelling one of my 15GB WA accounts this month ... that Telkom offer is now more appealing!!!!
Never thought I would say that!
 
I've been testing secure sites from around 10am this morning and seems to be loading OK on our test box.
Please post up some tracert results so we can try and identify where the issues are coming in here.
 
All int sites are loading super slow for me '/

local sites load fine
 
Well League of Legends login does not work at all with a webafrica account.

64.7.194.222 https

Code: 
Tracing route to 64.7.194.222 over a maximum of 30 hops

  1    13 ms    12 ms    12 ms  ndn-ip-esr-3.ipnet.wa.co.za [41.185.66.1]
  2    38 ms    37 ms    37 ms  wnls-ipc1-vl-108.wa.co.za [196.220.59.238]
  3    38 ms    38 ms    37 ms  wnls-cr1-vl-801.wa.co.za [41.185.0.67]
  4    69 ms    38 ms    38 ms  41-66-150-41-29.available.africainx.net [41.66.150.41]
  5   204 ms   221 ms   215 ms  LD-GS-MSC-M-to-CT-RO-MSC-M-SAT3-core-p2p.africainx.net [41.66.132.49]
  6   191 ms   193 ms   190 ms  195.50.122.217
  7   224 ms   188 ms   199 ms  ae-21-52.car1.London1.Level3.net [4.69.139.98]
  8   221 ms   218 ms   191 ms  xe-0-1-0-6.r02.londen03.uk.bb.gin.ntt.net [129.250.8.137]
  9   191 ms   226 ms   199 ms  ae-4.r22.londen03.uk.bb.gin.ntt.net [129.250.5.24]
 10   284 ms   273 ms   258 ms  as-0.r22.nycmny01.us.bb.gin.ntt.net [129.250.3.254]
 11   281 ms   267 ms   298 ms  ae-0.r23.nycmny01.us.bb.gin.ntt.net [129.250.3.73]
 12   291 ms   268 ms   283 ms  ae-1.r20.asbnva02.us.bb.gin.ntt.net [129.250.2.9]
 13   382 ms   338 ms   334 ms  ae-2.r21.lsanca03.us.bb.gin.ntt.net [129.250.3.55]
 14   346 ms   352 ms   349 ms  po-2.r00.lsanca17.us.bb.gin.ntt.net [129.250.5.246]
 15   339 ms   337 ms   353 ms  xe-1-3.r00.lsanca17.us.ce.gin.ntt.net [198.172.90.26]
 16   384 ms   343 ms   349 ms  border1.te1-1-bbnet1.lax010.pnap.net [216.52.255.13]
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.


It just does not log in. The connection time's out the whole time. It DOES WORK FINE with all backbones IS,SAIX and Cybersmart works fine. Then I dial a pppoe connection with webafrica and try to log in and it fails the whole time connection time out.
 
Next month i seriously have to look at alternative internet arrangements I have been blaming ABSA lately for sh|tty internet banking performance, but I seriously think it has partly to do with WA performance
 
Code: 
Traceroute has started…

traceroute: Warning: facebook.com has multiple addresses; using 66.220.149.11
traceroute to facebook.com (66.220.149.11), 64 hops max, 72 byte packets
 1  * * *
 2  wnls-ipc1-vl-108.wa.co.za (196.220.59.238)  29.980 ms  29.108 ms  26.906 ms
 3  wnls-cr2-vl-801.wa.co.za (41.185.0.66)  33.687 ms  34.206 ms  35.610 ms
 4  41-66-150-177-b1.available.africainx.net (41.66.150.177)  37.246 ms  35.033 ms  34.786 ms
 5  ld-gs-msc-m-to-ct-ro-msc-m-sat3-core-p2p.africainx.net (41.66.132.49)  207.154 ms  255.172 ms  181.020 ms
 6  linx.br02.lhr1.tfbnw.net (195.66.225.121)  180.002 ms  181.272 ms  188.256 ms
 7  ae18.bb02.iad2.tfbnw.net (74.119.79.202)  496.215 ms  306.763 ms  307.162 ms
 8  ae11.bb02.pao1.tfbnw.net (74.119.77.252)  614.258 ms  613.795 ms  614.246 ms
 9  ae1.dr01.snc5.tfbnw.net (74.119.77.182)  614.706 ms  667.062 ms  560.837 ms
10  po510.csw02a.snc5.tfbnw.net (74.119.78.22)  614.293 ms  617.476 ms  610.841 ms
11  www-10-02-snc5.facebook.com (66.220.149.11)  614.270 ms  613.910 ms  614.659 ms
 
WAJeff said:
I've been testing secure sites from around 10am this morning and seems to be loading OK on our test box.
Please post up some tracert results so we can try and identify where the issues are coming in here.
Click to expand...

Is your "test box" on a completely separate ADSL tel line to simulate the end-users experience? No point testing this if you're sitting directly on the WA network.

I'm experiencing the exact same problems since yesterday and day before on WA. During the day I can barely load https sites, they're either very slow or simply time out. I have difficulty signing in to MSN/Windows Live Messenger. It times out. I (sometimes) can't reply to tweets on Twitter, it times out. Regular browsing to non-secure sites is not that bad but still slower than what I'm used to.
When I switch to Afrihost everything I mentioned above, works 100%.

Note that I only experience these issues during business hours! Performance on WA is 100% fine (for me) after 5pm, every day. Why the miraculous turnaround in performance from 4pm (dead) to 6pm (normal) ? Surely all the outages mentioned on the WA Status page would still apply, regardless of time of day. Traffic management software shaping rules appear to be too aggressively applied during the day... what else could be the explanation for such a quick turnaround in performance every single day? But nobody at WA reponds to this sort of comment nor do anyone investigate the probability of this being an issue, or at least nobody has provided feedback on it. I just get the usual "We're having problems, bear with us" replies from WA support when a ticket is logged. Yet I crawl during day and fly from about 5/6pm onwards. I have zero issues in the evening.

I think it's ironic that everything works on Afrihost, yet it's ISP's like them who were affected by the SEACOM outage in the first place, then they presumably organised bandwidth on SAT3 and now they're still performing OK. Yet WA who is not even on SEACOM are currently struggling more and WA has been using SAT3 from the start. <shakes head>

Every day I'm forced to switch to my backup Afrihost acc due to this non-performance on WA during business hours and after hours I'm back on WA at fullspeed.

I just looked at the WA status page and the "connectivity to secure sites" issue has been marked as resolved. Yet, I'm still struggling on https sites at the time of writing. Facebook.com is set to https and times out for me. Can't load it at all. The site flies when I switch to Afrihost so I'm not sure about the status of these issues either.

Here's a few traceroutes:

C:\Users\user1>tracert facebook.com

Tracing route to facebook.com [66.220.149.11]
over a maximum of 30 hops:

1 3 ms 1 ms <1 ms 192.168.0.1
2 24 ms 25 ms 22 ms wblv-ip-esr-3.ipnet.wa.co.za [41.185.83.1]
3 35 ms 35 ms 25 ms wnls-ipc1-vl-105.wa.co.za [196.220.59.250]
4 28 ms 24 ms 26 ms wnls-cr2-vl-801.wa.co.za [41.185.0.66]
5 67 ms 38 ms 39 ms 41-66-150-177-b1.available.africainx.net [41.66.
150.177]
6 182 ms 300 ms 198 ms LD-GS-MSC-M-to-CT-RO-MSC-M-SAT3-core-p2p.africai
nx.net [41.66.132.49]
7 182 ms 178 ms 179 ms linx.br02.lhr1.tfbnw.net [195.66.225.121]
8 310 ms 284 ms 270 ms ae19.bb02.iad1.tfbnw.net [74.119.76.142]
9 357 ms 350 ms 349 ms ae13.bb02.pao1.tfbnw.net [74.119.78.186]
10 335 ms 333 ms 341 ms ae1.dr01.snc5.tfbnw.net [74.119.77.182]
11 339 ms 350 ms 350 ms po510.csw02a.snc5.tfbnw.net [74.119.78.22]
12 357 ms 345 ms 345 ms www-10-02-snc5.facebook.com [66.220.149.11]

Trace complete.

C:\Users\user1>tracert twitter.com

Tracing route to twitter.com [199.59.148.82]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.0.1
2 26 ms 22 ms 22 ms wblv-ip-esr-3.ipnet.wa.co.za [41.185.83.1]
3 29 ms 25 ms 27 ms wnls-ipc1-vl-108.wa.co.za [196.220.59.238]
4 27 ms 26 ms 24 ms wnls-cr1-vl-801.wa.co.za [41.185.0.67]
5 42 ms 27 ms 52 ms 41-66-150-41-29.available.africainx.net [41.66.1
50.41]
6 181 ms 178 ms 206 ms LD-GS-MSC-M-to-CT-RO-MSC-M-SAT3-core-p2p.africai
nx.net [41.66.132.49]
7 197 ms 186 ms 196 ms 195.50.122.217
8 223 ms 240 ms 181 ms ae-52-52.csw2.London1.Level3.net [4.69.139.120]

9 192 ms 180 ms 178 ms ae-58-223.ebr2.London1.Level3.net [4.69.153.137]

10 247 ms 246 ms 247 ms ae-43-43.ebr1.NewYork1.Level3.net [4.69.137.74]

11 250 ms 251 ms 250 ms ae-10-10.ebr2.Washington12.Level3.net [4.69.148.
50]
12 279 ms 251 ms 252 ms ae-5-5.ebr2.Washington1.Level3.net [4.69.143.221
]
13 263 ms 257 ms 252 ms ae-82-82.csw3.Washington1.Level3.net [4.69.134.1
54]
14 254 ms 253 ms 254 ms ae-3-80.edge2.Washington4.Level3.net [4.69.149.1
44]
15 261 ms 252 ms 251 ms TWITTER-INC.edge2.Washington4.Level3.net [4.53.1
14.102]
16 353 ms 338 ms 330 ms 199.16.159.46
17 351 ms 401 ms 383 ms 199.16.159.49
18 328 ms 328 ms 328 ms r-199-59-148-82.twttr.com [199.59.148.82]

Trace complete.

C:\Users\user1>ping facebook.com

Pinging facebook.com [66.220.149.11] with 32 bytes of data:
Reply from 66.220.149.11: bytes=32 time=351ms TTL=243
Reply from 66.220.149.11: bytes=32 time=369ms TTL=243
Reply from 66.220.149.11: bytes=32 time=345ms TTL=243
Reply from 66.220.149.11: bytes=32 time=347ms TTL=243

Ping statistics for 66.220.149.11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 345ms, Maximum = 369ms, Average = 353ms
Click to expand...
 
Have to say I am so tired of hassles and issues not been dealt with and resolved. Right now I do not have the energy to try trace routes etc - I just wish we could get a normal, decent service that is reliable.

Really good points have been raised above and most likely will never be answered.

Sorry to be negative - after awhile one gets worn down, and that is how I feel now
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X