shitty pings?

any one else having hassles?

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

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=90ms TTL=61
Reply from 203.16.214.17: bytes=32 time=90ms TTL=61
Reply from 203.16.214.17: bytes=32 time=211ms TTL=61
Reply from 203.16.214.17: bytes=32 time=122ms 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 = 90ms, Maximum = 211ms, Average = 128ms

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=90ms 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
Reply from 203.16.214.17: bytes=32 time=89ms 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 = 89ms, Maximum = 90ms, Average = 89ms

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=89ms TTL=61
Reply from 203.16.214.17: bytes=32 time=90ms TTL=61
Reply from 203.16.214.17: bytes=32 time=90ms TTL=61
Reply from 203.16.214.17: bytes=32 time=91ms 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 = 89ms, Maximum = 91ms, Average = 90ms

C:\Documents and Settings\aaron>

yep. Lodge those support requests.

1500/256 Netspace/Cas exchange if it matters.

Support request 701141 submitted.

We'll be back to you soon.

If you need to follow up this request later, you can either reply to the email confirmation that you should find in your mailbox, or call our helpdesk and quote your ticket number (701141).

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\matt>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=102ms TTL=56
Reply from 203.26.94.189: bytes=32 time=102ms TTL=56
Reply from 203.26.94.189: bytes=32 time=102ms TTL=56
Reply from 203.26.94.189: bytes=32 time=103ms TTL=56

Ping statistics for 203.26.94.189:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 102ms, Maximum = 103ms, Average = 102ms

C:\Documents and Settings\matt>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 billion.router [192.168.1.254]
2 99 ms 100 ms 129 ms 203.38.103.1
3 100 ms 101 ms 101 ms TenGigE0-8-0-0.fli-core1.adelaide.telstra.net [2
03.50.120.129]
4 100 ms 100 ms 101 ms GigabitEthernet0-2.way27.adelaide.telstra.net [2
03.50.119.37]
5 101 ms 101 ms 115 ms optus3.lnk.telstra.net [139.130.237.10]
6 105 ms 124 ms 103 ms ge-wan5-1.55drc76fg.optus.net.au [202.139.124.10
]
7 * * * Request timed out.
8 114 ms 103 ms 122 ms gi5-1.cor3.adl2.internode.on.net [203.16.212.155
]
9 103 ms 102 ms 102 ms games.internode.on.net [203.26.94.189]

Trace complete.

C:\Documents and Settings\matt>

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

E:\Documents and Settings\Kiza>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=45ms TTL=59
Reply from 203.16.214.17: bytes=32 time=42ms TTL=59
Reply from 203.16.214.17: bytes=32 time=40ms TTL=59
Reply from 203.16.214.17: bytes=32 time=41ms 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 = 40ms, Maximum = 45ms, Average = 42ms

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

E:\Documents and Settings\Kiza>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 modem [192.168.0.1]
2 13 ms 12 ms 11 ms loop0.lns1.per1.internode.on.net [150.101.0.195]

3 13 ms 12 ms 13 ms fa0-0-3.cor1.per1.internode.on.net [150.101.0.17
7]
4 41 ms 41 ms 41 ms pos4-0.bdr1.adl6.internode.on.net [203.16.212.17
0]
5 40 ms 40 ms 40 ms gi5-1.cor3.adl2.internode.on.net [203.16.212.155
]
6 82 ms 41 ms 41 ms internode.on.net [203.16.214.17]

Trace complete.

E:\Documents and Settings\Kiza>

net dropped out for around 2min and it's all back to normal.

yup, i'm on 45ms now

wish i was...
my pings are currently. "request timed out"

I love telstra... my adsl / phone was working fine on monday up until lunch... then *pop* Goodbye ADSL, Goodbye Phone (no dial tone).

Now I've been stuck without phone or internet (at home) for nearly two days.... I always thought that having internet problems wouldn't be too much of an issue, and i laughed at stories of folks who are "addicted" to the net.

I didn't think i actually used it that much WRONG! (just as well i can use the net at work or i would probably be hiding under my desk in the fetal position... oh wait, that's just normal for me anyway!)

Enjoy your internet goodness!

mines still up the shit

mine are up the sh1t also ping rate to node doubled for a change - will restart modem for a final check then lodge a 'fixit request' like the wind

edit 15:11
Support request 702233 submitted.

Hi Kurt,

Thanks for sending in your support request.

While the pings may have increased from what you're used to, what is actually happening that causing this to be a problem for you?

If it's gameplay, can you please supply extended pings (ping IP -n 100) and traceroutes to the game server you're using?

Kind regards,

Hmmm - havent even got to game play yet as my ping is up the shit - Insid is yours still shite aswell??

How about anyone else in Karama before i send a small parcel of abuse back thier way

Hi Aaron,

Thanks for your support request.

It looks as though there's presently an issue in the Northern Territory with regards to latency. We're investigating this with Telstra, and will be in contact when we have an update. Thank you for your patience.

Kind regards,

Matthew
Customer Support Officer

Pinging www.internode.on.net [203.16.214.17] with 32 bytes of data:

Reply from 203.16.214.17: bytes=32 time=54ms TTL=59
Reply from 203.16.214.17: bytes=32 time=59ms TTL=59
Reply from 203.16.214.17: bytes=32 time=52ms TTL=59
Reply from 203.16.214.17: bytes=32 time=52ms 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 = 52ms, Maximum = 59ms, Average = 54ms

D:\Documents and Settings\Matthew Brown>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 home.gateway [192.168.1.254]
2 50 ms 49 ms 49 ms nexthop.sa.ii.net [203.173.60.88]
3 49 ms 52 ms 50 ms gi0-1-703.ade-pipe-bdr2.ii.net [203.215.10.10]
4 52 ms 49 ms 52 ms AS4739.adelaide.pipenetworks.com [218.100.3.11]

5 52 ms 53 ms 54 ms gi5-1.cor1.adl4.internode.on.net [203.16.212.148
]
6 51 ms 52 ms 52 ms corp.internode.on.net [203.16.214.17]

Trace complete.

Internode 8Mbps (Nightcliff)

Pinging internode.on.net [203.16.214.17] with 32 bytes of data:

Reply from 203.16.214.17: bytes=32 time=101ms TTL=61
Reply from 203.16.214.17: bytes=32 time=101ms TTL=61
Reply from 203.16.214.17: bytes=32 time=101ms TTL=61
Reply from 203.16.214.17: bytes=32 time=101ms 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 = 101ms, Maximum = 101ms, Average = 101ms

im getting the above pings in cas :(

oh did i mention it doesnt stay connected either

FFS
but that could be something to do with telstra fella down the road i guess lol.

U:\>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=34ms TTL=55
Reply from 203.16.214.17: bytes=32 time=45ms TTL=55
Reply from 203.16.214.17: bytes=32 time=33ms TTL=55
Reply from 203.16.214.17: bytes=32 time=39ms TTL=55

Ping statistics for 203.16.214.17:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 45ms, Average = 37ms

This is a request to anyone in CDU - can you guys please open up the port for steam so i can have this LEET ping in Darwin please? I will only play on it 4 hours a day!!!!! and it will be beneficial for my school results as it relaxes me...

GGKTHX BI

and he will be tutoring me so i will also need access :P

Hi Aaron,

I have followed up this fault with Telstra today, they will investigate the network
paths and get back to us asap. Thank you for your patience while we investigate this
issue.

Kind regards,

Abbey
Helpdesk Team Leader

ps.....abbey sounds hawt :p

She's unlikely to be an old hag too. :p

http://www.news.com.au/adelaidenow/story/0,22606,21409458-5003680,00.html

Quote:
"The average age of people (at Internode) is 24."

or fat :S

w00t

Hi Aaron,

We have been advised by Telstra today that the network routing has been
changed.

Could you please re-run your tests and advise of your results.

If you have any further questions please reply to this email or contact the
Helpdesk on 1300 788 233.

---
Kind regards,
Ian Pilkington
Customer Support Officer

since im at work i wonder who can check for me, ah yes crispy is bumming it at home!! :p

crispy can you confirm for me?

mean while,

still getin outages

Pinging www.internode.on.net [203.16.214.17] with 32 bytes of data:

Reply from 203.16.214.17: bytes=32 time=102ms TTL=61
Reply from 203.16.214.17: bytes=32 time=105ms TTL=61
Reply from 203.16.214.17: bytes=32 time=101ms TTL=61
Reply from 203.16.214.17: bytes=32 time=102ms 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 = 101ms, Maximum = 105ms, Average = 102ms

C:\Documents and Settings\John Kornm>

did you go to 8mb korny?

Fash and I have noticed that our pings on 8MB have been increasing as well.

He's on Telstra, I'm on 'Node

Telstra is playing with the lines?

60 to 103 ? ERRR K

Got this today after i sent them an emial stating that the issue isnt fixed and its still up the sh1t - man it sucks playing games over 100 latency

Hi Kurt,

Thanks for the update.

We are aware of issues in NT at the moment, and the issue is currently being investigated by Telstra.

I've added you to the list of affected customers.

We'll be in touch as soon as we can when we have more information.

Kind regards,

Luke
Customer Support Officer

http://forums.whirlpool.net.au/forum-replies.cfm?t=708305

http://forums.whirlpool.net.au/forum-replies.cfm?t=708263

seems alot of people having issues

Pinging www.iinet.com.au [203.59.24.221] with 32 bytes of

Reply from 203.59.24.221: bytes=32 time=176ms TTL=57
Reply from 203.59.24.221: bytes=32 time=175ms TTL=57
Reply from 203.59.24.221: bytes=32 time=178ms TTL=57
Reply from 203.59.24.221: bytes=32 time=177ms TTL=57

Ping statistics for 203.59.24.221:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 175ms, Maximum = 178ms, Average = 176ms

That is really bad!

Something up with the Telstra lines?

Only took 2 weeks but as of this morning pings seem to be back to normal in the ghetttooooo YAAAAAAY - bout time too...

Havent had anythin official from the Node helpdesk but will wait and see