LATENCY!!!

WAangelo said:
Hi guys

Thank you for all your valuable feedback provided so far.

Our engineers have informed us that they have tweaked the network a bit and things should be running a bit smoother now.

We have since noticed a big drop in latency/speed queries both via tickets and calls.

If there is anyone still experiencing issues with high latency/speed issues, I urge you to contact our support center and log it with a consultant.

We would like to try to identify any trends or recurring issues so that we can work on putting measures in place to enhance your Web Africa experience.

Thank you.
Click to expand...

Sorry Angelo, you haven't fixed the problem.

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

1 18 ms 18 ms 16 ms dsl-185-88-1.dynamic.wa.co.za [41.185.88.1]
2 21 ms 24 ms 20 ms vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
3 18 ms 19 ms 19 ms vl36.er.gw.cpt.za.wa.co.za [41.185.0.66]
4 34 ms 37 ms 37 ms vl38.cr.gw.cpt.za.wa.co.za [41.185.0.73]
5 154 ms 151 ms 144 ms fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
6 * 124 ms 126 ms wa-acc1.wadns.net [196.220.39.253]
7 126 ms 123 ms 123 ms 196.220.58.66

Trace complete.
 
I'm with MWEB (Clareinche) but if I run that same tracert I get:

Tracing route to webafrica.com [196.220.58.66]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 9 ms 10 ms 41-133-112-1.dsl.mweb.co.za [41.133.112.1]
3 72 ms 76 ms 76 ms 196-28-178-166.adsl.mweb.co.za [196.28.178.166]

4 90 ms 87 ms 88 ms 196-28-178-133.adsl.mweb.co.za [196.28.178.133]

5 107 ms 104 ms 102 ms 198.32.214.45
6 125 ms 124 ms 122 ms vl40.cr.gw.cpt.za.wa.co.za [41.185.0.97]
7 100 ms 103 ms 103 ms fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
8 111 ms 125 ms 104 ms wa-acc1.wadns.net [196.220.39.253]
9 106 ms 104 ms 111 ms 196.220.58.66

Trace complete.
 
I spoke to soon, seems problem is getting worse again...

Pinging www.saix.net [196.25.1.200] with 32 bytes of data:
Reply from 196.25.1.200: bytes=32 time=59ms TTL=250
Reply from 196.25.1.200: bytes=32 time=61ms TTL=250
Reply from 196.25.1.200: bytes=32 time=42ms TTL=250
Reply from 196.25.1.200: bytes=32 time=53ms TTL=250
Reply from 196.25.1.200: bytes=32 time=52ms TTL=250
Reply from 196.25.1.200: bytes=32 time=53ms TTL=250
Reply from 196.25.1.200: bytes=32 time=64ms TTL=250
Reply from 196.25.1.200: bytes=32 time=64ms TTL=250
Reply from 196.25.1.200: bytes=32 time=67ms TTL=250
Reply from 196.25.1.200: bytes=32 time=67ms TTL=250

Ping statistics for 196.25.1.200:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 67ms, Average = 58ms
 
I am also having a problem with WA. To WA, something is definitely wrong with your network ... it's been off and on since Monday on my side. IS with AH works fine.

Sort it out ...
 
Blown out completely again:

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 9 ms 10 ms 41-133-112-1.dsl.mweb.co.za [41.133.112.1]
3 131 ms 134 ms 138 ms 196-28-178-166.adsl.mweb.co.za [196.28.178.166]
4 140 ms 146 ms 147 ms 196.41.144.36
5 161 ms 160 ms 149 ms www.mweb.co.za [196.2.63.110]

Trace complete.

I logged a fault online a few days ago - yesterday someone from the call centre phoned me and after I explained the problem said she would get a technician to phone me (not bad). Which he did a few hours later (good) - he had already tested my line and found no problem (very good - but I knew that already), then when I explained the problem he said he would have to ask the Clareinche exchange specialist to contact me today (excellent). Nothing yet though - but this is the furtherest I have ever gotten. LOL.
 
JayN said:
I am also having a problem with WA. To WA, something is definitely wrong with your network ... it's been off and on since Monday on my side. IS with AH works fine.

Sort it out ...
Click to expand...

This thread is for the Cape Town latency issue.
 
Here we go - all going bad now...

Pinging www.saix.net [196.25.1.200] with 32 bytes of data:
Reply from 196.25.1.200: bytes=32 time=151ms TTL=250
Reply from 196.25.1.200: bytes=32 time=145ms TTL=250
Reply from 196.25.1.200: bytes=32 time=120ms TTL=250
Reply from 196.25.1.200: bytes=32 time=133ms TTL=250
Reply from 196.25.1.200: bytes=32 time=139ms TTL=250
Reply from 196.25.1.200: bytes=32 time=153ms TTL=250
Reply from 196.25.1.200: bytes=32 time=128ms TTL=250
Reply from 196.25.1.200: bytes=32 time=126ms TTL=250
Reply from 196.25.1.200: bytes=32 time=121ms TTL=250
Reply from 196.25.1.200: bytes=32 time=137ms TTL=250
Reply from 196.25.1.200: bytes=32 time=142ms TTL=250
Reply from 196.25.1.200: bytes=32 time=138ms TTL=250

Ping statistics for 196.25.1.200:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 120ms, Maximum = 153ms, Average = 136ms
 
It is very Likely that all WA issues are caused by our Southern Suburb problems as there Data Center sits in Newlands which is the middle of all this mess, therefore routing for most WA users will be affected as well.

But Yeah, this is a CT Latency Thread, I would suggest someone change it
 
Up to 140ms local latency on Clareinch at 2pm. Seems as bad as usual...

Surv0 said:
guess the downloading has begun....
Click to expand...

Update: Well, I was downloading a podcast (12MB at 20KB/sec). So, do I now need to notify my ISP in advance when I want to do downloads??
 
Last edited:
absynth said:
@ Will@MWEB - Here are the stats for Cape Town CBD
Click to expand...

Thanks absynth, my last request for feedback was to try and ascertain the full extent of the fault that has now been acknowledged - it may turn out to be the same issue that's affecting you. If not we'll take it on in the next round.
 
Hi guys

I have been in contact with the engineers to find out if there is any further updates.

I have been assured that the general latency issue has been resolved.

Extensive testing was done our side to try and replicate the the problem but it did not resurface.

Everything on our network is operational and functioning as it should.

The general problem still seems to be an external factor and this is by no means pointing a finger at anybody/organization.

We can assure you that we are doing everything in our power to try and locate the source of the problems being experienced.

We ask that you continue to monitor your connection and forward us any test results.

If there are instances where you receive better results using a different ISP account, we urge you to continue posting the results.


Thank you.
 
Gordon_R said:
Up to 140ms locla latency on Clareinch at 2pm. Seems as bad as usual...
Click to expand...

Gordon you seem to have done a great job of tracking this issue from your side - at what times of the day would you say the latency is generally present?
 
Sigh.

I have PM'd antowan asking him to change the name of the thread so hopefully people with their isolated problems will stop posting here :/
 
Will@MWEB said:
Gordon you seem to have done a great job of tracking this issue from your side - at what times of the day would you say the latency is generally present?
Click to expand...

from my experience, usually starts just after lunch, from about 1 or 2. But its very intermittant, daily, for at least the last 2 months. Some days it only starts peaking in the evening or night. Other times it starts in the morning. But definitely seems to be more in the afternoon, possibly in conjunction with shaping periods by ISPs.
 
Hi Will, for me it follows a similar pattern (with slight variations). Normal until about 9am, then averages at about 8x worse until about 4pm-6pm, then averages about 14x from there until about 11:30pm.

Packet losses worst between 7pm and 11pm. I have a nice graph of the last couple of days but not sure how to send it to you.
 
teRRRier said:
Hi Will, for me it follows a similar pattern (with slight variations). Normal until about 9am, then averages at about 8x worse until about 4pm-6pm, then averages about 14x from there until about 11:30pm.

Packet losses worst between 7pm and 11pm. I have a nice graph of the last couple of days but not sure how to send it to you.
Click to expand...

Pretty much exactly the same for me, except I'm alright till about 10:00 or so in the mornings.
 
I can tell you that my latencies are in the 150 region when I get home at 6. They climb to about 200 and then start dropping at about 11.00 PM. My download speeds also hover around 1 meg at most during this time period, and I'm on a 6 meg profile. This has only started recently, since two weeks ago I was flying at full speed with no latency issues.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X