LATENCY!!!

Gordon_R said:
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...
Click to expand...

Brother passed the story on from a friend at college, told him to get more details tomorrow if possible, will relay on forum.
 
Yeah latency went a bit iffy just before 7 but now it is flying on AxxessLite in WoW. On Clareinch exchange, this has been the best latency in weeks (months?). 384k line getting about 450ms to 650ms which is pretty damn decent.

Lets hope they have fixed and improved the service!
 
Mine is back to normal :D

Time to shoot people in the face!!!
 
Spiking a bit but playable. Probably some work that still needs to be done but its good to be able to play again!
 
Very nice :)

Lets hope it stays like this



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

1 1 ms <1 ms <1 ms login.router [10.0.0.2]
2 7 ms 7 ms 7 ms wrbs-ip-esr-2.ipnet.wa.co.za [41.185.88.1]
3 8 ms 8 ms 9 ms vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
4 9 ms 9 ms 8 ms vl36.er.gw.cpt.za.wa.co.za [41.185.0.66]
5 9 ms 9 ms 8 ms vl38.cr.gw.cpt.za.wa.co.za [41.185.0.73]
6 9 ms 8 ms 8 ms fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
7 9 ms 9 ms 9 ms wa-acc1.wadns.net [196.220.39.253]
8 10 ms 9 ms 9 ms www.webafrica.co.za [196.220.58.66]

Trace complete.
 
I just played a clannie and 30-40ms. felt great. I wonder what has changed tbh and I wonder if it is going to stay this way
 
Last edited:
Phoned my buddy at telkom and he agreed with what the other techie told me this morning when he called while he was at the exchange.
They have been busy moving ppl around on the exchange to cater for the repairs that was needed to be done caused by some "unforseen" bugs after the upgrades.
The moving around meant that more ppl was on 1 exchange hence more congestion aswell. seems we all a bit better off now :)
 
well my ping is still fine :) why didnt they just admit it? if they had said "yes, thats a temporary problem in your area while we fix the networks which will be completed before november" then atleast we could have just chilled and waited. its actually disgusting how they arent able to tell us anything and resort to making up lies to get rid of us. i am going to record all my future phone calls with telkom because that was just ridiculous.
 
If you admit to a problem then you also have to comit to a timeline for repair. If you deny and refrain from comment you covering your own ass and can take your own sweet time to repair something that you broke. - that most likely their approach!!! from a business point, thats never good business, its still business , just a nevermind attitude. and we moan at the techies and callcentre staff but they have no choice but to do as they told, they will never comit to giving you a proper answer unless they 100% sure of it.
Best thing to do is to when you see a technician in your area, go over and make friends with him/her, that way you will have at least contact with the ppl actually doing the work at ground level.
 
Well, everything looked fine last night - like having new internet all over again..

Let's hope it's resolved for good.
 
Calix: Good point about denial and ETA.

Joker: I think the problem will just surface somewhere else in a month's time!

And so the the cycle will continue...
 
Gordon_R said:
Joker: I think the problem will just surface somewhere else in a month's time!

And so the the cycle will continue...
Click to expand...
Agreed - whatever was fixed I suspect it is temporary.
Keep a look out for a new thread opening soon - "LATENCY,NOTHERN SUBURBS!!!!!!!!!!"
Hope I am wrong.
 
ajules said:
Agreed - whatever was fixed I suspect it is temporary.
Keep a look out for a new thread opening soon - "LATENCY,NOTHERN SUBURBS!!!!!!!!!!"
Hope I am wrong.
Click to expand...

Who cares about the Northern Suburbs :-)
 
I laugh that happens and then one of you guys move to the Northern Suburbs. I will LoL Hard.
 
jpmonster said:
I laugh that happens and then one of you guys move to the Northern Suburbs. I will LoL Hard.
Click to expand...

It was a joke! Our offices in Century City gets routed through Bellville and we work with VPN's and latency sensitive applications so latency like that will essentially mean that for all practical purposes we have no connectivity. But I am slightly worried that it will happen in the Northern Suburbs in the future. We are currently still on 4Mbps at the office, so there is an exchange or two still to be upgraded :-( More pain on the way I expect.
 
Mine's back up sky high. Anyone else?

On WA - Table View, CPT

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\duaN>ping www.mybroadband.co.za

Pinging www.mybroadband.co.za [41.203.21.137] with 32 bytes of data:
Reply from 41.203.21.137: bytes=32 time=490ms TTL=51
Reply from 41.203.21.137: bytes=32 time=523ms TTL=51
Reply from 41.203.21.137: bytes=32 time=524ms TTL=51
Reply from 41.203.21.137: bytes=32 time=540ms TTL=51

Ping statistics for 41.203.21.137:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 490ms, Maximum = 540ms, Average = 519ms

C:\Users\duaN>ping www.wage.co.za

Pinging www.wage.co.za [196.220.58.65] with 32 bytes of data:
Reply from 196.220.58.65: bytes=32 time=922ms TTL=120
Reply from 196.220.58.65: bytes=32 time=876ms TTL=120
Reply from 196.220.58.65: bytes=32 time=942ms TTL=120
Reply from 196.220.58.65: bytes=32 time=663ms TTL=120

Ping statistics for 196.220.58.65:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 663ms, Maximum = 942ms, Average = 850ms

C:\Users\duaN>ping www.webafrica.co.za

Pinging www.webafrica.co.za [196.220.58.66] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Reply from 196.220.58.66: bytes=32 time=972ms TTL=120

Ping statistics for 196.220.58.66:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 972ms, Maximum = 972ms, Average = 972ms

C:\Users\duaN>ping www.webafrica.co.za

Pinging www.webafrica.co.za [196.220.58.66] with 32 bytes of data:
Reply from 196.220.58.66: bytes=32 time=552ms TTL=120
Reply from 196.220.58.66: bytes=32 time=829ms TTL=120
Request timed out.
Request timed out.

Ping statistics for 196.220.58.66:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 552ms, Maximum = 829ms, Average = 690ms

C:\Users\duaN>
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X