LATENCY!!!

nope mine still steady aswell. using saix atm . tested with IS and pings bit higher tho.
 
My graph is very similar to teRRRier, though I have min/max on, showing even more spikes (5th hop only).

I turn my PC off overnight, so I can't show a 12 hour graph, but the 24 hour graph shows a huge improvement!
 
(rondebosch) well, i noticed my pings improve at 10pm last night and are still 'decent', but definitely not ideal. theres still packet loss and lots of jitter, and it looks like my ping is starting to get worse right now.

12 hour graph:
http://i.imgur.com/1KbDR.png

speed test (mweb 4meg uncapped on a 6meg line):
http://www.speedtest.net/result/1004954246.png

@ WA / MWEB: have you gotten any official word from telkom?
 
jpmonster said:
@Calix, Im in Sybrand Park, Next to the Rondebosch Golf Course
Click to expand...

Interesting that u basically next to athlone and a buddy of mine lives there and he has not been gettin any of the problems that we have had day or night.. he also on 4mb line.
 
Pinging telkom.co.za [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=36ms TTL=243
Reply from 196.43.22.222: bytes=32 time=36ms TTL=243
Reply from 196.43.22.222: bytes=32 time=35ms TTL=243
Reply from 196.43.22.222: bytes=32 time=35ms TTL=243
Reply from 196.43.22.222: bytes=32 time=37ms TTL=243
Reply from 196.43.22.222: bytes=32 time=35ms TTL=243
Reply from 196.43.22.222: bytes=32 time=35ms TTL=243
Reply from 196.43.22.222: bytes=32 time=35ms TTL=243
Reply from 196.43.22.222: bytes=32 time=38ms TTL=243
Reply from 196.43.22.222: bytes=32 time=35ms TTL=243
Reply from 196.43.22.222: bytes=32 time=35ms TTL=243
Reply from 196.43.22.222: bytes=32 time=35ms TTL=243
Reply from 196.43.22.222: bytes=32 time=35ms TTL=243
Reply from 196.43.22.222: bytes=32 time=36ms TTL=243
Reply from 196.43.22.222: bytes=32 time=35ms TTL=243
Reply from 196.43.22.222: bytes=32 time=35ms TTL=243
Reply from 196.43.22.222: bytes=32 time=36ms TTL=243
Reply from 196.43.22.222: bytes=32 time=36ms TTL=243
Reply from 196.43.22.222: bytes=32 time=38ms TTL=243
Reply from 196.43.22.222: bytes=32 time=36ms TTL=243

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

Looking good on my side..
 
Content for now , still waiting to see rest of the day. Would really like an official response as to if it had been fixed, I realy cant take the word of a techie that called me this morning although as far as results are now , he might have been on the right track as to what was going on.


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

1 7 ms 9 ms 7 ms dsl-242-172-01.telkomadsl.co.za [41.242.172.1]
2 7 ms 8 ms 8 ms 196.43.11.218 ------------ > gauteng ??
3 8 ms 8 ms 8 ms 196.43.25.206 -------------> Parrow ?? hmmm?
4 10 ms 9 ms 9 ms ge0-3.br2.cpt1.za.mtnbusiness.net [196.7.8.206]

5 42 ms 40 ms 41 ms ge11-0-0.gw2.jnb6.za.mtnbusiness.net [196.30.1.2
2]
6 40 ms 38 ms 42 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.13
6]
7 40 ms 41 ms 42 ms 196.30.213.108
8 68 ms 43 ms 47 ms firewall1.jnb2.host-h.net [196.7.216.173]
9 60 ms 41 ms 42 ms mybroadband.co.za [41.203.21.137]

Trace complete.


Tracing route to games.saix.net [196.43.22.222]
over a maximum of 30 hops:

1 19 ms 14 ms 8 ms dsl-242-172-01.telkomadsl.co.za [41.242.172.1]
2 27 ms 28 ms 28 ms rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.4
3.11.166]
3 28 ms 82 ms 28 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
4 33 ms 32 ms 38 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.34]
5 31 ms 31 ms 30 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.
 
Last edited:
Now if this results can continue when ppl get home later on... :) lets hope
 
I've received no notification of any fix yet. Until i do my assumption is that any reduction we are seeing in symptoms is temporary, we have had days like this before.
 
Will@MWEB said:
I've received no notification of any fix yet. Until i do my assumption is that any reduction we are seeing in symptoms is temporary, we have had days like this before.
Click to expand...

and hope we have plenty more.
@will : the comment the techie gave me. whats your thoughts on that?
 
this is what happened when i restarted my router,i recommend you try it:
http://i.imgur.com/aE70X.png

those spikes might be my IM and browser. not sure. played some quake and it was awesome!!! i got the sickest frags... please stay!!
 
Lack of comments on this thread = people not having issues at the moment I take it. Apparently some techy found the problem and fixed it, he deserves a medal.
 
Shard said:
Lack of comments on this thread = people not having issues at the moment I take it. Apparently some techy found the problem and fixed it, he deserves a medal.
Click to expand...

Details about this techie please! Or are you just speculating?

Edit: Latency still looking good for me. I'm not quite ready to delete PingPlotter yet!

Tracert should be fine for routine checking one this 'episode' is over...
 
Last edited:
Much better tonight in Claremont/Newlands

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

1 6 ms 15 ms 9 ms 41.0.60.1
2 44 ms 36 ms 44 ms 41.0.9.214
3 47 ms 40 ms 38 ms 41.0.72.1
4 30 ms 32 ms 37 ms 41.0.9.61
5 37 ms 31 ms 32 ms 41.0.0.5
6 31 ms 30 ms 30 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.253.109]
7 44 ms 33 ms 33 ms rrba-ip-esr-1-pos-8-0-0.telkom-ipnet.co.za [196.43.8.146]
8 37 ms 30 ms 37 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
9 37 ms 33 ms 39 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.30]
10 35 ms 38 ms 36 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]

Trace complete.
 
My local latency is still good, but I've just started getting horrendous international results. Anybody else?

Edit: Was just been for a few mins. International seems stable now.

Changed my PingPlot to news.bbc.co.uk (usually 260ms from CT vis SEACOM).
 
Last edited:
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X