I have noticed an increase from my normal 40 to high 100+ms returns
I suggest everybody takes the time to log a job at respective ISP's to have the matter fixed.
NT Latency Jump 22/4
52 public posts in this discussion.
Post 2
no, no one has noticed :p
Post 3
Normal 40, it is a normal 65 for a friend of mine in the CBD on Internode.
Where are you and what are you using?
Post 4
yer 100ms here too, Cas exchange support request logged.
Post 5
fuck it.. 95ms
where do we log a support request unseen?
Post 6
internode online support all web based.
cant miss it.
I am Anula on Internode. normal 35-40ms returns
Post 7
Damn i get 50 at best on 512/128 the extra upload drops ya ping by that much eh? :lol:
That's 512/512 aye, out of interest what sorta pings people get on 1500/256?
I emailed my isp too, no response yet.
Post 8
Yea someone kill Unseen :P
On 1500/256 its higher than 512/512 by a good 10+ms. The sdsl plans really help in terms of ping times for people in Darwin.
I am in Nightcliff and still have ~90ms pings. *kills Telstra*
Post 9
Now Saturday 24th
Still 100+
Post 10
do i log it as non-urgent assistance??
that's the only online one i see kurt.
can u provide a link
Post 11
yes, it's non-urgent. But you put it as high priority.
Hope this isn't 100+ for our Nodeladder defence on Monday :|
Post 12
Yeah my pings on 80 from the Palmo exchange
Usually on 40. Im on 1500/256
Post 13
Support request 12185 submitted.
Post 14
whats a ping ? is it like ping pong :P
Post 15
Sure is Flam
B doing lots of it at Freedom...
Post 16
Any receive anything from node support yet?
Tis a long weekend so doubt anything will be done for a while yet :cry:
Post 17
how do i log one of those tec thingys with telstra because
i have 1500/256kps and i am getting 120ping when i get 40 normally
Post 18
its not worth submitting a fault report; this happens once a fucking month, like clockwork. its a fucking joke.
Post 19
well its not gonna get fixed if unseen is the only one complaining about it each time is it
Post 20
so how do i do it???
Post 21
Quote from Knight Of Nih:
well its not gonna get fixed if unseen is the only one complaining about it each time is it
the point is, it DOESNT GET FIXED. if it was FIXED, it wouldnt keep HAPPENING.
Post 22
well sit back and sook about it each month then
its not like theregoing to read all you dsl costomers minds to find out what the problem is and when it happens
Post 23
you dont get it do you? its a fault, caused repetetively, by telstra. if telstra wanted to fix it, it would be fixed. clearly they dont want to fix it. whining to your isp isn't going to do anything, your isp can't fix the problem. all they can do is pressure telstra to fix it. clearly, that isn't doing anything either, since this is still happening, a good six to eight months after the first time it occurred. maybe if you actually HAD dsl you'd appreciate the alarming regularity of this particular 'fault' and realise that no amount of complaining about it actually gets anything DONE.
Post 24
oi can u please stop bitching and give me some help so maybe it will not happen every month
Post 25
rmaybe you should look for a help or support link on the bigpond home page. i dunno, that'd be the logical place to start i guess. certainly makes more sense than looking on here for it.
Post 26
Quote from paladin:
[quote:4064fc40f3="Knight Of Nih"]well its not gonna get fixed if unseen is the only one complaining about it each time is it
the point is, it DOESNT GET FIXED. if it was FIXED, it wouldnt keep HAPPENING.[/quote:4064fc40f3]
From what I read in whirlpool in the internode area, it is because of the switching technology Telstra is using to back haul the data to SA.
Probalaly only have to upgrade one little bit and it would be fix, but in the mean time we have to waiting for Telstra to notive and then manually change the setting.
Will post linkage when found
Not linkage but explaination
Quote:
Darwin Pings have shot through the roof again :( what do I do?
Why does this happen?
Unfortunately due to the way Telstra route their data from Darwin to Adelaide, this happens sometimes.
How do we get it fixed?
All you need to do is log a support request here: cgi.internode.on.net/cgi-bin/support and tell us that Darwin Pings are high again, post us a traceroute to games.internode.on.net and some pings if you don't mind.
The real nitty gritty as to why this happens: courtesy of Mark Newton
Ok, a bit of background is needed to answer this.
Firstly: Inside the deep, dark innards of Telstra's ADSL network, there's a protocol called ATM. ATM is used (grudgingly) by ISPs to talk to Telstra's IGR aggregation routers. It's also used INSIDE the ADSL network to connect each individual ADSL customer to their DSLAM, and each DSLAM to the aggregating IPSN (Shasta, ERX, whatever). The Ethernet frames which your ADSL modem transmits and receives are essentially bridged over ATM.
Secondly: As blackcoffee says, there's no ADSL aggregation point in the NT, so all ADSL traffic (for all ISPs) is carried back to Adelaide. As far as Telstra's ADSL network is concerned, Darwin, Katherine and Alice Springs don't exist in their own right, they're just suburbs of Adelaide. So the ATM PVCs which link NT DSLAMs to the aggregators are interstate.
Thirdly: ATM uses a protocol called SDH for long-haul transmission. SDH is old-school telco technology. Among other things, an SDH node can detect a link failure in less than 50 mSec. SDH is usually based on a "ring" topology, so you can get from any node to any other node by going clockwise or anticlockwise around the ring. Usually it's set up to prefer the direction which hops through the fewest number of SDH nodes to get to the destination (so in a ring through Adelaide, Melbourne, Sydney, Brisbane, Cairns, Darwin and Alice Springs, traffic will ordinarily flow from Darwin to Adelaide via the "direct" anticlockwise path).
If SDH detects a link failure, it'll shunt traffic in the opposite direction around the ring to work around it. So, in the example ring described above, if the hop between (say) Darwin and Alice Springs was interrupted, within 50 mSec SDH would work out that it can go to Adelaide via Cairns, Brisbane, Sydney, Melbourne and on to Adelaide. The fact that that path involves several thousand extra kilometers, many extra SDH "hops", and an extra 100 mSec of latency doesn't matter; Having packets arrive late is better than not having them arrive at all.
The ATM cells being carried by SDH are completely unaware when this happens. They know they've left Darwin and are going towards Adelaide; They don't care how they get there, as long as they arrive. So ATM doesn't think it's a fault when this occurs.
When the fault which caused the reversal of the ring is fixed, SDH does nothing. Traffic continues to flow in whatever direction it was flowing in before the fault was rectified.
All of this means that if the direct path from Darwin to Adelaide is interrupted for more than 50 mSec, all NT ADSL traffic flows the "long way around" the ring, and will continue to flow the long way around even if the fault is corrected until someone notices and manually flips the traffic back in the other direction. SDH doesn't consider that using the long path is a bug, because SDH is primarily used to build voice services, and as long as the latency is less than the maximum permissible latency for a voice telephone call everyone is happy.
Anyway, what this all means is that occasionally traffic for all ISPs to/from the Northern Territory is slow; When one ISP complains to Telstra about the extra latency, Telstra manually reverts the links and all ISPs get magically quicker again. SDH can be configured to do that automatically, but in this instance it hasn't.
The last line is what is pissing me off
Post 27
Yeh, agreed Jeat. It's shit - automatic would be so much simpler for all concerned.. yet Telstra just don't set it up in this way. Why? because they must enjoy people getting absolutely fucking shitted off with them.
Post 28
I am pissed, cause I have had better pings on dail up. Hell people though I was on dail up time on GA in DC.
On the whole most people wouldn't notice the difference in pings, it is only the different breed called gamers that do.
Post 29
yeah that basically confirms my suspicion. someone go backhoe the link, it'll probably get fixed faster.
Post 30
no don't do that, I wouldn't trust the attitude up here for quick work.
Not Today
Not Tommorrow
Maybe next fortnight
:)
Post 31
Any got a reply from Support yet? Been a week roughly and no reply for me.
Post 32
i havent..
Post 33
yeah, i got a reply..
i'll post it when i get home..
basically said they are aware of the problem and will contact me when it's resolved.
Post 34
My ISP hasn't replied yet. Probably still confused that I had some technical jargon to back up my claims. (i gave them the link to that article by Mark Newton)
btw i'm with iiNet
Post 35
ewwww.. iiNet... what a loser!!!
Internode replied to me within 1-2 working days i think.. i'll check when i get home.
Post 36
Quote from MetalAttack:
i havent..
Maybe casue your on..... TELSTRA!!!
Post 37
Yeah got a reply a few days ago asking for some pings and traceroutes.
Post 38
yeah, i sent all mine in the support request..
makes life easier
Post 39
with the way telstra has handled this problem in the past and probably will handle it in the future, we might as well start lobbying for cable internet again :|
Post 40
Hi,
We are aware of the problems in the Northern Territory at the moment and we have lodged a fault with Telstra and are awaiting from the to rectify the issue. As soon as we get word back from Telstra you will be notified.
--
Kind regards,
Daniel Jones
_______________________________________
Internode Technical Support Team
Post 41
Yep pings still around 100. I Think I will start driving around and smash every telstra box, sub box I see and blow up a few of their exhanges every month from about the 20th of each month.
That might get their attention to fix the problem I think.
Only joking.
Or maybee.......
:twisted:
Post 42
Burk, what are you pings to the Internode servers? My are 60 or so, I was lead to believe that is as good as we can get in the NT ping wise.
GA pings are 75-80.
Xtra in NZ is 115
Post 43
are you talking in-game pings, or command line pings?
Post 44
Jeat, what exchange are you on? Those sounds like "normal" pings, gettin about 120-130 on GA and like 150+ on Xtra from Cas exchange, could just be this exchange then if u arent on it :P
Post 45
I live in the CBD, and yes in game pings. Using the command line to ping games.internode.on.net I get between 43 and 65.
Post 46
mmmm means its not afffecting everyone then is it, probably why it maybe hasn't been fixed yet? Regardless, it should have happen in the first place.
Post 47
Hmmmm, Jeat... you lucky SOB.
still getting 100+ pings command line or otherwise.
Post 48
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\GusIsInsane>tracert games.internode.on.net
Tracing route to games.internode.on.net [203.26.94.189]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 88 ms 89 ms 89 ms loop0.adsl1.adl1.internode.on.net [203.16.215.216]
3 183 ms 94 ms 90 ms gi0-2-13.cor1.adl1.internode.on.net [203.16.212.213]
4 90 ms 93 ms 90 ms games.internode.on.net [203.26.94.189]
Trace complete.
C:\Documents and Settings\GusIsInsane>
Post 49
Quote from Seqo:
Hmmmm, Jeat... you lucky SOB.
still getting 100+ pings command line or otherwise.
heh I though I was lucky til 1.30am til I actually checked my ping in game after missing rifle shots in Forgotten Hope. Yep I am up there in 90 with you guys as well.
Post 50
OMG. I'm getting 50 and 60 ping to internode.
Post 51
Oh Yeah!
C:\Documents and Settings\GusIsInsane>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=61
Reply from 203.26.94.189: bytes=32 time=45ms TTL=61
Reply from 203.26.94.189: bytes=32 time=45ms TTL=61
Reply from 203.26.94.189: bytes=32 time=46ms 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 = 45ms, Maximum = 46ms, Average = 45ms
Post 52
hey hey back to normal 4/5 .. coolies
Lockzor