web africa crawling

Just get back home at around 21.45 - can barely browse - everthing's timing out. Swop to Afrihost and it's all good.

Trace routes from both about a minute apart, WebAfrica first, Afrihost second:

WebAfrica
Tracing route to mybroadband.co.za [41.203.21.137]

over a maximum of 30 hops:

1 1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 7 ms 7 ms 7 ms wbs-ip-esr-4.ipnet.wa.co.za [41.185.86.1]
3 * 610 ms 600 ms vl108.cr.gw.cpt.za.wa.co.za [196.220.59.238]
4 619 ms 626 ms 580 ms vl34.er.gw.cpt.za.wa.co.za [41.185.0.34]
5 1142 ms 1082 ms 1060 ms upstream.vl101.gw.cpt.za.wa.co.za [196.220.59.226]
6 1154 ms 1078 ms 1017 ms 196.43.11.234
7 1058 ms 1062 ms 1138 ms 196.43.25.206
8 1103 ms 1076 ms 1082 ms ge0-3.br2.cpt1.za.mtnbusiness.net [196.7.8.206]
9 1051 ms * 1031 ms 196.30.1.21
10 1125 ms 1096 ms 1085 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
11 1082 ms 1195 ms 1198 ms 196.30.213.108
12 407 ms 385 ms 543 ms firewall1.jnb2.host-h.net [196.7.216.173]
13 1184 ms 1261 ms 1246 ms mybroadband.co.za [41.203.21.137]

Trace complete.

Afrihost
Tracing route to mybroadband.co.za [41.203.21.137]

over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 7 ms 7 ms 6 ms 196-210-150-1.dynamic.isadsl.co.za [196.210.150.1]
3 31 ms 30 ms 30 ms cdsl1-rba-vl2460.ip.isnet.net [196.38.72.217]
4 33 ms 32 ms 32 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
5 31 ms 30 ms 31 ms 168.209.1.139
6 34 ms 30 ms 29 ms 168.209.1.179
7 36 ms 29 ms 28 ms ge0-1.br1.jnb7.za.mtnbusiness.net [196.30.228.241]
8 29 ms 29 ms 28 ms ge0-1.cr1.jnb7.za.mtnbusiness.net [196.30.228.122]
9 31 ms 30 ms 29 ms 196.30.1.21
10 30 ms 30 ms 30 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
11 32 ms 32 ms 32 ms 196.30.213.108
12 30 ms 31 ms 29 ms firewall1.jnb2.host-h.net [196.7.216.173]
13 30 ms 30 ms 30 ms mybroadband.co.za [41.203.21.137]

Trace complete.

Eww. I've recommended loads of people to WebAfrica - I'm just embarrassed now.
 
Last edited:
Although I had to swap out my account, it does look like connectivity has picked up again now.
 
"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."

Why should anyone send their username and password? I'll rather just wait this out, than sending this information through.
 
"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."


Why should anyone send their username and password? I'll rather just wait this out, than sending this information through.


Maybe so that WA can check the account to see if they can pick up any problems?
 
Last edited:
Maybe so that WA can check the account to see if they can pick up any problems?

They do not need your Password and ..duh.. you should never give it out – right? Specially not to their “great” support staff. Refer to recent posts of Data Theft on MYBB.

Essentially, providing WA with your Client Code will allow them to identify the MYBB Trouble Users with WA Accounts. Attend to them and they might get a good review.

Could sing you songs here but won't. It would not be sustainable.

This crowd believes in BS’ing their customers beyond believe and are part of the reason why SA has the Fncked up Internet Solutions (No Pun Intended IS ;) that we have.

Hat off to MWEB for what they are doing. Used to hate them, still not using them but getting closer.

WA….Go Fnuck yourselves. Stop bullshjtting your customers.

My 5 cents worth…all I have left after years of getting r@ped by these clowns.

PS: Response from WA with legal Jargon is imminent.
 
Maybe so that WA can check the account to see if they can pick up any problems?
Client Code should be more than enough information. I have called WA numerous times with problems and they always only asked for the Client Code.
I just think that giving out the password is a little dodgy. *shrugs*
 
WA connectivity much better, but not yet solved... (shaping currently too intense)

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 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 8 ms 6 ms 22 ms vl36.er.gw.cpt.za.wa.co.za [41.185.0.66]
5 6 ms 6 ms 7 ms vl38.cr.gw.cpt.za.wa.co.za [41.185.0.73]
6 7 ms 7 ms 7 ms fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
7 8 ms 7 ms 7 ms wa-acc1.wadns.net [196.220.39.253]
8 8 ms 9 ms 7 ms 196.220.58.66

Trace complete.

Ping statistics for 196.220.58.66:
Packets: Sent = 333, Received = 333, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 70ms, Average = 8ms

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 5 ms 5 ms wbs-ip-esr-4.ipnet.wa.co.za [41.185.86.1]
3 7 ms 6 ms 6 ms vl108.cr.gw.cpt.za.wa.co.za [196.220.59.238]
4 * 8 ms 8 ms vl35.er.gw.cpt.za.wa.co.za [41.185.0.38]
5 9 ms 7 ms 9 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 13 ms 7 ms 7 ms 196.43.25.206
8 9 ms 11 ms 8 ms ge0-3.br2.cpt1.za.mtnbusiness.net [196.7.8.206]
9 184 ms 28 ms 32 ms 196.30.1.21
10 28 ms 28 ms 27 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
11 28 ms 51 ms 28 ms 196.30.213.108
12 33 ms 27 ms 28 ms firewall1.jnb2.host-h.net [196.7.216.173]
13 58 ms 64 ms 46 ms mybroadband.co.za [41.203.21.137]

Trace complete.
 
Looking a lot better who.is.michael!
What do your international results look like this morning?
 
Top
Sign up to the MyBroadband newsletter
X