Whirlpool

Hi

I am getting extremely slow speeds in Melbourne North (Somerton Exchange)

My first hop is loop0.lns10.mel6.internode.on.net, i am getting pings beween 600-1200 ms !!!

CAn anyone else ping this and also anyone else experiencing same ??

ta

Pinging loop0.lns10.mel6.internode.on.net [150.101.212.56] with 32 bytes of data:

Reply from 150.101.212.56: bytes=32 time=21ms TTL=254
Reply from 150.101.212.56: bytes=32 time=20ms TTL=254
Reply from 150.101.212.56: bytes=32 time=18ms TTL=254
Reply from 150.101.212.56: bytes=32 time=21ms TTL=254

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

That indicates an issue local to you, or congestion on your exchange/RIM.

Make sure no programs are running that could be utilising your internet connection and then re-test. If that fails then contact the tech support.

Yes, me too. Been very ugly since mid afternoon. I'm on the Somerton exchange.

Pinging loop0.lns10.mel6.internode.on.net [150.101.212.56] with 32 bytes of data

:

Reply from 150.101.212.56: bytes=32 time=2133ms TTL=251
Reply from 150.101.212.56: bytes=32 time=1768ms TTL=251
Request timed out.
Reply from 150.101.212.56: bytes=32 time=735ms TTL=251

Ping statistics for 150.101.212.56:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 735ms, Maximum = 2133ms, Average = 1545ms

tried a trace to 150.101.212.56 and seems like it is slow . Am also in melb but s/e suburbs and no issues here .

Tracing route to loop0.lns10.mel6.internode.on.net [150.101.212.56]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.254
2 26 ms 26 ms 26 ms loop0.lns10.mel4.internode.on.net [150.101.212.
2]
3 26 ms 26 ms 26 ms 150.101.212.6
4 25 ms 28 ms 28 ms gi5-2.cor2.mel6.internode.on.net [150.101.212.1
9]
5 511 ms 456 ms 356 ms loop0.lns10.mel6.internode.on.net [150.101.212.
6]

Trace complete.

Heres mine im in melbourne too I havent noticed any slowdowns at all.
Pinging 150.101.212.56 with 32 bytes of data:

Reply from 150.101.212.56: bytes=32 time=12ms TTL=254
Reply from 150.101.212.56: bytes=32 time=11ms TTL=254
Reply from 150.101.212.56: bytes=32 time=11ms TTL=254
Reply from 150.101.212.56: bytes=32 time=11ms TTL=254

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

Im also in Somerton exchange in Melbourne and have noticed a slow down. I downloaded the 100meg test and it wouldn't exceed 300kb/s, whereas before today i was around the 800kb/s.

Anyway, here are my ping results:

Pinging loop0.lns10.mel6.internode.on.net [150.101.212.56] with 32 bytes of data

:
Reply from 150.101.212.56: bytes=32 time=80ms TTL=251
Reply from 150.101.212.56: bytes=32 time=156ms TTL=251
Reply from 150.101.212.56: bytes=32 time=98ms TTL=251
Reply from 150.101.212.56: bytes=32 time=42ms TTL=251

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

Can someone explain if this is any good or not, I have no idea sorry
=)

Seems ok in east melbourne area.

i had the same problem. im on the somerton exchange. though its fixed now after 30 minutes of waiting and troubleshooting.

Seems to be okay (or at least better) now....

I am on somerton exchnage aswell , so looks like issue with somerton exchange, can an internode rep comment please

from what i know the tech support said that she had checked the outages from telstra wholesale and said that there is no outages.

OzWolfbane writes...

I am getting extremely slow speeds in Melbourne North

My brother-in-law called me around 8.30 pm saying his Internet has crapped out – unusably slow performance. He said he still had plenty of quota and wasn't shaped.

He is on the Somerton exchange. Came good around 30 minutes later, just when he was about to call Support.

better but still slow in somerton

Yeh ive noticed it is better in Somerton, but im still downloading at 300kb/s max instead of the usual 800kb/s

just wanted to know is everyone connected to tw affected or just the people that are on internode.

Might be a bit hard to tell here because this *is* the Internode forum.

TezBiAn writes...

300kb/s max instead of the usual 800kb/s

Rimmed?

I am still getting pings of 80ms to first hop, i think time to all iinet

OzWolfbane writes...

I am still getting pings of 80ms to first hop, i think time to all iinet

Have you contacted support?

I'm also on Somerton exchange in Melbourne.

This is the second time I'm noticing this, it happened about 2 months ago and all returned to normal in a couple of days, the problem might be the exchange itself.

I downloaded the 50meg test file last night and today to test but it wont go above 300kb/s, normally it's around the 800kb/s.

CrunchyNut writes...

today to test but it wont go above 300kb/s, normally it's around the 800kb/s.

At a guess sounds like Telstra has capped you to 3mbit because of backhaul congestion.

Mr1979 writes...

At a guess sounds like Telstra has capped you to 3mbit because of backhaul congestion.

Sounds about right, it's a small exchange.

Mr1979 writes...

At a guess sounds like Telstra has capped you to 3mbit because of backhaul congestion.

I suggest people call support :)

I'm also on the Somerton exchange.

Something was definitely broken yesterday for a few hours there (in the afternoon).

But the issues has been there for about a week now, up and down speeds~

Painfully slow speeds yesterday though.

Everything seems to have come good now though.

---

Known issues with this exchange:

• Connections from around 5pm each night drop, and have done so for the last few months. This affects everyone in Somerton, not just internode customers.
• There are no ports left in this exchange.
• Primus has also just installed their own DSLAMS in the somerton exchange. (so maybe they're doing something in the exchange?

Its all gone to shit again with pings of 400ms+, i suggest everyone call support or they wont do anything

Im on hold atm with tech support, something is obviously wrong with the Somerton exchange.

its happening again. i am going to call support now. very high pings at 900+ms and sites are opening very slow.

what did they say to you ?

OzWolfbane writes...

i think time to all iinet

Are you on Internode or iinet?

It might be time to upgrade your profile

/forum-user.cfm?id=23678

i called them and they said that there's a problem with the exchange. i tried with to modems and same result. though right now it seems to be working fine. 60 ping and max out when downloading.

http://advisories.internode.on.net/item/5837/

kriptik writes...

i called them and they said that there's a problem with the exchange.

did they have an ETR ? its not even on their website, you sure they weren't fobbing you off

C:\...>ping -t loop0.lns10.mel6.internode.on.net

Pinging loop0.lns10.mel6.internode.on.net [150.101.212.56] with 32 bytes of data

:

Request timed out.
Request timed out.
Reply from 150.101.212.56: bytes=32 time=3839ms TTL=254
Reply from 150.101.212.56: bytes=32 time=365ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 150.101.212.56: bytes=32 time=1053ms TTL=254
Reply from 150.101.212.56: bytes=32 time=667ms TTL=254
Reply from 150.101.212.56: bytes=32 time=386ms TTL=254
Reply from 150.101.212.56: bytes=32 time=735ms TTL=254
Reply from 150.101.212.56: bytes=32 time=177ms TTL=254
Reply from 150.101.212.56: bytes=32 time=3091ms TTL=254
Reply from 150.101.212.56: bytes=32 time=831ms TTL=254
Reply from 150.101.212.56: bytes=32 time=225ms TTL=254
Request timed out.

Ping statistics for 150.101.212.56:
Packets: Sent = 20, Received = 10, Lost = 10 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 177ms, Maximum = 3839ms, Average = 1136ms
Control-C

Yep, was working okay this afternoon, albeit slower than normal. But it seems to have kharked it altogether again now....

Pinging loop0.lns10.mel6.internode.on.net [150.101.212.56] with 32 bytes of data

:

Reply from 150.101.212.56: bytes=32 time=575ms TTL=254
Reply from 150.101.212.56: bytes=32 time=851ms TTL=254
Reply from 150.101.212.56: bytes=32 time=1374ms TTL=254
Request timed out.
Reply from 150.101.212.56: bytes=32 time=3638ms TTL=254
Reply from 150.101.212.56: bytes=32 time=1432ms TTL=254
Reply from 150.101.212.56: bytes=32 time=4391ms TTL=254
Reply from 150.101.212.56: bytes=32 time=802ms TTL=254
Reply from 150.101.212.56: bytes=32 time=894ms TTL=254
Request timed out.
Request timed out.
Reply from 150.101.212.56: bytes=32 time=319ms TTL=254
Reply from 150.101.212.56: bytes=32 time=3834ms TTL=254
Reply from 150.101.212.56: bytes=32 time=1667ms TTL=254
Reply from 150.101.212.56: bytes=32 time=1432ms TTL=254
Reply from 150.101.212.56: bytes=32 time=1355ms TTL=254
Reply from 150.101.212.56: bytes=32 time=3130ms TTL=254

Ping statistics for 150.101.212.56:
Packets: Sent = 17, Received = 14, Lost = 3 (17% loss),
Approximate round trip times in milli-seconds:
Minimum = 319ms, Maximum = 4391ms, Average = 1835ms

Blech! Lucky I wasn't planing on using it tonight...

Haklin writes...

http://advisories.internode.on.net/item/5837/

the exchange im connected to (somerton) is not on that list.

Pinging internode.on.net [203.16.214.17] with 32 bytes of da
Request timed out.
Request timed out.
Reply from 203.16.214.17: bytes=32 time=278ms TTL=59
Request timed out.
Reply from 203.16.214.17: bytes=32 time=739ms TTL=59
Reply from 203.16.214.17: bytes=32 time=3693ms TTL=59
Reply from 203.16.214.17: bytes=32 time=296ms TTL=59
Request timed out.
Request timed out.
Reply from 203.16.214.17: bytes=32 time=1519ms TTL=59
Reply from 203.16.214.17: bytes=32 time=1935ms TTL=59
Request timed out.
Request timed out.
Reply from 203.16.214.17: bytes=32 time=62ms TTL=59
Request timed out.
Reply from 203.16.214.17: bytes=32 time=2498ms TTL=59
Reply from 203.16.214.17: bytes=32 time=677ms TTL=59
Reply from 203.16.214.17: bytes=32 time=315ms TTL=59
Reply from 203.16.214.17: bytes=32 time=303ms TTL=59
Reply from 203.16.214.17: bytes=32 time=279ms TTL=59
Reply from 203.16.214.17: bytes=32 time=2624ms TTL=59
Reply from 203.16.214.17: bytes=32 time=1995ms TTL=59
Reply from 203.16.214.17: bytes=32 time=1244ms TTL=59
Reply from 203.16.214.17: bytes=32 time=796ms TTL=59
Reply from 203.16.214.17: bytes=32 time=367ms TTL=59
Reply from 203.16.214.17: bytes=32 time=342ms TTL=59
Reply from 203.16.214.17: bytes=32 time=688ms TTL=59
Reply from 203.16.214.17: bytes=32 time=2112ms TTL=59
Reply from 203.16.214.17: bytes=32 time=1408ms TTL=59
Reply from 203.16.214.17: bytes=32 time=528ms TTL=59

Ping statistics for 203.16.214.17:
Packets: Sent = 30, Received = 22, Lost = 8 (26% loss),
Approximate round trip times in milli-seconds:
Minimum = 62ms, Maximum = 3693ms, Average = 1122ms

Slow here too, Somerton Exchange, we are with Optusnet. I have noticed issues all week long, but yesterday and today has been the worst. We have logged the issue with them and have a ticket. My husband just went across the road to talk to a neighbour who has had issues in the past the same time as we have, he hasn't been online today, but was yesterday and had such bad connection issues he just turned the PC off! Let's hope the multiple calls from everyone gets the exchange looked at asap. This is not the first time we have had exchange issues, same time 2 years ago it happened, and took until February the next year for it to be resolved! All up we lost internet connection for a total 4 weeks (with the worst being 2 weeks of no connection), yeah, that was a fun time...

sweetcaro writes...

This is not the first time we have had exchange issues, same time 2 years ago it happened, and took until February the next year for it to be resolved! All up we lost internet connection for a total 4 weeks (with the worst being 2 weeks of no connection), yeah, that was a fun time...

I can imagine so...

I hope it's something very temporary, im so used to my 8Mb/s connection, I dont want that to go away :(

The guy from tech support said he's going to flag the enquiry to Telstra, so i guess it's just wait and see.

THey havent even flagged this as a fault yet, they are still waiting for more people to call in, I suggest you email as I had to wait 1hr 45mins, you call that customer service internode ??

Fingers crossed. My husband mentioned this thread in his conversation, so Optus has been made aware that it looks to be an exchange issue at Somerton, affecting many. I swear that exchange needs to be rehauled in a big way.

I didn't know you can get optus on the Somerton exchange.

yeh i thought they stopped reselling Telstra, unless you are a very old customer ?

i have two freinds that are connected with iprimus. i contacted them both they have adsl2+ speeds and they both said that there is nothing wrong with the connection and that they are maxing out on their speeds. so this means that most people that are using tw in somerton are affected except the primus users.

edit: forgot to say that they are on the somerton excange.

I didn't know that. We have been with Optusnet since moving here in June 2002. So yeah, longtime customers.

The problem is back again..

Time to call in!

yep cant get to whirlpool without timing out twice

OzWolfbane writes...

I had to wait 1hr 45mins

Did you make use of their call back service so as you didn't have to wait on hold?

I've lodged a ticket.

Only waited about 3 minutes to talk to someone. :)

We'll see how long this takes to fix..

----

Kinda impossible running a web business, on dial up speeds..

Paul Warren writes...

We'll see how long this takes to fix..

Have you got another modem to try LOL.

Paul Warren writes...

Kinda impossible running a web business, on dial up speeds..

Business must be slow if your busy posting on whirlpool and not tending to your company ;)

I put in a fault via the web to 'node last night, so they should have a fair few in the system now....

UGH! Optus told us we should be fixed now, yes, I am just zooming along here. They redid our line this morning (whatever that means), well, now, it seems worse than ever before. In a way I am glad there are a few of us experiencing issues here, in the end it will make it easier to get resolved I think. There is obviously something bodgy down at the exchange.

Test Results from Oz Broadband Speed Test
----------------------------------
Test run on 17/11/2008 @ 11:26 AM

Mirror: OptusNet
Data: 600 KB
Test Time: 31.53 secs

Your line speed is 155 kbps (0.15 Mbps).
Your download speed is 19 KB/s (0.02 MB/s).

I just did another speed test, you have to laugh. Our ADSL is slower than Dial Up right now. LOL.

Test Results from Oz Broadband Speed Test
----------------------------------
Test run on 17/11/2008 @ 11:36 AM

Mirror: OptusNet
Data: 70 KB
Test Time: 18.36 secs

Your line speed is 31 kbps (0.03 Mbps).
Your download speed is 4 KB/s (0 MB/s).

Man that's shocking, I hope they get it fixed soon, and yeh I agree – because we're all experiencing this, then that makes it a bit easier to take as you'd think the problem should be fixed soon.

Steps writes...

Business must be slow if your busy posting on whirlpool and not tending to your company ;)

I'm pretty pissed off to be honest (with the exchange problem).

Our "ebusiness" has ground to a halt today because we can't do anything that requires net access.

• Can't access orders..
• Can't access emails.
• Can't receive incoming calls, or make outgoing calls

-----------

I'll give it another hour and then I'll head down to the local Telstra shop and buy a NextG card.

-----------

Test run on 17/11/2008 @ 12:13 PM

Mirror: Internode
Data: 600 KB
Test Time: 12.28 secs

Your line speed is 398 kbps (0.4 Mbps).
Your download speed is 50 KB/s (0.05 MB/s).

Its not just slow speeds its around 50% packet loss resulting in browsing worse than dialup

i tried this with two different modems and still the same result

Anyone actually driven down to the exchange to see if the little Telstra man is there? :)

Ha, just had the same thought Paul!

Are you having better luck now? I am noticing an improvement in the last few minutes. Not fixed, but a little faster. So perhaps someone is down there.

Still nothing on the advisories page.

It's all over the shop sweetcaro..

Comes good, then dies again.

Perhaps the primus ADSL2 connections in the exchange are causing issues?

Do you think the road works that's happening near there has something to do with it?

TezBiAn writes...

Do you think the road works that's happening near there has something to do with it?

Unlikely unless they have damaged a vital cable.

TezBiAn writes...

Do you think the road works that's happening near there has something to do with it?

I was thinking that too, I dont think it can be discounted.

Back online again now......

Jesus, this is annoying!

I don't think the road works has anything to do with it, but who knows!

Paul Warren writes...

Perhaps the primus ADSL2 connections in the exchange are causing issues?

I thought that they had their own fiber from exchange

Still cruddy here. Download test shows 4kb/s. Roadworks could have cut something, who knows. Frustrated...

Just drove past the exchange and there was a Bigpond van there. But.... as I turned at the mess of an intersection there was a Telstra guy and another guy looking at something in the median strip, so hope they haven't damaged something....

I hope they fix it soon, my shows all come out on Tuesday's!!

However not to look selfish, I feel sorry for you Paul Warren, you need it to run your business, and I hope you get your net fixed before all of us :)

The median strip thing is a worry, good to know they are down there though. I have even had my 4yo daughter throw her hands up in disgust today and declare it 'ridiculous' when trying to playing some online games! Heh, copying me.

hahaha, thanks tez! :)

<sarcasm> Hey, if you guys don't mind – just let me use all the bandwidth until 6pm till warcom closes ey?

Then I'll take you all to the pub over the road from the exchange!</sarcasm>

I've already lost thousands in revenue today, and lets not talk profits ....

So if I can make a few bucks whilst the net is 'kinda working' it must be my shout!

LOL Paul! Will hold you to that! :D How close are you to the exchange? We are a fair distance, 3km+. We live near Bridgewater Road, if you jump the fence at the end of our court you're in Craigieburn in fact.

Seems better at the moment. Might be a good sign....

my net seems to be working fine right now. i think those bigpond and telstra guys i aw fixed the problem.

Hope you've been speaking to the support team Paul – would hate to think you're making noises about lost income here rather than discussing the connection issues with the ISP. ;)

sweetcaro writes...

We are a fair distance, 3km+. We live near Bridgewater Road, if you jump the fence at the end of our court you're in Craigieburn in fact.

Same with me :)

I'm in brushwood circuit.

http://maps.google.com/maps?f=q&hl=en&q=18+Brushwood+Circuit,+Victoria,+Australia&sll=37.0625,-95.677068&sspn=33.160552,64.511719&layer=&ie=UTF8&z=16&ll=-37.610543,144.919689&spn=0.008091,0.01575&om=1&iwloc=addr

Brendan. writes...

Hope you've been speaking to the support team Paul

Yep, twice.

Nothing they can do at all.

Other than lodge faults with TLS and wait.... And wait...

paul u live only a few streets away from my residence. and on the same rim according to adsl2 exchanges.
i wanted to ask something . do u have a 8mb connection and if so are you capped at 3mb

Still major issues here, no change.

Test Results from Oz Broadband Speed Test
----------------------------------
Test run on 17/11/2008 @ 06:37 PM

Mirror: OptusNet
Data: 70 KB
Test Time: 18.78 secs

Your line speed is 31 kbps (0.03 Mbps).
Your download speed is 4 KB/s (0 MB/s).

We're close by, we are in Siret Court, opposite side of Bridgewater Road. Is your Internet ok now?

im maxing out with my connection. heres a ping request:

Pinging internode.on.net [203.16.214.17] with 32 bytes of data:
Reply from 203.16.214.17: bytes=32 time=90ms TTL=59
Reply from 203.16.214.17: bytes=32 time=92ms TTL=59
Reply from 203.16.214.17: bytes=32 time=65ms TTL=59
Reply from 203.16.214.17: bytes=32 time=63ms 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 = 63ms, Maximum = 92ms, Average = 77ms

and a oz speedtest

Test Results from Oz Broadband Speed Test
----------------------------------
Test run on 17/11/2008 @ 07:00 PM

Mirror: Internode
Data: 600 KB
Test Time: 4.99 secs

Your line speed is 979 kbps (0.98 Mbps).
Your download speed is 122 KB/s (0.12 MB/s).

<knockonwood> all ok now...

Paul you really need prepaid 3G backup or something man,

OzWolfbane writes...

Paul you really need prepaid 3G backup or something man,

I'm surprised a business as large as his doesn't already have a backup!

Seems to be back up, but I don't think I'm getting anywhere near the same speed I was seeing before this mess. What are the rest of you seeing ?
Are we capped to 300kB now ?
And did anyone actually get any response/explanation from Internode ? 22 Hours since I lodged my ticket and not even a "Yes, there is a problem at the exchange" response. Just silence ?

Zero Cool writes...

I'm surprised a business as large as his doesn't already have a backup!

This is the first time in close to uhm, 5 years~ being with Internode, I've ever had an issue like this (that has lasted this long also).

I'm heading out tomorrow morning though to buy a NextG card.

You can get pre-paid can't you?

Roxburgh Park + Somerton here also.

I emailed Internode late this afternoon with the intent to call it in when I got home later, but of course it's fixed itself up. :)

The behaviour I saw here was more like clearing a backlog: things would flow fine for a couple of seconds, pause for a couple of seconds, then flow again (with the outstanding packets flooding in/catching up at this point). Imagine boxes on a production line banking up at a door which raises and lowers every couple of seconds... when the door raises the backlog is cleared but as soon as it closes they're banking up again. Everything gets through eventually, it's just a very inefficient and choppy way of doing it.

Maximum pings were past 3000ms at times and never went below about 400 (they're now 25). Average download speeds were also in the dog house. This is a 1500/256 ADSL1 link.

I did see a Telstra station wagon at the exchange when I went past about 7:15pm.

These two advisories may be related, or coincidental...

http://advisories.internode.on.net/item/5830/
"DSL Interruptions in NSW and VIC"

http://advisories.internode.on.net/item/5822/
"Possible latency and congestion for ACT, Victorian and Tasmanian Customers"

Rama66 writes...

And did anyone actually get any response/explanation from Internode ? 22 Hours since I lodged my ticket and not even a "Yes, there is a problem at the exchange" response. Just silence ?

Was it a phone or email ticket? Don't expect a prompt response to email, I only submitted mine online because I wanted to include some technical details, but I was also intending to follow it up with a call to expedite things.

rowan250 writes...

http://advisories.internode.on.net/item/5822/
"Possible latency and congestion for ACT, Victorian and Tasmanian Customers"

Whoops, ignore this one, just realised it's from last week

And today is not Tuesday

Its far from fixed, its just better...its not fixed when you get 100ms pings to your first hop

Pinging loop0.lns10.mel4.internode.on.net [150.101.212.32] with 32 bytes of data

:

Reply from 150.101.212.32: bytes=32 time=91ms TTL=254
Reply from 150.101.212.32: bytes=32 time=48ms TTL=254
Reply from 150.101.212.32: bytes=32 time=86ms TTL=254
Reply from 150.101.212.32: bytes=32 time=55ms TTL=254

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

sweetcaro writes...

How close are you to the exchange? We are a fair distance, 3km+. We live near Bridgewater Road, if you jump the fence at the end of our court you're in Craigieburn in fact.

I'm also right on the border, a couple of streets west of Bridgewater Road...

I know someone ON Bridgewater Road [Craigieburn] who has access to ADSL2+, which is presumably coming off the Craigieburn exchange. In Roxburgh Park we're off a RIM hanging off the Somerton exchange (possibly the box near the primary school?), so if I understand correctly my neighbours 20m away in Craigieburn can get ADSL2+, while I'm stuck with ADSL1+ in Roxburgh Park. Maybe I should ask if I can stick a wireless access point in there. :D

(I wonder if Telstra would consider 'crossing the boundary' as it were, I do recall in my previous life as a small ISP that we had half our lines run from a different exchange – or at least path – so there was some redundancy.)

OzWolfbane writes...

Its far from fixed, its just better...its not fixed when you get 100ms pings to your first hop

I just gave Internode a quick call, Telstra has reported to them that the fault started at 2:30pm (I presume this is when it was 'officially recognised' rather than traced back to the actual time of first fault – I was having problems in the morning) and was fixed at 6:36pm

If you think there's something Not Quite Right<tm> then let Internode know.

$#&#!$... it's happening again...

PING www.internode.on.net (203.16.214.27): 56 data bytes
64 bytes from 203.16.214.27: icmp_seq=0 ttl=60 time=2642.235 ms
64 bytes from 203.16.214.27: icmp_seq=1 ttl=60 time=1772.782 ms
64 bytes from 203.16.214.27: icmp_seq=2 ttl=60 time=1051.229 ms
64 bytes from 203.16.214.27: icmp_seq=3 ttl=60 time=620.444 ms
64 bytes from 203.16.214.27: icmp_seq=4 ttl=60 time=1819.398 ms
64 bytes from 203.16.214.27: icmp_seq=5 ttl=60 time=1263.641 ms
64 bytes from 203.16.214.27: icmp_seq=6 ttl=60 time=286.634 ms
64 bytes from 203.16.214.27: icmp_seq=7 ttl=60 time=2247.329 ms
64 bytes from 203.16.214.27: icmp_seq=8 ttl=60 time=5101.845 ms
64 bytes from 203.16.214.27: icmp_seq=9 ttl=60 time=4131.240 ms
64 bytes from 203.16.214.27: icmp_seq=10 ttl=60 time=3169.097 ms
64 bytes from 203.16.214.27: icmp_seq=11 ttl=60 time=3029.647 ms
64 bytes from 203.16.214.27: icmp_seq=12 ttl=60 time=3689.725 ms
64 bytes from 203.16.214.27: icmp_seq=13 ttl=60 time=4013.708 ms
64 bytes from 203.16.214.27: icmp_seq=14 ttl=60 time=4006.956 ms
64 bytes from 203.16.214.27: icmp_seq=15 ttl=60 time=2986.776 ms
64 bytes from 203.16.214.27: icmp_seq=16 ttl=60 time=2013.365 ms
64 bytes from 203.16.214.27: icmp_seq=17 ttl=60 time=1033.805 ms
64 bytes from 203.16.214.27: icmp_seq=18 ttl=60 time=93.914 ms

rowan250 writes...

If you think there's something Not Quite Right<tm>

Guys if you dont get around 20ms in first hop then its not fixed

There is your right:

Pinging loop0.lns10.mel4.internode.on.net [150.101.212.32] with 32 bytes of data

:

Reply from 150.101.212.32: bytes=32 time=998ms TTL=254
Reply from 150.101.212.32: bytes=32 time=881ms TTL=254
Reply from 150.101.212.32: bytes=32 time=958ms TTL=254
Reply from 150.101.212.32: bytes=32 time=1046ms TTL=254
Reply from 150.101.212.32: bytes=32 time=1055ms TTL=254
Reply from 150.101.212.32: bytes=32 time=1198ms TTL=254
Reply from 150.101.212.32: bytes=32 time=1125ms TTL=254
Reply from 150.101.212.32: bytes=32 time=1236ms TTL=254
Reply from 150.101.212.32: bytes=32 time=1208ms TTL=254
Reply from 150.101.212.32: bytes=32 time=999ms TTL=254
Reply from 150.101.212.32: bytes=32 time=1039ms TTL=254
Reply from 150.101.212.32: bytes=32 time=970ms TTL=254
Reply from 150.101.212.32: bytes=32 time=846ms TTL=254
Reply from 150.101.212.32: bytes=32 time=728ms TTL=254
Reply from 150.101.212.32: bytes=32 time=732ms TTL=254

Ping statistics for 150.101.212.32:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 728ms, Maximum = 1236ms, Average = 1001ms
Control-C

Just noticed this thread...Pinging internode game servers

1 <1 ms <1 ms <1 ms 10.0.0.1
2 184 ms 183 ms 181 ms loop0.lns10.mel6.internode.on.net [150.101.212.56]
3 184 ms 186 ms 189 ms vlan113.cor2.mel6.internode.on.net [150.101.210.30]
4 174 ms 162 ms 188 ms gi5-2.cor3.mel4.internode.on.net [150.101.212.136]
5 199 ms 200 ms 197 ms pos3-0.bdr2.adl2.internode.on.net [203.16.212.129]
6 192 ms 183 ms 174 ms po3.cor1.adl6.internode.on.net [203.16.212.153]
7 176 ms 179 ms 176 ms 203.26.94.70

Ive been trying to play some games tonight and its impossible...IS this a node issue or telstra? Im on Maindstone exchange...

OzWolfbane writes...

Guys if you dont get around 20ms in first hop then its not fixed

I was just relaying the info that Internode have and pointed out that if it's NOT fixed to call them so they can nudge Telstra and tell them to do the job properly... Internode support are not mind readers. :)

From my POV things are playing up again, at times even more badly than I noticed earlier today. I'm going to leave it for tonight and give them a call tomorrow.

mine is still good. around 90 ping

PING www.internode.on.net (203.16.214.27): 56 data bytes
64 bytes from 203.16.214.27: icmp_seq=0 ttl=60 time=303.472 ms
64 bytes from 203.16.214.27: icmp_seq=1 ttl=60 time=225.674 ms
64 bytes from 203.16.214.27: icmp_seq=2 ttl=60 time=1043.801 ms
64 bytes from 203.16.214.27: icmp_seq=3 ttl=60 time=81.229 ms
64 bytes from 203.16.214.27: icmp_seq=4 ttl=60 time=1277.649 ms
64 bytes from 203.16.214.27: icmp_seq=5 ttl=60 time=299.386 ms
64 bytes from 203.16.214.27: icmp_seq=6 ttl=60 time=868.911 ms
64 bytes from 203.16.214.27: icmp_seq=7 ttl=60 time=446.380 ms
[.]
64 bytes from 203.16.214.27: icmp_seq=44 ttl=60 time=206.582 ms
64 bytes from 203.16.214.27: icmp_seq=45 ttl=60 time=94.943 ms
64 bytes from 203.16.214.27: icmp_seq=46 ttl=60 time=51.914 ms
64 bytes from 203.16.214.27: icmp_seq=47 ttl=60 time=138.995 ms
64 bytes from 203.16.214.27: icmp_seq=48 ttl=60 time=115.811 ms
64 bytes from 203.16.214.27: icmp_seq=49 ttl=60 time=78.351 ms

--- www.internode.on.net ping statistics ---
50 packets transmitted, 49 packets received, 2% packet loss
round-trip min/avg/max/stddev = 33.902/588.284/2191.541/646.331 ms

It's all over the place. Doing some pings a few mins ago I saw round trip times in excess of 5000ms (5 seconds!)

right now im getting good results.

Pinging internode.on.net [203.16.214.17] with 32 bytes of data:
Reply from 203.16.214.17: bytes=32 time=66ms TTL=59
Reply from 203.16.214.17: bytes=32 time=74ms TTL=59
Reply from 203.16.214.17: bytes=32 time=69ms TTL=59
Reply from 203.16.214.17: bytes=32 time=56ms 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 = 56ms, Maximum = 74ms, Average = 66ms

Woah. What's happening in Melbourne tonight?

Tracing route to games.on.net [203.26.94.250]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway [192.168.1.254]
2 154 ms 162 ms 160 ms loop0.lns10.mel6.internode.on.net [150.101.212.56]
3 170 ms 176 ms 176 ms vlan113.cor2.mel6.internode.on.net [150.101.210.30]
4 185 ms 186 ms 182 ms gi5-2.cor3.mel4.internode.on.net [150.101.212.136]
5 170 ms 170 ms 175 ms pos3-0.bdr2.adl2.internode.on.net [203.16.212.129]
6 175 ms 180 ms 172 ms gi1-1.cor3.adl2.internode.on.net [203.16.215.40]
7 166 ms 165 ms 168 ms ows1.cmg.internode.on.net [203.26.94.250]

Trace complete.

[Edit: Heidelberg exchange]

I just got a text message from Internode saying Telstra confirms internet speed issues on SOMERTON Exchange are now resolved.

Bull$hit they are!

Pinging internode.on.net [203.16.214.17] with 32 bytes of data:
Reply from 203.16.214.17: bytes=32 time=169ms TTL=58
Reply from 203.16.214.17: bytes=32 time=216ms TTL=58
Reply from 203.16.214.17: bytes=32 time=218ms TTL=58
Reply from 203.16.214.17: bytes=32 time=207ms TTL=58

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

Im downloading at 200kb/s, alot better than yesterday but nowhere near the 800 i normally get.

Going to give them a call now.

The issue IS NOT resolved.

Surely internode can do more than they're currently doing about this?

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

Reply from 203.16.214.17: bytes=32 time=177ms TTL=58
Reply from 203.16.214.17: bytes=32 time=198ms TTL=58
Reply from 203.16.214.17: bytes=32 time=224ms TTL=58
Reply from 203.16.214.17: bytes=32 time=219ms TTL=58

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

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

Reply from 203.16.214.17: bytes=32 time=177ms TTL=58
Reply from 203.16.214.17: bytes=32 time=198ms TTL=58
Reply from 203.16.214.17: bytes=32 time=224ms TTL=58
Reply from 203.16.214.17: bytes=32 time=219ms TTL=58

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

Paul Warren writes...

You can get pre-paid can't you?

No, Telstra have whats called a casual plan, but its a min of 6 months, and be prepared to pay upto $100 a month for it not including the hardware!

Looking normal again this morning... touchwood...

PING www.internode.on.net (203.16.214.27): 56 data bytes
64 bytes from 203.16.214.27: icmp_seq=0 ttl=59 time=24.578 ms
64 bytes from 203.16.214.27: icmp_seq=1 ttl=59 time=25.493 ms
64 bytes from 203.16.214.27: icmp_seq=2 ttl=59 time=24.969 ms
64 bytes from 203.16.214.27: icmp_seq=3 ttl=59 time=23.720 ms
64 bytes from 203.16.214.27: icmp_seq=4 ttl=59 time=24.059 ms
64 bytes from 203.16.214.27: icmp_seq=5 ttl=59 time=23.757 ms
64 bytes from 203.16.214.27: icmp_seq=6 ttl=59 time=24.023 ms
64 bytes from 203.16.214.27: icmp_seq=7 ttl=59 time=24.446 ms
64 bytes from 203.16.214.27: icmp_seq=8 ttl=59 time=23.614 ms
64 bytes from 203.16.214.27: icmp_seq=9 ttl=59 time=24.062 ms

--- www.internode.on.net ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 23.614/24.272/25.493/0.571 ms

i am receiving these shocking results:

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 didnt expect this from node

PING www.internode.on.net (203.16.214.27): 56 data bytes
64 bytes from 203.16.214.27: icmp_seq=0 ttl=59 time=3268.030 ms
64 bytes from 203.16.214.27: icmp_seq=1 ttl=59 time=2230.041 ms
64 bytes from 203.16.214.27: icmp_seq=2 ttl=59 time=1222.725 ms
64 bytes from 203.16.214.27: icmp_seq=3 ttl=59 time=215.454 ms
64 bytes from 203.16.214.27: icmp_seq=4 ttl=59 time=3774.190 ms
64 bytes from 203.16.214.27: icmp_seq=5 ttl=59 time=2742.942 ms
64 bytes from 203.16.214.27: icmp_seq=6 ttl=59 time=1712.445 ms
64 bytes from 203.16.214.27: icmp_seq=7 ttl=59 time=681.665 ms
64 bytes from 203.16.214.27: icmp_seq=8 ttl=59 time=7198.980 ms
64 bytes from 203.16.214.27: icmp_seq=9 ttl=59 time=6254.062 ms
64 bytes from 203.16.214.27: icmp_seq=10 ttl=59 time=5221.911 ms
64 bytes from 203.16.214.27: icmp_seq=11 ttl=59 time=4214.548 ms
64 bytes from 203.16.214.27: icmp_seq=12 ttl=59 time=3195.994 ms
64 bytes from 203.16.214.27: icmp_seq=13 ttl=59 time=2165.561 ms
64 bytes from 203.16.214.27: icmp_seq=14 ttl=59 time=1141.817 ms
^C
--- www.internode.on.net ping statistics ---
17 packets transmitted, 15 packets received, 11% packet loss
round-trip min/avg/max/stddev = 215.454/3016.024/7198.980/1967.927 ms

The backed up production line is happening again, worst I've seen so far. 7.2 seconds round trip time.....

edit: couple of mins later and it's back to 25ms. On the phone to 'node now

Holy cow!

64 bytes from 203.16.214.27: icmp_seq=12 ttl=59 time=11858.454 ms

Nearly 12 seconds round trip time! Wow! Don't think I've ever seen RTT that large since my overloaded 28.8k analog modem days. :D

I have reported this to internode again this morning, they told me telstra reported it fixed yesterday.

They will follow up with telstra again today, I suggest people keep reporting this to internode to follow up as telstra seems to think they fixed the issue.

I'm currently at work, if some people can call internode and send them the results of their pings to the internode servers, this will give them a good idea of the enormity of the problem.

I also asked why there was no advisory and the rep said he will speak to his team leader and see what they can do.

Can a internode rep comment and take ownership of it here ?? Why is it not on your incidents website ?? They all seem to have dissapeared

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

Reply from 203.16.214.17: bytes=32 time=177ms TTL=58
Reply from 203.16.214.17: bytes=32 time=198ms TTL=58
Reply from 203.16.214.17: bytes=32 time=224ms TTL=58
Reply from 203.16.214.17: bytes=32 time=219ms TTL=58

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

Disgusting..

Im getting an average ping of 30ms now, and for the first time in 4 days, I'm downloading at 800kb/s (internode 100mb test file)

I'm not holding my breath that it'll stay like that though.

I've been running some extended pings (10 minutes) to see the min/max values... this one had my eyes popping out of my head

---