first one for the year...no need to say anything else but get those support requests in and hopefully they actually implement that permanent fix sometime soon.
Typical Latency Jump is Back
13 public posts in this discussion.
Post 2
Pinging www.internode.on.net [203.16.214.17] with 32 bytes of data:
Reply from 203.16.214.17: bytes=32 time=88ms TTL=61
Reply from 203.16.214.17: bytes=32 time=97ms TTL=61
Reply from 203.16.214.17: bytes=32 time=89ms TTL=61
Reply from 203.16.214.17: bytes=32 time=89ms TTL=61
C:\Documents and Settings\Matt>tracert www.internode.on.net
Tracing route to www.internode.on.net [203.16.214.17]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms SpeedTouch.lan [10.0.0.138]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 92 ms 118 ms 95 ms corp.internode.on.net [203.16.214.17]
Trace complete.
and was just about to go play some cs.. :(
Post 3
well it was 'sometime in february' so maybe it's busted because they are working on it?
Post 4
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=89ms TTL=61
Reply from 203.16.214.17: bytes=32 time=87ms TTL=61
Reply from 203.16.214.17: bytes=32 time=86ms TTL=61
Reply from 203.16.214.17: bytes=32 time=88ms 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 = 86ms, Maximum = 89ms, Average = 87ms
E:\Documents and Settings\Administrator>tracert www.internode.on.net
Tracing route to www.internode.on.net [203.16.214.17]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.0.55
2 88 ms 87 ms 87 ms loop0.lns1.adl2.internode.on.net [203.16.215.223]
3 92 ms 88 ms 88 ms gi0-2-8.cor1.adl2.internode.on.net [203.16.212.161]
4 91 ms 89 ms 91 ms gi0-2-2.cor2.adl2.internode.on.net [203.16.215.86]
5 95 ms 106 ms 90 ms corp.internode.on.net [203.16.214.17]
Trace complete.
Post 5
Quote from Burk:
well it was 'sometime in february' so maybe it's busted because they are working on it?
Lol as much as we want that too be true do u actually believe that?
Post 6
no, but the more i say it.. the more i might believe it
Post 7
play an MMORPG and it wont matter. :D
Post 8
True dat homie *puts fist to chest*
Post 9
Pinging internode.on.net [203.16.214.17] with 32 bytes of data:
Reply from 203.16.214.17: bytes=32 time=50ms TTL=61
Reply from 203.16.214.17: bytes=32 time=50ms TTL=61
Reply from 203.16.214.17: bytes=32 time=52ms TTL=61
Reply from 203.16.214.17: bytes=32 time=48ms 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 = 48ms, Maximum = 52ms, Average = 50ms
Fixed already?
Edit: Come to think of it, my pings have been normal the past 2 days. I'm on the City exchange, maybe only cas was affected.
Post 10
fine for me now
Post 11
my ping is still 80ms
Post 12
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Wrathlons.WRATHLON>ping internode.on.net
Pinging internode.on.net [203.16.214.17] with 32 bytes of data:
Reply from 203.16.214.17: bytes=32 time=49ms TTL=61
Reply from 203.16.214.17: bytes=32 time=43ms TTL=61
Reply from 203.16.214.17: bytes=32 time=43ms TTL=61
Reply from 203.16.214.17: bytes=32 time=44ms 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 = 43ms, Maximum = 49ms, Average = 44ms
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Wrathlons.WRATHLON>tracert internode.on.net
Tracing route to internode.on.net [203.16.214.17]
over a maximum of 30 hops:
1 <1 ms 1 ms <1 ms 192.168.0.55
2 42 ms 44 ms 43 ms loop0.lns1.adl2.internode.on.net [203.16.215.223]
3 45 ms 101 ms 54 ms gi0-2-8.cor1.adl2.internode.on.net [203.16.212.161]
4 44 ms 44 ms 46 ms gi0-2-2.cor2.adl2.internode.on.net [203.16.215.86]
5 44 ms 46 ms 45 ms corp.internode.on.net [203.16.214.17]
Trace complete.
Looks like its fixed for us here.
Post 13
https://ios.homelinux.com/smokeping/cgi-bin/smokeping.cgi?target=Internode.NodeADL
Was fixed at 2:15am this morning...