Anyone else on the cas exchange noticed the ping increase to node servers from 50ish up to 80-90 for the last few days...it's like we have the bad ping of adsl2 without any of the positives.
Ping increase
48 public posts in this discussion.
Post 2
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Administrator>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=31ms TTL=59
Reply from 203.16.214.17: bytes=32 time=30ms TTL=59
Reply from 203.16.214.17: bytes=32 time=31ms TTL=59
Reply from 203.16.214.17: bytes=32 time=30ms TTL=59
Ping statistics for 203.16.214.17:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 31ms, Average = 30ms
C:\Documents and Settings\Administrator>
Post 3
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\James Bailey>ping game.on.net
Pinging game.on.net [203.16.214.223] with 32 bytes of data:
Reply from 203.16.214.223: bytes=32 time=87ms TTL=59
Reply from 203.16.214.223: bytes=32 time=88ms TTL=59
Reply from 203.16.214.223: bytes=32 time=88ms TTL=59
Reply from 203.16.214.223: bytes=32 time=89ms TTL=59
Ping statistics for 203.16.214.223:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 87ms, Maximum = 89ms, Average = 88ms
C:\Documents and Settings\James Bailey>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=89ms TTL=59
Reply from 203.16.214.17: bytes=32 time=88ms TTL=59
Reply from 203.16.214.17: bytes=32 time=88ms TTL=59
Reply from 203.16.214.17: bytes=32 time=88ms TTL=59
Ping statistics for 203.16.214.17:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 88ms, Maximum = 89ms, Average = 88ms
Post 4
James your about a week late on noticing this - kinda why i have stopped playin BF2 for the time
and yes it has gone up from48/50 - 120 for all node servers for both me and insidious
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Bad Crispy>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=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
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
Post 5
Your not in Karama by any chance are you?
Post 6
^I noticed it a few days ago just hadn't asked anyone else about it yet.
Edit: No I'm in Wagaman
Post 7
Then yes i am blaming the cas exchange ( for a change)
This is the 2nd time in two months this has happened.
Insid is waiting for a response to 'why does my node suck' email he sent about this yesterday.
There was a post ( on GU) about how this all goes back to telstra but i cant find it right now.......
Post 8
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=48ms TTL=61
Reply from 203.16.214.17: bytes=32 time=47ms TTL=61
Reply from 203.16.214.17: bytes=32 time=47ms TTL=61
Reply from 203.16.214.17: bytes=32 time=47ms 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 = 47ms, Maximum = 48ms, Average = 47ms
Nightcliff exchange.. sorry guys.. mabey this is just an exchange problem
Post 9
Pinging games.internode.on.net [203.26.94.189] with 32 bytes of data:
Reply from 203.26.94.189: bytes=32 time=122ms TTL=61
Reply from 203.26.94.189: bytes=32 time=89ms TTL=61
Reply from 203.26.94.189: bytes=32 time=121ms TTL=61
Reply from 203.26.94.189: bytes=32 time=172ms 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 = 89ms, Maximum = 172ms, Average = 126ms
C:\Documents and Settings\Craig>
Post 10
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=44ms TTL=61
Reply from 203.26.94.189: bytes=32 time=45ms 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 = 44ms, Maximum = 46ms, Average = 45ms
Post 11
Hey knight - which part of Karama you in??
im spathe and insidious is just of kalymnos and i thought ours were bad - unless you were downloading when you did the ping.....
Post 12
dulverton crt
Post 13
yep, not wrong
this is really becoming a pain in the ass imo.
Post 14
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=43ms TTL=59
Cas exchange - malak.
Post 15
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
G:\>ping 203.16.214.17
Pinging 203.16.214.17 with 32 bytes of data:
Reply from 203.16.214.17: bytes=32 time=50ms TTL=60
Reply from 203.16.214.17: bytes=32 time=49ms TTL=60
Reply from 203.16.214.17: bytes=32 time=49ms TTL=60
Reply from 203.16.214.17: bytes=32 time=49ms 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 = 49ms, Maximum = 50ms, Average = 49ms
G:\>
Post 16
I don't have a problem from Wulagi. That's off cas exchange.
Post 17
Well after chattin at work, my mate says that there is a sub exchange in karama - so maybe its not cas after all, and just some idiot telstra person ****** up some things last week in the hood - trying to escape with his life
Post 18
I have the problem too, damn ghetto thugs leaching my bandwith....
Post 19
lol unseen, why did you do a ping from canberra? does your dsl go via casuarina? :P would suck if it did :)
Post 20
I suspect the ATM traffic is stuffed on our side of the fence this time !
/me reminds myself to ask Telstra Engineers wtf we are diffrent to Cas exchange in Karama next time I speak to 'em ????
Guys hanging off the Nightcliff and Cas Exchange had a post in here re this couple of months ago however I couldn't find it (didn't look too hard mind u) anyways Node reguarly says we all gotta log jobs for this so they can go jam it down Telstra's throat and get 'em to fix our ATM routing. Node Guys suffering this fault can u post details of your service request here so we can keep an eye on 'em all. Think we need 4 or 5 all up to get some "movement at the station".
On that note suppose I'd better dig around and log a fault tommorow as well :)
Post 21
[ticket.internode.com.au #405052] AutoReply: Latency / Ping has doubled and not gone back down
Logged last night after talking to insidious.
Did all the things they asked for in reply to his job, and sent all info to them through the online helpdesk reqest tool.
Post 22
if its not too personal
can i get a count,
who here lives in karama:
have you been experiencing broadband issues:
Provider:
speed:
Post 23
who here lives in karama: karama
have you been experiencing broadband issues: double latency - 90ms
Provider: internode
speed:1500
____________
Post 24
oh oh oh me !!!
who here lives in karama: karama
have you been experiencing broadband issues: double latency - 90ms
Provider: internode
speed:1500
____________
happiness abound =)
Post 25
who here lives in karama: karama
have you been experiencing broadband issues: double latency - 97ms (avegage)
Provider: internode
speed:1500
Post 26
who here lives in karama: Fannie Bay
have you been experiencing broadband issues: I'm capped! :grin:
Provider: wild it
speed:512
Pinging 203.16.214.223 with 32 bytes of data:
Reply from 203.16.214.223: bytes=32 time=56ms TTL=56
Reply from 203.16.214.223: bytes=32 time=53ms TTL=56
Reply from 203.16.214.223: bytes=32 time=54ms TTL=56
Reply from 203.16.214.223: bytes=32 time=55ms TTL=56
Ping statistics for 203.16.214.223:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 53ms, Maximum = 56ms, Average = 54ms
Though I'd rub it in! :grin:
Just wanted to beat cocky to it! :p
Post 27
Pinging www.internode.com [203.16.214.17] with 32 bytes of data:
Reply from 203.16.214.17: bytes=32 time=46ms TTL=57
Reply from 203.16.214.17: bytes=32 time=45ms TTL=57
Reply from 203.16.214.17: bytes=32 time=46ms TTL=57
Reply from 203.16.214.17: bytes=32 time=46ms TTL=57
Ping statistics for 203.16.214.17:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 45ms, Maximum = 46ms, Average = 45ms
Post 28
SO looking through the forum we have at least 6 unhappy campers including me in Karama, and atleast 1 in wagaman.
Is NO ONE else in darwin having any problems at all??
Post 29
nope not I
Post 30
its fixed?????
Post 31
Quote from insidious:
its fixed?????
not on my end still getting 90-91 pings to node.
Post 32
Ping happiness abound - someone must have gotten thier sh1t together and done something up here as i am now back down to 36-45 pings again =)
Post 33
Yeah Brain said he's back to normal as well but mine are still ****ed. Anyone else having continuing latency problems?
Post 34
I was hoping that between all the whinging and annoying me and insidious ( mainly insidious) have done this may have been looked at for all of us....
Post 35
mines still the same
Post 36
Yay finally fixed today...only took em a month or so
Post 37
hooray
:)
Post 38
umm okay? mines still stuffed
seriously - so pissed off about this
Post 39
which suburb - and do you know anyone else in it - need people with problems to number over 5 for telstra to listen......apparently
Post 40
I had Internode call me at work today asking about whether the ping was fixed or not. To be honest, I hadn't even checked in a week.
Post 41
Dear ,
Thank you for your email dated 26 Jun regarding your connectivity enquiry.
The DNS server information you provided does not indicate any problems. Furthermore,
we cannot guarantee ping results. As mentioned in one of our earlier correspondence,
please conduct a speed test for us to determine whether your connection speed falls
below the acceptable minimum speed for your plan.
seriously, get ****ed
Post 42
mine is still fked.... 120 ping when i was usually gettin 50-60
Post 43
still? it's been 'fked' since 29-06-2006? get a new isp man.
Post 44
Quote from fash;306018:
mine is still fked.... 120 ping when i was usually gettin 50-60
Try logging something with your ISP.
Post 45
all good here, spyware????
C:\Documents and Settings\aaron>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=43ms TTL=60
Reply from 203.16.214.17: bytes=32 time=44ms TTL=60
Reply from 203.16.214.17: bytes=32 time=44ms TTL=60
Reply from 203.16.214.17: bytes=32 time=45ms 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 = 43ms, Maximum = 45ms, Average = 44ms
Post 46
Quote from fash;306018:
mine is still fked.... 120 ping when i was usually gettin 50-60
C:\>ping internode.on.net
Pinging internode.on.net [203.16.214.17] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 203.16.214.17:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
I wouldn't complain if i were you!
Post 47
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\>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=241ms TTL=57
Reply from 203.16.214.17: bytes=32 time=56ms TTL=57
Reply from 203.16.214.17: bytes=32 time=58ms TTL=57
Reply from 203.16.214.17: bytes=32 time=58ms TTL=57
Ping statistics for 203.16.214.17:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 56ms, Maximum = 241ms, Average = 103ms
Me @ work.
Post 48
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:>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=70ms TTL=57
Reply from 203.16.214.17: bytes=32 time=72ms TTL=57
Reply from 203.16.214.17: bytes=32 time=63ms TTL=57
Reply from 203.16.214.17: bytes=32 time=80ms TTL=57
Ping statistics for 203.16.214.17:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 80ms, Average = 71ms
me while leechn