LATENCY!!!

My latency only returned to normal at around 12am last night - bit later than normal. As usual it's fine now, but it normally blows out from 9am onwards - getting a nice average ping of 14 to tenet.cinx.net.za currently.
 
This morning seems alot more stable. tracing from work... on the clareinch exchange.

Tracing route to www.saix.net [196.25.1.200]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms adpfw.localdomain [10.0.0.250]
2 6 ms 6 ms 6 ms dsl-144-160-01.telkomadsl.co.za [41.144.160.1]
3 9 ms 7 ms 6 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [196.43.11.30]
4 7 ms 7 ms 7 ms wblv-ip-www-1.saix.net [196.25.1.200]

Trace complete.

C:\Users\Ian>tracert www.telkom.co.za

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

1 <1 ms <1 ms <1 ms adpfw.localdomain [10.0.0.250]
2 5 ms 6 ms 6 ms dsl-144-160-01.telkomadsl.co.za [41.144.160.1]
3 28 ms 28 ms 29 ms rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.43.11.166]
4 28 ms 29 ms 28 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
5 31 ms 59 ms 31 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.34]
6 32 ms 32 ms * nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]
7 32 ms 31 ms 33 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]

Trace complete.

I find though that it gets worse progressively through the course of the day. Last night was just shocking. I reckon the downloading at those times causes the sudden jump in latency.
 
@ Will@MWEB - Here are the stats for Cape Town CBD

Pinging www.saix.net [196.25.1.200] with 32 bytes of data:
Reply from 196.25.1.200: bytes=32 time=244ms TTL=250
Reply from 196.25.1.200: bytes=32 time=292ms TTL=250
Reply from 196.25.1.200: bytes=32 time=235ms TTL=250
Reply from 196.25.1.200: bytes=32 time=218ms TTL=250

Ping statistics for 196.25.1.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 218ms, Maximum = 292ms, Average = 247ms



Tracing route to www.saix.net [196.25.1.200]
over a maximum of 30 hops:

1 189 ms 192 ms 179 ms dsl-144-152-01.telkomadsl.co.za [41.144.152.1]
2 168 ms 138 ms 132 ms wblv-ip-essr-1-atm-2-0-0-1.telkom-ipnet.co.za [1
96.43.11.22]
3 152 ms 157 ms 132 ms wblv-ip-www-1.saix.net [196.25.1.200]

Trace complete.

Done at 9am.

Thanks
 
Seems to be much less 'head-wind' this morning in the Southern Suburbs, I'm also getting sub-10ms local latency at 9am!

Did Will@MWeb say that the problem had been 'identified' or 'fixed'?

Still some slight delays on other backhaul routes, but these are beyond the IPC stage, and normal for peak periods.

Edit: Oh dear, seems like CBD still has a problem...
 
Last edited:
I seriously hope theve resolved the issue, but previously the pings have gone normal, then screwed again later in the day so im not holding my breath.

If a telkom techie verbally acknowledged the problem, and hes a gamer and effected, my worry has been put at ease somewhat. Will wait and see what happens.
 
I have a telkom and mweb account... on my mweb uncapped I have latency in excess of 8000ms playing world of warcraft tonight but when I switch to my telkom account my latency is around 250 - 350ms .... explain that!!!

Ps. I play on the US servers and with my webafrica account I cant even connect to wow (permenantly)!!
Click to expand...

Please guys, read the thread. This is not about general latency issues, but about Telkom network issues in Cape Town.

But anyway, Mweb uncapped is problematic for gaming. One of my friends who has it can rarely ever log into steam, but it's uncapped so he doesn't complain about it. WA is also having some network issues if you look around the forums. You want good WoW pings? Go with a shaped/semi-shaped/unshaped capped account.
 
Last edited:
From Newlands on the Clareinche exchange:-

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 10 ms 10 ms 41-133-112-1.dsl.mweb.co.za [41.133.112.1]
3 12 ms 12 ms 12 ms 196-28-178-166.adsl.mweb.co.za [196.28.178.166]
4 12 ms 11 ms 12 ms 196.41.144.36
5 12 ms 12 ms 13 ms www.mweb.co.za [196.2.63.110]

Trace complete.

At work I'm on the Foreshore exchange (DeWaterkant area) and getting 8ms ping to www.mweb.co.za
 
nicomz said:
Will@Mweb Stop Lying to user about a Telkom problems, Mweb has the problems not telkom, it is time users stand up to you(Mweb) and take a stance against you. Mweb is gonna have a big suprise in the coming days and weeks. Things have gone to far with Mweb bul****ting users. What Mweb is doing is Fraud!!!!!!
Click to expand...

These issues are affecting users at the exchanges being discussed regardless of ISP, please learn to read and don't post such drivel. It just makes you look ignorant and wastes the time of people actually trying to resolve the issues.
 
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.
 
Hey

Will check it out tonight. But yeh, My ping is usually fine until 7:30pm. Then 160ms-200ms then at 11:15pm it is back to 20ms. So for the guys that did tracerts after 11pm, it is normal if your ping was below 100ms
 
Oh no, the monster is coming back to life...

It has been fine up till now, but local latency has reached 50ms at 11am!?

I don't think anything has been properly 'fixed' yet, it has just been a slow Thursday...
 
nicomz said:
Will@Mweb Stop Lying to user about a Telkom problems, Mweb has the problems not telkom, it is time users stand up to you(Mweb) and take a stance against you. Mweb is gonna have a big suprise in the coming days and weeks. Things have gone to far with Mweb bul****ting users. What Mweb is doing is Fraud!!!!!!
Click to expand...

As RSD mentioned above - go back to the rock you climbed out of buddy. This is NOT ISP related...
 
Surv0 said:
I seriously hope theve resolved the issue, but previously the pings have gone normal, then screwed again later in the day so im not holding my breath.

If a telkom techie verbally acknowledged the problem, and hes a gamer and effected, my worry has been put at ease somewhat. Will wait and see what happens.
Click to expand...

Don't you have any parcels to move around. Go push some boxes damn you!

I can't say I can complain , my Openweb Gold 384kbps uncapped account is flying - full speed both day and night.

J
 
Tracing route to www.saix.net [196.25.1.200]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms adpfw.localdomain [10.0.0.250]
2 6 ms 5 ms 6 ms dsl-144-160-01.telkomadsl.co.za [41.144.160.1]
3 7 ms 7 ms 7 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [196.43.11.30]
4 75 ms 73 ms 73 ms wblv-ip-www-1.saix.net [196.25.1.200]

Trace complete.

Hope 4 is worrying... think its taking a turn again...
 
Last edited:
Latency is still a hint high on local (24ms more than usual), but much better on the whole.
 
jsheed_sa said:
Don't you have any parcels to move around. Go push some boxes damn you!

I can't say I can complain , my Openweb Gold 384kbps uncapped account is flying - full speed both day and night.

J
Click to expand...

pfft - 384 :p no need to slow those down, as they are already the slowest :p go cache some more youtube videos to give u something to watch later...

Pinging www.saix.net [196.25.1.200] with 32 bytes of data:
Reply from 196.25.1.200: bytes=32 time=30ms TTL=250
Reply from 196.25.1.200: bytes=32 time=30ms TTL=250
Reply from 196.25.1.200: bytes=32 time=24ms TTL=250
Reply from 196.25.1.200: bytes=32 time=26ms TTL=250
Reply from 196.25.1.200: bytes=32 time=10ms TTL=250
Reply from 196.25.1.200: bytes=32 time=14ms TTL=250
Reply from 196.25.1.200: bytes=32 time=15ms TTL=250
Reply from 196.25.1.200: bytes=32 time=21ms TTL=250
Reply from 196.25.1.200: bytes=32 time=29ms TTL=250
Reply from 196.25.1.200: bytes=32 time=29ms TTL=250
Reply from 196.25.1.200: bytes=32 time=22ms TTL=250
Reply from 196.25.1.200: bytes=32 time=8ms TTL=250
Reply from 196.25.1.200: bytes=32 time=24ms TTL=250
Reply from 196.25.1.200: bytes=32 time=23ms TTL=250
Reply from 196.25.1.200: bytes=32 time=22ms TTL=250

Ping statistics for 196.25.1.200:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 30ms, Average = 21ms

Still up and down, but not going above 30 on my side.
 
Yep. Seeing the same thing. But it's all over the place. I average about 70 a few minutes ago (tenet.cinx.net.za), now its down to 35, but as I type it's heading north again. Now down to 12 LOL.

Will have to monitor it over a longer period and especially tonight around Unhappy Hour (7pm) when it usually bombs.
 
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...


Last night my international speed test results yielded 0.10mbps download, and 0.40mbps up. Packet loss on pinging towards sky.net and gamepath.net.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X