Latency?

Is it just me, or has the latency increased again? ..
getting about 110ms......... it was at about 40-50ms yesterday?

anybody know anything about this?..

:mad:

Yeah I heard a few people from Darwin talk about increased latency, so I don't think it's just you :P

I'd be willing to point my finger at Telstra for the fault.

I've been having issues all day :(

Not sure what is going on.

Pinging games.internode.on.net [203.26.94.189] with 32 bytes of data:

Reply from 203.26.94.189: bytes=32 time=86ms TTL=61
Reply from 203.26.94.189: bytes=32 time=86ms TTL=61
Reply from 203.26.94.189: bytes=32 time=85ms TTL=61
Reply from 203.26.94.189: bytes=32 time=86ms TTL=61

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

This is the second time ive noticed this in the last couple of months - ping rate doubles for a couple of days and then drops back down ( later part hasnt happened yet :mad: )

When ive asked other players on the servers ( that are down south and 'node customers) they reckon that thier ping rate hasnt changed at all so it seems to come back the Telstra and the Cas exchange.....

either way very annoying

Bring on Fiber to node!!!

This mite be the problem,

the following is post made by Simon Hackett on the Whirlpool Internode Forums

Quote:
This issue is years old.

Here: Let me re-explain it to save you looking around for older threads about it:

It is the result of a configuraition characteristic in the national Telstra ATM data backhaul network. Every time there is a brief outage on a data path, the ATM network switches almost instantly to a backup path, if one exists. That is great. It means that when the 'short' path from Alice and/or Darwin to Adelaide goes down, the Telstra ATM data network instantly switches your data to their backup path.

That backup path from Alice (I believe) involves moving the data back via Darwin and then across via two other states and down again back to Adelaide - with the resulting higher latency (but at least you're still connected).

But ATM data networks are older, and in some ways less smart, than IP based ones. And this is an ATM network, not an IP one, at this level. The ATM network does NOT consider the minimisation of latency to be a target here - if the backup link is working, then the network will continue to use that (much longer) backup path until the BACKUP path later has a glitch, at which point the data flow will switch back to the original, shorter path.

Telstra *can* configure their ATM network, instead of the above, so that it is 'revertive' - i.e. so that it automatically reverts to a specified path when that path is available. That would cause the service to snap back to the lower latency path automatically.

But the ATM network isn't just for ADSL, its the general backhaul network Telstra uses for all sorts of things. And they refused, simply aren't interested, in changing the configuration of the underlying network. I have the long winded version of 'no' back in my mailbox somewhere, but it comes down to Telstra refusing to specify any latency targets in their ADSL service (they really don't contract to provide us with ANY specific target latency), so this is, in their view, NOT A FAULT and hence it isn't something they want to mess with their underlying ATM network to 'fix' because it isn't (in their view) broken.

Instead, then, every time it happens, our staff spend days trying to get someone at Telstra Wholesale to in turn try to get someone in their ATM network management area to briefly reset the backup path to force the data back onto the primary path.

That fixes the issue, but the next time the primary path goes down, even for 10-20 milliseconds, 'blink' - we're back on the backup path again. That might not happen again for days or weeks. Or it might happen ten minutes after the backup path is reset.

We have indeed complained about it repeatedly, and we ultimately received a high level response which I'd summarise as 'Not interested in fixing it'.

We buy the service Telstra deliver to us, in terms of the tail circuit offering available to us to provide.

It is exactly the same offering everyone else gets - the differentiations start at the point where we pick your data up and plug it in to our own national network.

I will repeat this so you are clear on it:

THIS ISSUE AFFECTS ALL ISPs EQUALLY: All Wholesale Telstra DSLAM acquirers, and it also affects all BigPond retail ADSL customers.

Even though it does, Telstra still won't change the underlying ATM network configuration to permanently fix it. At least we have tried to convince them to do so - and the fact that we, on our own, haven't been able to, just suggests it doesn't matter as much to other ISP's as it does to us, because we are very focussed on providing an excellent service.

You refer to Internode 'losing the money'. Be clear on this: as I said, this affects all ISP's equally. You will see exactly the same increased latency with any other provider, at exactly the same times. Plus whatever latency their own national network (or lack thereof) may then add to it. So taking your business elsewhere to (presumably) punish Internode here would be a pretty unfortunate case of blaming the messenger. At least we do dilligently and regularly hound Telstra to fix this each time it happens.

And in terms of you saying we aren't shouting loud enough at Telstra over this; You may find this hard to believe, but its the truth: Telstra aren't very interested in what we think about this sort of thing. Our choices are to accept what they offer us to not buy it. When push comes to shove, that's it. The only way to cross the line into getting a more flexible answer in this sort of matter often is political embarassment. They do seem to respond to that.

So, yes, absolutely, do complain direct to Telstra or your local member (or preferably both) on this one, it IS their fault, and after many months of shaking the tree on this, its clear that the only way to fix it IS likely to be political agitation by your local member - so please, go for it by all means. It has often worked in the past to get Telstra to fix geographically specific issues (e.g. lack of ADSL service in specific areas) where nothing else has.

Simon

thanks for the read.

Thanks,

That explains everything. Its not really what i wanted to hear .. but oh well.

Anybody have any ideas how we can get this fixed then? im not going to go as far as approaching my local member though.

Move out of Darwin. (See, I'd go to any length) ;)

haha awesome call

C:\Documents and Settings\Matt>ping www.internode.on.net

Pinging www.internode.on.net [203.16.214.17] with 32 bytes of data:

Reply from 203.16.214.17: bytes=32 time=43ms TTL=61
Reply from 203.16.214.17: bytes=32 time=42ms TTL=61
Reply from 203.16.214.17: bytes=32 time=42ms TTL=61
Reply from 203.16.214.17: bytes=32 time=42ms TTL=61

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

My Pings are fine.. Nightcliff exchange

omg.....people complaining about latency in darwin is as bad as people compaining about lag on blackrock

btw mine seems fine - then again, i dont see the difference in wow

as for approaching local member - anyone reckon Delia Lawrie would actually know what to do or even where to start......

Movin out of darwin is good - but everywhere else is just toooo Fracking cold

Reply from 203.16.214.17: bytes=32 time=86ms TTL=60
Reply from 203.16.214.17: bytes=32 time=85ms TTL=60
Reply from 203.16.214.17: bytes=32 time=86ms TTL=60
Reply from 203.16.214.17: bytes=32 time=86ms TTL=60

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

Maybe its just (*&(*&^& Karama.....

Second time in as many months that my latency has doubled
from 45ish up to and over 100 in Source games
and anywhere up tp 250 for some BF2 servers - makes keeping a conneciton a little hard.

I am whinging but i want what i pay for.

It took 6 months of reapplying for adsl, dealing with stupid optus and telstra people and a "exchange upgrade" to get it. My favourite while asking the lady at the Telstra call centre why every where in Darwin but Karama had adsl was met with 'maybe i should move house '( stupid bitch ) - ill just pop off to the bank for another 250K+ to get another place.... :mad:

Quote from OverDrive:
Move out of Darwin. (See, I'd go to any length) ;)

Dont move to Howard Springs then, I'm on 2-way sat and my best pings are around 600....

ATM? does this mean i cant get any money out? ;)

Fine for me

C:\Documents and Settings\Steve>ping games.internode.on.net

Pinging games.internode.on.net [203.26.94.189] with 32 bytes of data:

Reply from 203.26.94.189: bytes=32 time=46ms TTL=59
Reply from 203.26.94.189: bytes=32 time=44ms TTL=59
Reply from 203.26.94.189: bytes=32 time=44ms TTL=59
Reply from 203.26.94.189: bytes=32 time=46ms TTL=59

Ping statistics for 203.26.94.189:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 44ms, Maximum = 46ms, Average = 45ms

Quote from Bad Crispy:

It took 6 months of reapplying for adsl, dealing with stupid optus and telstra people and a "exchange upgrade" to get it. My favourite while asking the lady at the Telstra call centre why every where in Darwin but Karama had adsl was met with 'maybe i should move house '( stupid bitch ) - ill just pop off to the bank for another 250K+ to get another place.... :mad:
I don't understand - do you mean Karama has no ADSL? I lived in Livistona Rd and had ADSL over 18 months ago.

parts of karama don't, or didn't until not long ago. Knight can vouch for that.

i cant get a clear reading lowest was 48 ms on internode but then again my bro could be download his gay porn so who knows

Ive had adsl for almost 2 yrs - but the sh*t i had to go through to get it was annoying, I know insidious had fun getting it too.

It would be nice if Telstra would fix the issue