Web Africa issues in Cape Town?

dualmeister

dualmeister

Honorary Master
Joined
Oct 15, 2005
Messages
74,625
Reaction score
139,071
Location
Cape Town
Anyone else having Web Africa issues in the Cape Town, Durbanville area?

Since Monday our line has be totally unstable.

Reported issue to Web Africa 4 days ago, but they've been stuffing around and nothing has improved! :mad:

Telkom has been out to check the line. Tested with their router and ISP account. No issues.

Tested line using FNB Connect account. No issues.
Tested line using MWEB account. No issues.

Using Web Africa account.

Ping statistics for 74.125.233.81:
Packets: Sent = 200, Received = 173, Lost = 27 (13% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 253ms, Average = 39ms

They keep saying they'll call back, but don't.

Pathetic service.
 
Tracing route to www.google.com [74.125.233.81]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.0.1
2 8 ms 7 ms 8 ms xxx.xxx.xxx.xxx.dynamic.isadsl.co.za [xxx.xxx.xxx.xxx]
3 9 ms 9 ms 9 ms cdsl1-ctn-vl2173.ip.isnet.net [196.38.72.113]
4 9 ms 9 ms 9 ms 196.35.115.128
5 9 ms 9 ms 10 ms 168.209.6.13
6 30 ms 30 ms 30 ms 168.209.100.213
7 57 ms 29 ms 30 ms 168.209.1.179
8 30 ms 31 ms 36 ms 74.125.49.66
9 31 ms 31 ms 30 ms 64.233.174.57
10 31 ms 30 ms 30 ms jnb01s02-in-f17.1e100.net [74.125.233.81]

Trace complete.

Tracing route to www.webafrica.co.za [41.185.61.34]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 8 ms 7 ms 8 ms xxx.xxx.xxx.xxx.dynamic.isadsl.co.za [xxx.xxx.xxx.xxx]
3 9 ms 9 ms 9 ms cdsl2-ctn-vl2276.ip.isnet.net [196.38.72.125]
4 9 ms 9 ms 9 ms 196.35.115.136
5 15 ms 9 ms 9 ms 196.26.78.33
6 9 ms 9 ms 9 ms wa-is.isdsl.net [196.38.72.84]
7 9 ms 9 ms 9 ms wnls-cr2-vl-140.wa.co.za [41.185.1.1]
8 10 ms 10 ms 9 ms 41.185.61.34

Trace complete.
 
Last edited:
Can you do it again when there is packet loss? Cause those 2 traceroutes look 100% fine, while the ping stats shows there is a problem.
 
Tracing route to www.google.com [74.125.233.80]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.0.1
2 * * 7 ms xxx.xxx.xxx.xxx.dynamic.isadsl.co.za [xxx.xxx.xxx.xxx]
3 * * * Request timed out.
4 * * 13 ms 196.35.115.136
5 10 ms 14 ms 9 ms 168.209.6.13
6 * * * Request timed out.
7 53 ms 29 ms 30 ms 168.209.1.179
8 * * * Request timed out.
9 * 39 ms 51 ms 64.233.174.57
10 147 ms 149 ms 144 ms jnb01s02-in-f16.1e100.net [74.125.233.80]

Trace complete.
 
Last edited:
dualmeister said:
Tracing route to www.google.com [74.125.233.80]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.0.1
2 * * 7 ms xxx.xxx.xxx.xxx.dynamic.isadsl.co.za [xxx.xxx.xxx.xxx]
3 * * * Request timed out.
4 * * 13 ms 196.35.115.136
5 10 ms 14 ms 9 ms 168.209.6.13
6 * * * Request timed out.
7 53 ms 29 ms 30 ms 168.209.1.179
8 * * * Request timed out.
9 * 39 ms 51 ms 64.233.174.57
10 147 ms 149 ms 144 ms jnb01s02-in-f16.1e100.net [74.125.233.80]

Trace complete.
Click to expand...
In all honesty, that traceroute make it look like your ADSL line or Exchange is having problems at that moment you did the trace. Chances are, you have just been on the Web Africa account when the packet loss happen. You may need to stay on another ISP account long enough to see the problem also happen on those accounts.

But basically, hop 2 sits on a Telkom router, only hop 3 is on the IS network (which Web Africa uses).

So your bad luck is, while Telkom was there testing, the issue wasn't showing, because it is intermittent, and thus they close it as not being an issue at all.

Best of luck getting it resolved, intermittent issues are the worst.
 
Well the fact is. Was just on Web Africa account. Have zero internet connection.

Switched to MWEB and boom.

Ping statistics for 74.125.233.48:
Packets: Sent = 1000, Received = 1000, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 951ms, Average = 59ms

Tracing route to www.google.com [74.125.233.48]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 7 ms 6 ms 6 ms 41-xxx-xx-x.dsl.mweb.co.za [41.xxx-xx-x]
3 7 ms 8 ms 7 ms 197-84-96-138.cpt.mweb.co.za [197.84.96.138]
4 8 ms 7 ms 7 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 37 ms 38 ms 35 ms 197-84-5-242.cpt.mweb.co.za [197.84.5.242]
6 37 ms 39 ms 42 ms tengig0-7-0-1.vic-p-1.mweb.co.za [197.84.4.47]
7 35 ms 35 ms 35 ms 197-80-7-5.jhb.mweb.co.za [197.80.7.5]
8 35 ms 35 ms 35 ms 197-80-96-6.jhb.mweb.co.za [197.80.96.6]
9 39 ms 36 ms 35 ms 64.233.174.21
10 36 ms 36 ms 35 ms jnb01s01-in-f16.1e100.net [74.125.233.48]

Trace complete.

Will monitor MWEB as long as possible. But, I'm sure there won't be issues.
 
Could just be co-incidence still. Maybe you should stay on that M-Web account for longer, or even a whole day and just see if it stays like that.
 
Hmmm. This is interesting. Maybe it's my WA account that's giving me issues and not my router. I've had plenty of disconnects lately.
 
dualmeister said:
Unfortunately, they are hosting our mail so we have to be on their network.
Click to expand...

You don't have to be on their network to use their mail servers. You only need to be on a WA account if you want to use smtp.wa.co.za to send mail, but if you use the mail server for your domain you can be on any other dsl account.
 
We using:

pop.ourcompanyname.co.za
smtp.ourcompanyname.co.za

After numerous calls to them they seemed to have changed something as it has been OK for the last hour. The longest period of time since Monday.
 
Last edited:
With those servers, you can most certainly use any DSL account you like to be honest. Use whatever won't be causing you problems.
 
Hi Guys,

Can you you PM me your customer codes or email addresses so I can get our team to take a look. Those trace routes look fine and it could be an intermittent issue.

We have had no reported issues in the Cape Town area on our network.
 
Have been all the way up the ladder regarding WA support with no luck so looking at other options.

Is it possible that Telkom routes the traffic to Web Africa and FNB Connect differently at the exchange level? Like 2 different DSLAMs or whatever.

Its now a month later and our line is still ****ed, but only when connecting to Web Africa NOT FNB Connect or MWEB.

I believe that the Telkom routing to WA is some how overloaded.

The issues first started the Monday that most people came back to work after Dec holidays and starts timing out every morning at around 08H10.

How on earth do I even get Telkom to look into this :erm:
 
dualmeister said:
Have been all the way up the ladder regarding WA support with no luck so looking at other options.

Is it possible that Telkom routes the traffic to Web Africa and FNB Connect differently at the exchange level? Like 2 different DSLAMs or whatever.

Its now a month later and our line is still ****ed, but only when connecting to Web Africa NOT FNB Connect or MWEB.

I believe that the Telkom routing to WA is some how overloaded.

The issues first started the Monday that most people came back to work after Dec holidays and starts timing out every morning at around 08H10.

How on earth do I even get Telkom to look into this :erm:
Click to expand...

Could you PM your details so I can get our team to follow up with you.
 
Its being worked on thanks :)

Went as high as the CEO so getting some action now. Amazing though how at first everyone said there was nothing wrong, but finally someone admitted that there are some upstream issues.
 
Last edited:
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X