Are you having your latency fluctuate from 45ms to 100ms ?? It seems re-routing by Telstra is the issue but no-one seems to be able to fix it ! Im With Netspace - 512/128 (M) plan and have been 93ms for last 3-4 weeks, I'm CBD metro exchange. I logged job(s) with Netspace Support etc (told them it wasn't my router or PC and they still made me reset and check everything !!) This happened before and was resolve when Darwin experienced a blackout in the CBD back in Decemebr 2004 and the pings went back to 43ms !.
I have tested other ISP links (I'm a network tech for many different clients around Darwin) and doing a trace route to Adelaide results are ;
Internode 1500/256 is 45ms Connexus 256/64 is 100ms Arafura Wireless 11MB is 78ms Netspace 512/128 is 95ms
Which suggest issue is resolved with Internode and not Netspace and isn't Teltras issue alone ? It would help if Netspace acknowledged the issue instead of getting the end user to jump through hoops even after end user tell them what the issue is...
Im on Internode 1.5/256 on the Palmerston exchange, and since it was fixed what around a week ago now. I have been pinging www.on.net at 45ms.. Gaming is resulting in the low pings as well.
Yeah I have a couple mates and one client on Internode and thought it was fixed when they said so last week.. When I tested it though from home (Netspace) was still 93ms... ???
this may be stupidbut from what ive been hearing no.... i think it works like this... on 1.5 you dont get any more speed you are just able to get more data in the same period of time
I've read that the jump from 512 to 1500 will help latency albeit a small reduction. Something like 5% if your lucky. The cause of the latency doubling is not software based apparently but with the actual DSL infrastructure (its being mis-routed via QLD instead of SA and as there are more hops the long way round then.....it may be IP based, I'm not sure ?? (eg the hardware is still operational and only IP re-routes as opposed the the actual hardware switching to a alternative gateway. Not accurate but an example would be : Current 95ms Latency Route - long way round - (NT-> QLD-> NSW-> VIC) as opposed to 45ms Latency Route - straight down (NT-> SA-> VIC). Apparently the issue is with SDH which changes the route over when a failure occurs but doesn't reset back automatically. Therefore Telstra have to go an manually do it... Probably would take 10 seconds or so to actually do the task involved... I say apparently as there is now way to confirm it as all ISP's and Telstra explain they have no idea what it could possibly be ??
According to Internode, Telstra claim the routing issue has been fixed yet I'm still experiencing 90+ ms pings (I'm on Nightcliff exchange). So either Telstra is lying or we have another issue on our hands. I re-opened my ticket with Internode but the guy said he couldn't do anything because Telstra don't consider higher than normal latency a fault (go figure).
What he can do is log a speed fault with Telstra but everything about my connection is fine (no packet loss, etc) apart from the latency.
those of you on netspace, can you please send a support request (email [email]helpdesk@netspace.net.au[/email] regarding the issue) they've told me that i need more darwin netspace ppl to send in tracerts before telstra will act. my ticket number is: #1294747.
Pinging games.internode.on.net [203.26.94.189] with 32 bytes of data:
Reply from 203.26.94.189: bytes=32 time=55ms TTL=61 Reply from 203.26.94.189: bytes=32 time=56ms TTL=61 Reply from 203.26.94.189: bytes=32 time=57ms TTL=61 Reply from 203.26.94.189: bytes=32 time=55ms 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 = 55ms, Maximum = 57ms, Average = 55ms
YAY - Only took $##%#^$ 6 weeks !! LOL No word back from Netspace as to what happened either ? And nothing on their site ? While Internode posted the issue on their site and resolved it 3 weeks ago....hmmmmmm
Ping statistics for 203.26.94.189: Packets: Sent = 20, Received = 20, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 31ms, Maximum = 47ms, Average = 45ms
heh...gone again here as of this morning, presume the rest of you haev same issue. Log those support requests asap, the more they get the quicker they seem to react..i think.
PING 203.122.245.50 (203.122.245.50): 56 data bytes 64 bytes from 203.122.245.50: icmp_seq=0 ttl=125 time=100.119 ms 64 bytes from 203.122.245.50: icmp_seq=1 ttl=125 time=95.391 ms 64 bytes from 203.122.245.50: icmp_seq=2 ttl=125 time=100.635 ms 64 bytes from 203.122.245.50: icmp_seq=3 ttl=125 time=90.725 ms 64 bytes from 203.122.245.50: icmp_seq=4 ttl=125 time=95.377 ms
--- 203.122.245.50 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max/stddev = 90.725/96.449/100.635/3.634 ms
Pinging games.internode.on.net [203.26.94.189] with 32 bytes of data:
Reply from 203.26.94.189: bytes=32 time=47ms TTL=60 Reply from 203.26.94.189: bytes=32 time=47ms TTL=60 Reply from 203.26.94.189: bytes=32 time=47ms TTL=60 Reply from 203.26.94.189: bytes=32 time=47ms TTL=60
Ping statistics for 203.26.94.189: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 47ms, Maximum = 47ms, Average = 47ms
Pinging games.internode.on.net [203.26.94.189] with 32 bytes of data:
Reply from 203.26.94.189: bytes=32 time=40ms TTL=59 Reply from 203.26.94.189: bytes=32 time=40ms TTL=59 Reply from 203.26.94.189: bytes=32 time=40ms TTL=59 Reply from 203.26.94.189: bytes=32 time=41ms 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 = 40ms, Maximum = 41ms, Average = 40ms
They seemed to be fixed... Actually telstra were fixing some fiber optics last night between tennent creek and alice.. the lines were cut to fix this... that would have been the cause... was back up at 7 am this morning..