NT Latency gone AGAIN.... 5/6th

Happened in the last 5minutes.

and this ontop of the price hike .. hmmmm

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

C:\Documents and Settings\Kurt>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=104ms TTL=61
Reply from 203.16.214.17: bytes=32 time=104ms TTL=61
Reply from 203.16.214.17: bytes=32 time=103ms TTL=61
Reply from 203.16.214.17: bytes=32 time=103ms 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 = 103ms, Maximum = 104ms, Average = 103ms

C:\Documents and Settings\Kurt>

The latency jumps have been happening in the NT ever since I can remember - it's amazing that whatever the issue is hasn't been resolved in the last half decade.

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

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

Just posting one cos I never done it before.

Also my ping is better than unseen's.

and I don't care about rec's.

Haha. ;)

C:\Documents and Settings\lars>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=91ms TTL=61
Reply from 203.16.214.17: bytes=32 time=91ms TTL=61
Reply from 203.16.214.17: bytes=32 time=91ms 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 = 91ms, Maximum = 91ms, Average = 91ms

C:\Documents and Settings\lars>

hehehe unseen has the worst! nyer nyer =P

What the hell, just to piss people off...

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

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

Rec I told you I didn't care.

I don't care so much I'm going to ****ing kill you and steal your interwebs.

Bloody hell rec, how close to the city are ya?

1.3km from my local exchange, 5.1km from Internode servers themselves (Adelaide CBD).

3 hops once outside of my LAN, and two of those are within Internode's server farm. My house > local exchange > servers.

Reply from 210.15.254.234: bytes=32 time=11ms TTL=252
Reply from 210.15.254.234: bytes=32 time=12ms TTL=252
Reply from 210.15.254.234: bytes=32 time=13ms TTL=252
Reply from 210.15.254.234: bytes=32 time=12ms TTL=252

I'm almost close to rec's. Just need a bigger connection.

my brother sam in perth has fiber into his unit. grrrr

111 ms average here

Quote from Korny;309689:
my brother sam in perth has fiber into his unit. grrrr

Yeah but you have 111ms. No one cares about your bro, he doesn't post here. :P

Quote from rec;309692:
Yeah but you have 111ms. No one cares about your bro, he doesn't post here. :P

Just to clarify, noone cares about korny either.

Support request 817639 submitted.

this is shit

we pay for fast internet's and we get this sort of shit?

they could at least make the internet speed a constant,
dose anyone have any info why we keep getting such horrific pings?

http://forums.whirlpool.net.au/forum-replies-archive.cfm/38611.html
Quote:
Darwin Pings have shot through the roof again :( what do I do?

Why does this happen?

Unfortunately due to the way Telstra route their data from Darwin to Adelaide, this happens sometimes.

How do we get it fixed?

All you need to do is log a support request here: cgi.internode.on.net/cgi-bin/support[Image: http://forums.whirlpool.net.au/im/extlink.gif] and tell us that Darwin Pings are high again, post us a traceroute to games.internode.on.net and some pings if you don't mind.

The real nitty gritty as to why this happens: courtesy of Mark Newton

Ok, a bit of background is needed to answer this.

Firstly: Inside the deep, dark innards of Telstra's ADSL network, there's a protocol called ATM. ATM is used (grudgingly) by ISPs to talk to Telstra's IGR aggregation routers. It's also used INSIDE the ADSL network to connect each individual ADSL customer to their DSLAM, and each DSLAM to the aggregating IPSN (Shasta, ERX, whatever). The Ethernet frames which your ADSL modem transmits and receives are essentially bridged over ATM.

Secondly: As blackcoffee says, there's no ADSL aggregation point in the NT, so all ADSL traffic (for all ISPs) is carried back to Adelaide. As far as Telstra's ADSL network is concerned, Darwin, Katherine and Alice Springs don't exist in their own right, they're just suburbs of Adelaide. So the ATM PVCs which link NT DSLAMs to the aggregators are interstate.

Thirdly: ATM uses a protocol called SDH for long-haul transmission. SDH is old-school telco technology. Among other things, an SDH node can detect a link failure in less than 50 mSec. SDH is usually based on a "ring" topology, so you can get from any node to any other node by going clockwise or anticlockwise around the ring. Usually it's set up to prefer the direction which hops through the fewest number of SDH nodes to get to the destination (so in a ring through Adelaide, Melbourne, Sydney, Brisbane, Cairns, Darwin and Alice Springs, traffic will ordinarily flow from Darwin to Adelaide via the "direct" anticlockwise path).

If SDH detects a link failure, it'll shunt traffic in the opposite direction around the ring to work around it. So, in the example ring described above, if the hop between (say) Darwin and Alice Springs was interrupted, within 50 mSec SDH would work out that it can go to Adelaide via Cairns, Brisbane, Sydney, Melbourne and on to Adelaide. The fact that that path involves several thousand extra kilometers, many extra SDH "hops", and an extra 100 mSec of latency doesn't matter; Having packets arrive late is better than not having them arrive at all.

The ATM cells being carried by SDH are completely unaware when this happens. They know they've left Darwin and are going towards Adelaide; They don't care how they get there, as long as they arrive. So ATM doesn't think it's a fault when this occurs.

When the fault which caused the reversal of the ring is fixed, SDH does nothing. Traffic continues to flow in whatever direction it was flowing in before the fault was rectified.

All of this means that if the direct path from Darwin to Adelaide is interrupted for more than 50 mSec, all NT ADSL traffic flows the "long way around" the ring, and will continue to flow the long way around even if the fault is corrected until someone notices and manually flips the traffic back in the other direction. SDH doesn't consider that using the long path is a bug, because SDH is primarily used to build voice services, and as long as the latency is less than the maximum permissible latency for a voice telephone call everyone is happy.

Anyway, what this all means is that occasionally traffic for all ISPs to/from the Northern Territory is slow; When one ISP complains to Telstra about the extra latency, Telstra manually reverts the links and all ISPs get magically quicker again. SDH can be configured to do that automatically, but in this instance it hasn't.

fixed already?

Reply from 203.16.214.17: bytes=32 time=45ms TTL=60
Reply from 203.16.214.17: bytes=32 time=45ms TTL=60
Reply from 203.16.214.17: bytes=32 time=46ms TTL=60
Reply from 203.16.214.17: bytes=32 time=46ms TTL=60

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

Quote from Jay;309781:
http://forums.whirlpool.net.au/forum-replies-archive.cfm/38611.html

think this gets posted every time we start a thread ..

if people dont have it burnt into the back of there heads by now something is wrong lol...

its the noobs kurt!!!

Quote from insidious;309825:
fixed already?

Reply from 203.16.214.17: bytes=32 time=45ms TTL=60
Reply from 203.16.214.17: bytes=32 time=45ms TTL=60
Reply from 203.16.214.17: bytes=32 time=46ms TTL=60
Reply from 203.16.214.17: bytes=32 time=46ms TTL=60

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

Yep - I got an email this arvo about it being fixed. back to a decent ping ;)

Quote:
Hi Aaron,

Thank you for your support request with Internode.

As with previous times this has happened, we have contacted Telstra and it appears that they may have fixed this for us already. Please do let us know if you're still experiencing bad ping times and if possible, send along an example as you have done in the past.

For now though, it should be restored to normal.

If you have any further questions regarding this matter, please reply to this email or contact our Helpdesk by phone on 1300 788 233.

Kind regards,

Kirsty
Customer Support Officer

i would like to love Kirsty :P

still dodge here for me

Quote from addas;309901:
still dodge here for me

+1

all good here

iiNet Casuarina Exchange

must be the palmy Zimbabwe Exchange then

all good in moil

yeah i had to log a service request as im still shitty

Mines still up the sh*t as well..

average 102 ms

Cas exchange

i pinged from a telstra account today in Coonawarra road and it was getting 120 ms so its still up da shit.

all good here anula

its the 11th and im in palmo and this is still happening, im a bigpond customer and spoke to tech support on the phone, and they didnt really seem to care, he said the line speed is above the minimum amount it can be, so he cant log a job or something

I had an email today from node, saying that they wanted another Ping request sent to them, and also they have asked those with node that this is still happening too, to contact them.

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=56ms TTL=60
Reply from 203.16.214.17: bytes=32 time=57ms TTL=60
Reply from 203.16.214.17: bytes=32 time=58ms TTL=60
Reply from 203.16.214.17: bytes=32 time=57ms 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 = 56ms, Maximum = 58ms, Average = 57ms

Pings fine on Darwin CBD exchange

Mines good in wulagi

from one kurt to another - all fine here =)

Still high for me...

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

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

On Nightcliff exchange.

101 bah LAG!

here is tracerts from my comp. pls tell me if there is a different problem

Target Name: www.bigpond.com
IP: 144.135.18.32
Date/Time: 12/06/2007 9:22:47 PM

1 5 ms mygateway1.ar7 [192.168.1.1]
2 106 ms [172.18.113.1]
3 111 ms [172.18.72.14]
4 91 ms a-61-9-225-200.deploy.akamaitechnologies.com [61.9.225.200]
5 107 ms [172.18.117.225]
6 93 ms [172.18.117.229]
7 92 ms TenGigabitEthernet7-3.way21.Adelaide.telstra.net [165.228.157.77]
8 94 ms TenGigE0-8-0-0.way-core4.Adelaide.telstra.net [203.50.120.4]
9 129 ms Pos0-4-1-0.exi-core1.Melbourne.telstra.net [203.50.6.189]
10 122 ms bundle-POS1.chw-core2.Sydney.telstra.net [203.50.6.13]
11 121 ms TenGigabitEthernet8-1.pit2.Sydney.telstra.net [203.50.20.184]
12 122 ms pitt-tcom-r02 [139.130.41.70]
13 121 ms [144.135.19.84]
14 147 ms www.bigpond.com [144.135.18.32]

Target Name: www.internode.on.net
IP: 203.16.214.17
Date/Time: 12/06/2007 9:23:48 PM

1 0 ms mygateway1.ar7 [192.168.1.1]
2 92 ms [172.18.113.1]
3 92 ms [172.18.72.2]
4 92 ms a-61-9-225-199.deploy.akamaitechnologies.com [61.9.225.199]
5 91 ms TenGigabitEthernet9-3.way18.Adelaide.telstra.net [165.228.157.73]
6 92 ms GigabitEthernet0-1.way27.Adelaide.telstra.net [203.50.120.37]
7 103 ms optus3.lnk.telstra.net [139.130.237.10]
8 94 ms [61.88.221.203]
9 97 ms [61.88.221.203]
10 N/A []
11 96 ms gi1-17.cor3.adl2.internode.on.net [150.101.134.50]
12 98 ms www.internode.com [203.16.214.17]

Ping statistics for www.internode.on.net
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 98ms, Maximum = 98ms, Average = 98ms
Ping statistics for www.bigpond.com
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 147ms, Maximum = 147ms, Average = 147ms

i am using bigpond 8mb broadband, my router is a netcomm NB5plus4W

i am in the Suburb of gunn. i would really like to know if it's somethign with me personally, or if these show telstra's shitty backup routing

thanks
Gary

i'm in gunn too man, getting same 90ms-100ms pings, must be something with the palmy exchange now if the rest of darwin is back to normal.

man that sucks ass, its been like this over a week :(

I'm on Cas exchange and still sitting around 90's for ping to node. Awaiting reply from node as to when the problem will be fixed.

as soon as you find out can you post it on here, as im with bigpond, you try to tell them and they basically tell you to get nicked

no they tell you they do not care as its not in the contract to provide you with broadband speeds all the time.

if i could change to internode i could. but i dont want to waste money paying out the contract if im not going to use it

well I'm still down to 50ms on the cas exchange so don't know what the problem is.

its fixed... started being good out of no where about an hour ago

Quote from Garreh;310431:
its fixed... started being good out of no where about an hour ago

mine too - it coincided with me switching on my desktop machine for the first time in a week or so (as opposed to using my laptop - to head off the smartarses :P )... go figure =)

yea fixed for me; finally!!

Fixed.

Shame my video card failed and waiting for parts for a new system.

Off to savage it is then.

id say fixed however i now have a fluctuating ping.

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

C:\Documents and Settings\Kurt>ping www.internode.on.net -t

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

Reply from 203.16.214.17: bytes=32 time=255ms TTL=61
Reply from 203.16.214.17: bytes=32 time=60ms TTL=61
Reply from 203.16.214.17: bytes=32 time=82ms TTL=61
Reply from 203.16.214.17: bytes=32 time=122ms TTL=61
Reply from 203.16.214.17: bytes=32 time=170ms TTL=61
Reply from 203.16.214.17: bytes=32 time=211ms TTL=61
Reply from 203.16.214.17: bytes=32 time=255ms TTL=61
Reply from 203.16.214.17: bytes=32 time=59ms TTL=61
Reply from 203.16.214.17: bytes=32 time=84ms TTL=61
Reply from 203.16.214.17: bytes=32 time=128ms TTL=61
Reply from 203.16.214.17: bytes=32 time=174ms TTL=61
Reply from 203.16.214.17: bytes=32 time=223ms TTL=61
Reply from 203.16.214.17: bytes=32 time=59ms TTL=61
Reply from 203.16.214.17: bytes=32 time=59ms TTL=61
Reply from 203.16.214.17: bytes=32 time=101ms TTL=61
Reply from 203.16.214.17: bytes=32 time=141ms TTL=61
Reply from 203.16.214.17: bytes=32 time=186ms TTL=61
Reply from 203.16.214.17: bytes=32 time=228ms TTL=61
Reply from 203.16.214.17: bytes=32 time=59ms TTL=61
Reply from 203.16.214.17: bytes=32 time=59ms TTL=61
Reply from 203.16.214.17: bytes=32 time=106ms TTL=61
Reply from 203.16.214.17: bytes=32 time=224ms TTL=61
Reply from 203.16.214.17: bytes=32 time=58ms TTL=61
Reply from 203.16.214.17: bytes=32 time=61ms TTL=61

Ping statistics for 203.16.214.17:
Packets: Sent = 24, Received = 24, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 255ms, Average = 131ms

Edit all fixed. Silly non sending emails.

Woot fixed again.

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=55ms 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 = 56ms, Average = 55ms

YAYAYAYAYAYYAY :P i was so stoked when i saw it was fixed

i cant be bothered starting a new thread

seems same as last few reports

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

C:\Documents and Settings\aaron>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 xxx.xxx.x.x
2 87 ms 89 ms 89 ms loop0.lns11.adl2.internode.on.net [203.16.215.18
3]
3 195 ms 211 ms 227 ms v14.cor3.adl2.internode.on.net [203.16.212.254]

4 88 ms 89 ms 89 ms corp.internode.on.net [203.16.214.17]

Trace complete.

Damn - this seems to be happening more and more often for Darwin... firebomb telstra or move I say ;)

/lights bomb... well im 20 mtrs away from the cas exchange :P

The lovely Kirsty is on it again :D

Hi Aaron,

Thank you for your support request with Internode.

It does appear as though the problem has returned, we are currently looking in to the
matter again. It would be helpful if you know of anyone else with an Internode
connection, to get them to contact us with traceroute and ping information as well.
The sooner they contact us, the sooner we can get this fixed up again.

If you have any further questions regarding this matter, please reply to this email
or contact our Helpdesk by phone on 1300 788 233.

Kind regards,

Kirsty
Customer Support Officer
___________________________________
Internode Technical Support Team
Phone: 1300 788 233 for all support
Fax: 08 82356911
Web: http://www.internode.on.net

she still sounds hawt!!! in an electronic emaily type of way, i think its the sexy use of punctuation that does it for me :P

meh why .. they know the shit is ****ed ..

sick of lodging service requests.

Quote from insidious;312548:

C:\Documents and Settings\aaron>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 xxx.xxx.x.x
2 87 ms 89 ms 89 ms loop0.lns11.adl2.internode.on.net [203.16.215.18
3]
3 195 ms 211 ms 227 ms v14.cor3.adl2.internode.on.net [203.16.212.254]
4 88 ms 89 ms 89 ms corp.internode.on.net [203.16.214.17]

Trace complete.

4 hops from darwin or was that an edit ?? i get 11 from work? (from the router )

Tracing route to internode.on.net [203.16.214.17]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms gordon.somerville.local [*****]
2 <1 ms <1 ms <1 ms ****
3 <1 ms <1 ms <1 ms ****
4 61 ms 59 ms 59 ms *****
5 171 ms 363 ms 106 ms 172.18.71.14
6 282 ms 168 ms 126 ms 61.9.225.8
7 248 ms 230 ms 108 ms TenGigabitEthernet7-3.fli7.Adelaide.telstra.net
[139.130.94.49]
8 66 ms 59 ms 59 ms GigabitEthernet0-2.way27.Adelaide.telstra.net [2
03.50.119.37]
9 61 ms 59 ms 64 ms optus3.lnk.telstra.net [139.130.237.10]
10 62 ms 59 ms 59 ms 61.88.221.51
11 109 ms 198 ms 72 ms 61.88.221.51
12 * * * Request timed out.
13 134 ms 333 ms 504 ms gi1-17.cor1.adl6.internode.on.net [150.101.134.5
2]
14 1051 ms 1679 ms 1799 ms corp.internode.on.net [203.16.214.17]

Trace complete.

thats the spirit unseen

no edit dragon

o.0... internet hax?

i have a guess you rout through some sort of wan

.... on the was exchange?..... are you in darwin atm insid?

hahaha scared?!?

yes mate, i am in darwin

Darwin isn't a state, nor is the NT. :P

Still all fuxored in the Ghetto - thought it was just my eyesight last night - ping was fluctuating like the wind from 53 - to 85 every ping. Tonight however just plain doubled P.O.S

and i get the same thing here XR - 4 hops to supposed happiness

C:\Documents and Settings\kc>tracert internode.on.net

Tracing route to internode.on.net [203.16.214.17]
over a maximum of 30 hops:

1 * * * Request timed out.
2 84 ms 84 ms 84 ms loop0.lns10.adl6.internode.on.net [203.16.215.18
6]
3 85 ms 84 ms 84 ms vl13.cor1.adl6.internode.on.net [203.16.213.166]

4 85 ms 84 ms 84 ms internode.on.net [203.16.214.17]

Trace complete.

C:\Documents and Settings\kc>

Support request 854760 submitted.

We'll be back to you soon

Maybe they should setup a link for Darwin users on the lodge helpdesk page saying something like - "Click here if your ping is fuxored and you want us to get telstra to do something about it" - wouldnt have to do pings and tracerts and type bulk shit anymore :D

edit - Quote from rec;312724:
Darwin isn't a state, nor is the NT. :P but aleast i dont have to bath in a bucket =)

It's normal on the Nightcliff exchange.

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 44 ms 42 ms 43 ms loop0.lns10.adl6.internode.on.net [203.16.215.18
6]
3 43 ms 42 ms 44 ms vl13.cor1.adl6.internode.on.net [203.16.213.166]

4 44 ms 43 ms 42 ms corp.internode.on.net [203.16.214.17]

Trace complete.

Normal on Cas exchange also

gone again in sunny karama

start a new thread nub

this forum will have the same thread every 2 weeks if i did that

starting a new thread for each spike.... that would be interesting
side note: there are guys outside the case exchange doing some work today...
might be the cause for the latency

Or it could be one of a plethora of other pieces of work that needs doing on a weekly basis. :)

gone again in gunn

my internet went down for an hour last night
i rang my isp, they said telstra was doing maintenance down in adelaide

ping has been high for about 2 days aswell, and speed is up and down

Support request 870820 submitted.

i think they must actually wait for you to be in a war mepm!!

Or me :(

i think you have other issues there eater, this blows us out to 100 not 600 latency in game :D

seems like it that time of the month, lag spikes ftl

nightcliff.

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

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

Ditto for Stuart Park....

seems to be OK here in anula

Having massive issues

Here I was blaming my wife for downloading!

fine for me in karama, avg 43ms

bad here in palmo :(

They said they can't do anything about it unless people are getting a 3% packet loss....

Are people still having issues with their ping?

Yup yup

Internode has told me that there hasn't been many reports. If people are still having problems please report them.

On internode the support page is https://secure.internode.on.net/webtools/support

Reported, I also sent them an email about 6 days ago and have heard nothing back, I mentioned that when I submitted to there support page too.

They need a 3% loss before telstra will do anything, So I said most of internode users are games, and a higher ping means alot to these people.

Hopefully something happens :(

Anyone Still having problems?

Its been a fair wihle since it has been fixed.

not happy jan :P

yeah, it was fixed about a day, then went back to the 100's

I've put in another ticket to Internode.

havn't had a problem at all.

I still have a problem. They tell me that not many people have put a ticket in this time so it's more likely my PC :( But then it is also my laptop, my sons PC and both my routers.

its not you bud :) ..

hope that makes your day better :D

Finally got some positive communications.

Quote from Internode:
Hi Steven,

Thank you for your support request with Internode.

We have opened an ISP fault against Telstra for increased latency in NT, based on the information you and other customers in NT have provided. We hope to have this issue resolved soon.

If you have any further questions regarding this matter, please reply to this email or contact our Helpdesk by phone on 1300 788 233.

Kind regards,

its fixed
43ms

Woohoo 40ms niiice.

same