Ey, i'm on Netspace ADSL and have been gettin shitty pings all day:
Pinging games.internode.on.net [203.26.94.189] with 32 bytes of data:
Reply from 203.26.94.189: bytes=32 time=359ms TTL=60 Reply from 203.26.94.189: bytes=32 time=227ms TTL=60 Reply from 203.26.94.189: bytes=32 time=160ms TTL=60 Reply from 203.26.94.189: bytes=32 time=170ms TTL=60
Pinging games.internode.on.net [203.26.94.189] with 32 bytes of data:
Reply from 203.26.94.189: bytes=32 time=59ms TTL=60 Reply from 203.26.94.189: bytes=32 time=527ms TTL=60 Reply from 203.26.94.189: bytes=32 time=360ms TTL=60 Reply from 203.26.94.189: bytes=32 time=50ms TTL=60
As u can see there is nothing stable about them. Could anyone on ADSL (any ISP in Darwin but preferably Netspace) post their pings to the above site and some others if u want.
mmmmk this has been goin since this morning some time. Jono when u say node is buggered are u talkin pings im getting or the "usual" 100ms pings we often see here.
Nah more than that mate, like 200-300ish+ big difference.
It all seems good now. 8)
Nope I'll correct that - they are still buggered :D
Quote: Pinging games.internode.on.net [203.26.94.189] with 32 bytes of data:
Reply from 203.26.94.189: bytes=32 time=194ms TTL=61 Reply from 203.26.94.189: bytes=32 time=343ms TTL=61 Reply from 203.26.94.189: bytes=32 time=318ms TTL=61 Reply from 203.26.94.189: bytes=32 time=236ms 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 = 194ms, Maximum = 343ms, Average = 272ms
Quote: 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 423 ms 404 ms 287 ms loop0.cirrus.internode.on.net [203.16.215.223] 3 107 ms 109 ms 100 ms gi0-2-8.cor1.adl2.internode.on.net [203.16.212.161] 4 197 ms 176 ms 213 ms gig0-2-2.cor1.adl1.agile.on.net [203.16.215.94]
5 249 ms 285 ms 302 ms games.internode.on.net [203.26.94.189]
Just after midnight last night all Darwin pings rose by approx 200ms - this has happened before and we ALL know there is only one company to blame when all ISP's ADSL traffic is screwed...
holds... holds... i tell the dude getting high pings ... he say update windows... :shock: call microsoft.. i was like dude wtf... its got to do with the internet not windows... i says know lots of other people with high pings.. so he tell me to tell them to update windows..
holds... holds... i tell the dude getting high pings ... he say update windows... :shock: call microsoft.. i was like dude wtf... its got to do with the internet not windows... i says know lots of other people with high pings.. so he tell me to tell them to update windows..
telstra = gay tech support...
LOL I call you stupid for even bothering to ring em :shock: :lol: :P
Quote from PlayinG ShithousE: how u ping a server like that??
From the command line (works on any decent OS):
[code:1:22d16db54e]ping servername.com.au[/code:1:22d16db54e] or [code:1:22d16db54e]ping xxx.xxx.xxx.xxx[/code:1:22d16db54e] if you have an ip address to test.
See also ping /? on windows, and man ping on linux/unix/OS X
Reply from 203.26.94.189: bytes=32 time=491ms TTL=48 Reply from 203.26.94.189: bytes=32 time=546ms TTL=48 Reply from 203.26.94.189: bytes=32 time=443ms TTL=48 Reply from 203.26.94.189: bytes=32 time=490ms TTL=48
:(, A little better now was getting over a 1000 last night. This is with a 512kbs adsl connection by the way.
Edit : Umm when using a download program that allow resume (as connection keeps failing) and downloading off game arena will they still detect that its free content for me or do i have to start again and click the special telstra adsl button?
Quote: Pinging games.internode.on.net [203.26.94.189] with 32 bytes of data:
Reply from 203.26.94.189: bytes=32 time=107ms TTL=45 Reply from 203.26.94.189: bytes=32 time=107ms TTL=45 Reply from 203.26.94.189: bytes=32 time=105ms TTL=45 Reply from 203.26.94.189: bytes=32 time=109ms TTL=45
Ping statistics for 203.26.94.189: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 105ms, Maximum = 109ms, Average = 107ms
i lodged a report with node and they said that they were seeing what was wrong. they said it is more than likely just a fault with the hardware thanks to good old Telstra. hope it gets fixed soon, will keep people updated if node say anything contrary to this.
Even though i'm no longer a node user, i used their support ticket system to lodge a request :lol:
Just got a response:
Quote:
Hi,
I believe the ping issue in Darwin should now be rectified. If this is not the case please let me know so I can take the appropriate steps to sort it out.
By the looks of it noting is fixed :?: So i've replied stating that.
Is it possible for Darwin to get better pings than this?
Pinging games.internode.on.net [203.26.94.189] with 32 bytes of data:
Reply from 203.26.94.189: bytes=32 time=98ms TTL=61 Reply from 203.26.94.189: bytes=32 time=98ms TTL=61 Reply from 203.26.94.189: bytes=32 time=100ms TTL=61 Reply from 203.26.94.189: bytes=32 time=99ms 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 = 98ms, Maximum = 100ms, Average = 98ms
How much better are the pings between 512 and 1500 dsl connections? (In theory faster line speed should give you lower latency)
Quote from UltraGekko: Is it possible for Darwin to get better pings than this?
Pinging games.internode.on.net [203.26.94.189] with 32 bytes of data:
Reply from 203.26.94.189: bytes=32 time=98ms TTL=61 Reply from 203.26.94.189: bytes=32 time=98ms TTL=61 Reply from 203.26.94.189: bytes=32 time=100ms TTL=61 Reply from 203.26.94.189: bytes=32 time=99ms 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 = 98ms, Maximum = 100ms, Average = 98ms
How much better are the pings between 512 and 1500 dsl connections? (In theory faster line speed should give you lower latency)
This rise has happened late say 28th of November. Been like this for a week, normal pings to internode for node customers are 50-65 .. So yes you can get better pings
I've been notified that the high pings are apparently fixed :roll:
Anyone else still gettin this? :
Pinging games.internode.on.net [203.26.94.189] with 32 bytes of data:
Reply from 203.26.94.189: bytes=32 time=97ms TTL=60 Reply from 203.26.94.189: bytes=32 time=95ms TTL=60 Reply from 203.26.94.189: bytes=32 time=99ms TTL=60 Reply from 203.26.94.189: bytes=32 time=95ms 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 = 95ms, Maximum = 99ms, Average = 96ms
Quote from addas: I've been notified that the high pings are apparently fixed :roll:
Anyone else still gettin this? :
Pinging games.internode.on.net [203.26.94.189] with 32 bytes of data:
Reply from 203.26.94.189: bytes=32 time=97ms TTL=60 Reply from 203.26.94.189: bytes=32 time=95ms TTL=60 Reply from 203.26.94.189: bytes=32 time=99ms TTL=60 Reply from 203.26.94.189: bytes=32 time=95ms 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 = 95ms, Maximum = 99ms, Average = 96ms
Well try reseting your modem.. I know mine isnt .. still sitting high, but Coco in town is back to normal on 50 ping so yeah
Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\BurkynYurkyn>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=97ms TTL=61 Reply from 203.26.94.189: bytes=32 time=98ms TTL=61 Reply from 203.26.94.189: bytes=32 time=97ms TTL=61 Reply from 203.26.94.189: bytes=32 time=99ms 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 = 97ms, Maximum = 99ms, Average = 97ms
Pings are probably skyrocketing right now (and until Mondayish) because Telstra's usage metre has been taken offline, meaning for the next 3 days people wont be charged for downloads, and are going nuts.
Cock, I'm not blaming Telstra, it's a simply fact that their cable users with not be bandwidth impaired this weekend as they'll not be charged for any data transfered.
Oh and in closing, I'll make the suggestion that you remove your "Telstra Emploeye.." signature, probably not a wise move in Darwin keeping in mind how terrible their ADSL roll-out was here. At the very least, please spell employee properly, your upstanding always helpful company wouldn't like to be promoted with bad spelling. ;)
well, telstra was originally wholly publicly owned... and it had the available funds (through the government) i doubt any other ISP has the ability to do that. although, i believe internode is beginning to :)
Pinging games.internode.on.net [203.26.94.189] with 32 bytes of data:
Reply from 203.26.94.189: bytes=32 time=56ms TTL=61 Reply from 203.26.94.189: bytes=32 time=56ms TTL=61 Reply from 203.26.94.189: bytes=32 time=53ms TTL=61 Reply from 203.26.94.189: bytes=32 time=58ms 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 = 53ms, Maximum = 58ms, Average = 55ms
Quote from rec: Pings are probably skyrocketing right now (and until Mondayish) because Telstra's usage metre has been taken offline, meaning for the next 3 days people wont be charged for downloads, and are going nuts.
Quote from UltraGekko: Pinging games.internode.on.net [203.26.94.189] with 32 bytes of data:
Reply from 203.26.94.189: bytes=32 time=56ms TTL=61 Reply from 203.26.94.189: bytes=32 time=56ms TTL=61 Reply from 203.26.94.189: bytes=32 time=53ms TTL=61 Reply from 203.26.94.189: bytes=32 time=58ms 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 = 53ms, Maximum = 58ms, Average = 55ms