High Latency - Darwin Internode

Are any internode customers getting high pings atm.

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

C:\>

It's not just internode customers - it's all of Darwin. Thankyou Telstra - we lubs joo :-P

I am on Dodo and pings are over 100 Also i had disconnection problems this morning as well

Trace route (tracert) be more useful here.

Quote from tn1;287916:
I am on Dodo and pings are over 100 Also i had disconnection problems this morning as well
me too, around 3something am?

Ok can anybody who is a node customer - please log a support ticket as Node generally only acts if they recieve 5 tickets from different customers. Then hopefully Telstra will fix up the routing issue again.

im on it, they probably still remember me from last time :P

if anyone was looking Internode Online Support

Your ticket has been
assigned an ID of [ticket.internode.com.au #579217].

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

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.1.254
2 1 ms 1 ms 1 ms 192.168.0.1
3 134 ms 610 ms 415 ms loop0.lns1.adl2.internode.on.net [203.16.215.223
]
4 91 ms 90 ms 91 ms v14.cor3.adl2.internode.on.net [203.16.212.254]

5 90 ms 92 ms 91 ms corp.internode.on.net [203.16.214.17]

Trace complete.

Support request 579222 submitted.

Support request 579272 submitted.

Support request 579336 submitted

There is progress:

Thanks for your support request. We have had other reports of high latency in the North Territory, and it appears that the known NT latency problem may have occured. We will log a fault with Telstra and report back as soon as we have any update.

Kind regards,
Gareth
Customer Support Officer

ditto here - hopefully it will be frackin shortly

Quote from morbeous;287951:
There is progress:

Thanks for your support request. We have had other reports of high latency in the North Territory, and it appears that the known NT latency problem may have occured. We will log a fault with Telstra and report back as soon as we have any update.

Kind regards,
Gareth
Customer Support Officer

I got the same one :)

Looks like the latency is in the comindico network from my tracert

tracert telstra.com

Tracing route to telstra.com [144.135.19.10]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 124-243-142-10.static[124.243.142.10]
2 89 ms 91 ms 92 ms loop60.dsl.comindico.com.au [203.194.30.234]
3 90 ms 91 ms 90 ms ge8-0-0.cor02-waym-adl.comindico.com.au[203.220.236.60]
4 113 ms 112 ms 113 ms ge4-0-0.cor01-waym-adl.comindico.com.au [203.220.236.209]
5 112 ms 112 ms 112 ms pos2-1.cor02-kent-syd.comindico.com.au [203.194.1.21]
6 111 ms 113 ms 112 ms ge6-2.bdr03-kent-syd.comindico.com.au [203.194.28.249]
7 114 ms 113 ms 112 ms pos5-1-0.sn1.optus.com.au [202.139.18.165]
8 113 ms 113 ms 112 ms 61.88.221.135
9 113 ms 112 ms 112 ms gigabitethernet4-3.ken12.Sydney.telstra.net [139.130.2.65]
10 112 ms 112 ms 112 ms TenGigabitEthernet8-1.pit1.Sydney.telstra.net [203.50.20.39]
11 114 ms 112 ms 113 ms pitt-tcom-r01 [139.130.185.254]
12 147 ms 114 ms 112 ms 144.135.19.84
13 114 ms 116 ms 112 ms 144.135.19.10

Trace complete.

me thinks its the same problem as b4, changing our route's,switching,ports and corridors, last time Telstra had to rebuild the ports....

Trace internode.on.net; Start time 12/03/06 17:38:21
Tracing route to 203.16.214.17
50 bytes from 203.16.214.17: time=100 ms
Hop Avg Diff Address
1 1 1 192.168.x.x
2 98 97 203.16.215.216 loop0.lns1.adl4.internode.on.net
3 95 -3 203.16.213.172 vl13.cor1.adl4.internode.on.net
4 153 58 203.16.214.17 corp.internode.on.net
End time 12/03/06 17:38:31
host reached

Quote from Dw_PaSSion;288001:
last time Telstra had to rebuild the ports....

Its happening to a lot of people; so all the ports went faulty in all the exchanges in NT at the same time. Not likely

Quote from RakeR;288011:
Its happening to a lot of people; so all the ports went faulty in all the exchanges in NT at the same time. Not likely

Keith as much as I dont like to jump on the bandwagon ..

this particular problem, be it high latency. has always been a telstra problem .. Routes being sent around the eastern board.

However if it isnt a telstra problem id be surprised. :)

Although I think it is a Telstra problem, I agree with Raker. I don't think it is a problem that requires a rebuild of the ports. I reckon it is the old 'rerouting around the eastern board' problem.

All Im saying is on the routes that Ive seen, Telstra network isnt involved as there is other networks in play now. Optus, AGILE, Comindico just to name a few that dont pass though Telstra network.

So it maybe one of these.

I think most are just speaking from past experiences. and from what I understand there is 1 "pipe" into darwin, that is telstra?

either way its not working.. it could be the telstra problem it could be somthing else but 98% of the time its the same issue.. with the telstra link via Alice springs.

From what I understand node uses telstra's network to get to and leave darwin, so how can node be effected by other carriers.

Telstra does it again.

Sure but T3 shares, they are good, just like T2.

Lol.

It appears to be fixed

C:\Documents and Settings\Mark>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=60
Reply from 203.16.214.17: bytes=32 time=44ms TTL=60
Reply from 203.16.214.17: bytes=32 time=46ms 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 = 44ms, Maximum = 46ms, Average = 45ms

C:\Documents and Settings\Mark>

wooohooo - this looks a bit weird though? something must be wrong with my computer
D:\Documents and Settings\Administrator>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=6ms TTL=59
Reply from 203.16.214.17: bytes=32 time=6ms TTL=59
Reply from 203.16.214.17: bytes=32 time=48ms TTL=59
Reply from 203.16.214.17: bytes=32 time=48ms 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 = 6ms, Maximum = 48ms, Average = 27ms

My hat goes off to Internode and Telstra. At least when it happens Telstra is getting onto it much more quickly nowadays.

good work node + telstra

I think it was based on the number of support tickets lodged - which instigated the prompt action. Thanks to all who submitted a support request.

they would of seen my TT and thought not him again :P

last time i was all over them like a fat kid on a cup cake, i dont think they wanted any of that !!

credit where credits due, well done to T & Node for rectifying over the weekend

Great Work Guys... my adsl with node has been chugging a bit latetly.... hopefully this is now fixed... will check it out when I get home!

average of 45ms over 100 pings

all smiling all dancing low pings again.

must send somebloke at Node a thankyou email
Also due to the fact that we all noticed it and all sent in Requests on the weekend it got fixed a lot quicker than last time - thank the gods ;)

edit 44ms - i must be closer the the exchange than you :D