cas exchange problems?

Hi Guys,

Anyone having problems with the cas exchange latency? Specifically iinet customers.

Thanks

Node is ok 4 me.

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

Reply from 203.16.214.17: bytes=32 time=49ms TTL=60
Reply from 203.16.214.17: bytes=32 time=57ms TTL=60
Reply from 203.16.214.17: bytes=32 time=43ms TTL=60
Reply from 203.16.214.17: bytes=32 time=42ms 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 = 42ms, Maximum = 57ms, Average = 47ms

Whats the problem ment to be?

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

Had the problem for a while :( i live in Northlakes... I have tried with 3 different computers, 2 different modems (1 linksys) (1 dlink 604t)

No idea... but I personaly get high css ping for almost a month now...

try a tracert to internode

fine here, netspace but.

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

1 * * * Request timed out.
2 198 ms 74 ms 73 ms nexthop.sa.ii.net [203.173.60.88]
3 74 ms 74 ms 74 ms gi0-1-17.ade-pipe-bdr2.ii.net [203.173.60.189]
4 76 ms 75 ms 74 ms AS4739.adelaide.pipenetworks.com [218.100.3.11]

5 77 ms 75 ms 75 ms gi0-1.cor2.adl2.internode.on.net [203.16.212.152
]
6 75 ms 75 ms 76 ms corp.internode.on.net [203.16.214.17]

Trace complete.

check if there is any interfearence on the actual phoneline if there is get telstra to come fix it

Quote from shifty:
check if there is any interfearence on the actual phoneline if there is get telstra to come fix it

how would i check that? would i go to each port and have a look there? or whats the go?

While your connected to the internet (Dsl), pick up your phone reciever and listen for static.
It happens on mine as well, but i just chucked a normal line filter on and it cleared it right up.
Theres also mdb thresholds or someshit. If the line noise goes over that, then you might need telstra to check it.
But i believe that requires a specific tool.

Some modems however, in their management page, will show you the current mdb on the line.

any static in the phone line can slow down your internet, hook up your phone to the line and listen for static if there is any ring telstra and abuse them

Quote from Milenko:

But i believe that requires a specific tool.

Known as a Telstra employee.
But seriously, I had this same problem, bad pings, dropping out constantly - line had interference and it was physically pinched where the line entered our house. Fixed that and it was fine.

I am with iinet for their telephone.... does that matter? or still telstra's problem?

iinet rent telstra lines

At the end of the day it's tel$tra prob to fix, but as IINET is your phone provider you will have to get IINET to get tel$tra to look at your line, As you are not a Tel$tra customer they will tell you to call IINET.

quick check - anyone else got dodgy pings again on Cas Exchange?

Yep :(

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=99ms TTL=60
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=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 = 85ms, Maximum = 99ms, Average = 89ms

Same at Palmerston Exchange, :-(
I have reported it to Node support.

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

1 <1 ms <1 ms <1 ms 10.1.1.1
2 90 ms 91 ms 393 ms loop0.lns2.adl2.internode.on.net [203.16.215.224
]
3 683 ms 90 ms 89 ms gi0-2-8.cor1.adl5.internode.on.net [203.16.212.1
65]
4 93 ms 91 ms 111 ms games.internode.on.net [203.26.94.189]

Trace complete.

Pinging 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=93ms TTL=61
Reply from 203.16.214.17: bytes=32 time=87ms TTL=61
Reply from 203.16.214.17: bytes=32 time=203ms 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 = 87ms, Maximum = 203ms, Average = 118ms

ta will report it too :(

Quote:
Support request 363061 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 (363061).

Reported!

Thankyou for your support request with Internode.

It appears that there may be a network issue with latency in NT which is
causing high and fluctuating ping times.

Internode is currently investigating this issue.
We will contact you once we have further information.

Kind regards,

Tim *****
Customer Support Officer

is it only node?

i was getting it last night.. pissed me off....

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

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

really really good now, however i am getting drop outs :(

This problem comes and goes from each month to several months of no probs. From what I understand if the ATM TELSTRA NT network has a fault from SA it will re-route via the next available link. When the NT to Sa link is fixed TELSTRA does not automatically revert back to the original NT to SA connection.

TELSTRA has to do it manually.

Please correct me if I am wrong.

apparently (from what node told me about a year ago) telstra had fixed that problem such that "it would have happen again"

either way still borked for me.

Lataf - Yes that is how it worked, and I somehow don't think Telstra has fixed it yet :-/

They probably fixed the automatically rerouting back problem but not the reason it fails in the first place. It seems to come back to normal much more quickly now a days.

I'm having a few dropouts and slow loading times.. cant figure out why.

i get dropouts too... gives me the shits more than latency....

still borked for me here and havent really received much response from node.

I am still getting 90-12ms Pings through Palmerston exchange. Is anyone else still having problems as Node advised me it has been fixed. :-(

im with node, not haveing any problems.

still same here @ 90ms and no reply from node.

i will check tonight

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

shit pings again

It's alright for me at cas exchange. Could it be an internode only problem? I'm on iiNet.

C:\Documents and Settings\Steve>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=46ms TTL=59
Reply from 203.26.94.189: bytes=32 time=44ms TTL=59
Reply from 203.26.94.189: bytes=32 time=48ms TTL=59
Reply from 203.26.94.189: bytes=32 time=45ms TTL=59

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 = 48ms, Average = 45ms

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

Reply from 203.26.94.189: bytes=32 time=42ms TTL=58
Reply from 203.26.94.189: bytes=32 time=43ms TTL=58
Reply from 203.26.94.189: bytes=32 time=43ms TTL=58
Reply from 203.26.94.189: bytes=32 time=42ms TTL=58

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

all good for me.

cas exchange - iinet

61 ms for me :( **** iinet shits me

netspace here. doubt its isp related just happens sometimes when they "fix" it, not everyone gets done.

mmm....i love iinet atm..

pings havent gone over 45 for last week or so

same. In fact I've had good pings all year.

Ok can anyone with shit pings who are node customers please log another request ticket and we might get it fixed as node said they can not respond to one individual request.

I have the same issue here. Im with node on the Nightcliff exchange.

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

Reply from 203.26.94.189: bytes=32 time=87ms TTL=60
Reply from 203.26.94.189: bytes=32 time=86ms TTL=60
Reply from 203.26.94.189: bytes=32 time=86ms TTL=60
Reply from 203.26.94.189: bytes=32 time=87ms TTL=60

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

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

1 <1 ms <1 ms <1 ms smoothy [192.168.0.1]
2 1 ms <1 ms <1 ms RTA1320.home [192.168.1.1]
3 89 ms 88 ms 91 ms loop0.lns2.adl2.internode.on.net [203.16.215.224]
4 88 ms 87 ms 88 ms gi0-2-8.cor1.adl5.internode.on.net [203.16.212.165]
5 88 ms 89 ms 89 ms games.internode.on.net [203.26.94.189]

Trace complete.

I lodged a support request with them last week.

Got a reply -

Quote:

...
I know there was an issue a few days ago with the path the data was taking
between Darwin and Adelaide, but Telstra have since advised us that that
issue is resolved.

Since originally sending in the email, have you still got the latency
issue? Please attach pings & trace routes to your reply email.

You are on the Nightcliff exchange, and the reason why this latency occurs
across any ISP is because it was a problem with the route the traffic was
taking via Telstra's fibre optic cable. Even bigpond customers would have
had the issue.

Although there is no mention of the NT, I assume he was referring to this??? http://cgi.internode.on.net/advisories/item.html?id=3632 (wild guess)

I just sent back an email with some pings and traceroutes of most of the-mesh members scattered around town. Am about to send a link to this thread as well :P

See how we go...

Same, im with the iinet network and it seems over the last month or so my pings have doubled to internode games, I used to sit at 50 to 55ms. Now im sitting at 105ms.

PING internode.on.net (203.16.214.17) 56(84) bytes of data.
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=1 ttl=58 time=101 ms
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=2 ttl=58 time=103 ms
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=3 ttl=58 time=99.6 ms
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=4 ttl=58 time=105 ms
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=5 ttl=58 time=97.8 ms
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=6 ttl=58 time=101 ms

--- internode.on.net ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5022ms
rtt min/avg/max/mdev = 97.854/101.487/105.051/2.335 ms

Cheers
Rip

Its not the exchanges that are the problem....

I couldn't be bothered reading it all, so if someone said this then blah...

but something ( dont know what exactly ) ****s up on the way to darwin, causing the adelaide dudes to send the data another way ... a slower way, thats why they're not using it in the first place because it takes a longer route.

I don't agree this time. I'm getting great pings on Cas exchange with iiNet.

C:\Documents and Settings\Steve>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=44ms TTL=59
Reply from 203.26.94.189: bytes=32 time=43ms TTL=59
Reply from 203.26.94.189: bytes=32 time=43ms TTL=59
Reply from 203.26.94.189: bytes=32 time=43ms TTL=59

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

C:\Documents and Settings\Steve>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 192.168.0.1
2 42 ms 43 ms 43 ms nexthop.sa.ii.net [203.173.60.88]
3 44 ms 45 ms 43 ms gi0-1-17.ade-pipe-bdr2.ii.net [203.173.60.189]
4 41 ms 45 ms 43 ms AS4739.adelaide.pipenetworks.com [218.100.3.11]
5 44 ms 44 ms 44 ms gi0-1.cor2.adl2.internode.on.net 203.16.212.152]
6 46 ms 46 ms 44 ms games.internode.on.net [203.26.94.189]

Trace complete.

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

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

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

1 * * * Request timed out.
2 86 ms 85 ms 85 ms loop0.lns2.adl4.internode.on.net [203.16.215.199
]
3 85 ms 86 ms 85 ms g0-2-13.cor2.adl2.internode.on.net [203.16.213.1
72]
4 86 ms 86 ms 88 ms corp.internode.on.net [203.16.214.17]

Trace complete.

:( this sucks! im on nightcliff exchange thou.. is this were the problem lies?

Matt Im getting same sh*t pings on Palmerston Exchange, so I dont think it's just the exchange.

C:\>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=90ms TTL=60
Reply from 203.26.94.189: bytes=32 time=88ms TTL=60
Reply from 203.26.94.189: bytes=32 time=87ms TTL=60
Reply from 203.26.94.189: bytes=32 time=90ms TTL=60

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

C:\>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 10.1.1.1
2 89 ms 89 ms 89 ms loop0.lns2.adl4.internode.on.net [203.16.215.199
]
3 90 ms 89 ms 89 ms g0-2-13.cor2.adl2.internode.on.net [203.16.213.1
72]
4 91 ms 89 ms 93 ms games.internode.on.net [203.26.94.189]

Trace complete.

C:\>

FFS you guys dont ****ing listen im telling you the actuall problem, im not taking a guess.... and you all still dont listen.

Talk about arrogant.

No allan its you whos not listening.. How can people on the Cas exchange have good pings eh? did you even read longtoms post?

Quote:

I don't agree this time. I'm getting great pings on Cas exchange with iiNet.

C:\Documents and Settings\Steve>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=44ms TTL=59
Reply from 203.26.94.189: bytes=32 time=43ms TTL=59
Reply from 203.26.94.189: bytes=32 time=43ms TTL=59
Reply from 203.26.94.189: bytes=32 time=43ms TTL=59

Quote from Ph3n0m3n0n:
Its not the exchanges that are the problem....

I couldn't be bothered reading it all, so if someone said this then blah...

but something ( dont know what exactly ) ****s up on the way to darwin, causing the adelaide dudes to send the data another way ... a slower way, thats why they're not using it in the first place because it takes a longer route.
yes thats what usally happens
our packets are routed along the eastern coast

it dosnt appear to be the case this time tho

Typical telstra people say one thing they hear another.. :p

he might be on different equipment?

Alot of people on the cas exchange still have problems, palmo exchange, nightcliff, berrimah, darwin... the lot, you never know he could be on ADSL2+ equipment which is fed mainly by fibre, I dont know?

And for god sakes Matt, its ONE L in Alan .... lol

Wouldnt it show up on the traceroutes if we were getting routed through the eastern states?

I go straight to adelaide in 1 hop.

Quote from elmato:
Wouldnt it show up on the traceroutes if we were getting routed through the eastern states?

I go straight to adelaide in 1 hop.
yep
thats why it appears to be different this time

not necessarily.

Im glad you gave your reason Pala :P

not all routers decrement the TTL counter in an ip header, thus you can pass through a router without receiving an TTL exceeded response, which is how traceroute works.

happier now?

Thanks for the info paladin, so the traceroute is not showing all the hops. The question is - How can we get this fixed?.

1. Do we contact Telstra - and report a Fault ( but telstra will not see latency as a fault - as we are still connected and do not guarantee a certain QOS )

2. Keep harrasing Node - until they contact Telstra. ( see point above re QOS )

3. or put up with shit Pings and play freecell..

Quote from morbeous:

...

3. or put up with shit Pings and play freecell..

:-D

Yes well... Bf2 has been pretty unbearable.
Its a good thing soldat doesnt seem to lag ;)

BF2 is great for me :p

You can't report a fault with telstra about this. Reporting faults like this to them they/we wont do anything about, its a latency issue not a phoneline fault.

You will have to contact your ISP and ask wtf is going on and how long till it is fixed.

If you do contact your ISP they will ask you to email them several tracerts, from you and about 4 or 5 other people in the area.

yo go girl :P

Someone has raised the "beasts" !

I think I just saw a Cockroche move then ;)

Tee hee

In response "Fix your bloody ATM and with it your redundant routing via Alice properly Telscum :P"

It's worth considering that your TCP/IP is encapsulated in ATM on the way down to Adelaide and this may explain some of the single hop "traceroute" with diffrent latency symptoms.

"Google is your friend"

45 ms to games.internode.on.net from Karama

;)

Just seems strange, as when looking at all my pings, Just 1 hop to adelaide is 90ms, same with elmatos, his first hop to adelaide is 85odd ms,

Cheers
Rip

It's just taking the scenic route as per usual (not that "I" have that prob anymore ;) ) - what your not seeing in that first hop is the trip to QLD or whereever else they send wayward NT packets these days :)

I wouldn't be supprised :P

I have spoken to Node support AGAIN, and apparently they need at least 5 people to complain about the latency before they can contact telstra...
Please could anybody - Node customers experiencing this latency contact Node AGAIN and log your support request ticket in this thread and I will follow up with Node.

They need the subject to be high latency from Darwin and include a copy of tracert/ping.

My Ticket Requests are to date are:
363297
362021
372852

Support request 373690 submitted.

I included my old ticket number too #363061
So this is all the ticket numbers to inclued for you tech request people

Quote:

Same issue as
373690
363061
363297
372852
362021
373698

EDIT : Knights request number added

Please add your ticket numbers as you log them!

Support request 373698 submitted.

done

#367770 - for me

#373773 - for my old man... (different exchange)

Looks like we have met the the no of requests and now Node are contacting Telstra - to make them aware.

Hopefully Telstra will fix it again.

Thanks for lodging the requests.

FYI guys there is a good explanation of the problem at the bottom of this thread.

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

Thanks to SK2 for pointing it out :)

Ah sweet was wondering why my ping was in the 90s Hope they can fix it soon - bf2 is still good but it makes cod2 a pain in the arse to play.

Hi,

Thanks for your traceroutes and pings. We have relodged the latency fault
with Telstra and will hopefully have the issue sorted out soon. If you
have any further queries regarding this matter, please feel free to
contact our Helpdesk by phone on 1300788233.

Kind regards,
Gareth Cleeves
Customer Support Officer

Hi,

Thanks for your traceroutes and pings. We have relodged the latency fault
with Telstra and will hopefully have the issue sorted out soon. If you
have any further queries regarding this matter, please feel free to
contact our Helpdesk by phone on 1300788233.

Kind regards,
Gareth Cleeves
Customer Support Officer

lol @ copy paste.. Got the same email

Kornk

Don't hate the Player HATE the game

:P

damn, now my pings have gone up since you guys have logged your requests.

What is going on? they're back to normal again.

Not for me

i didnt log a support request im fine.

I raise the question though .. 4 yrs I was there nothing has changed, why do u think they will now

Because it's different now, things were harder then, we've come a long way!
People have come a long way!

....pffft sif things will change, we're just waiting on another temporary fix for the "temporary fix"

There is light at the end of the tunnel

Sorry about the response times , we have been extremely busy of late.
We have sent a fault off to Telstra as we have found there is definately another latency problem between NT -> SA. A technician is going to look at it in the next few days.

We will contact you back as soon as we know there is a resolution.

This type of problem has been very painful for ourselves and obviously for yourself.

Kind Regards.
--
Stuart Porter
Internode Technical Support

yeah, something is definetly wrong with the service. (im with Bigpond)

ive been getting 100-130+ pings on all servers etc for the past 3 weeks.

I phoned Bigpond to ask what the problem is, they said there wasnt a problem and because my download rates were still around the 50k mark there was nothing they could do.

this has happened before. last time i left it and did nothing .. it eventually went back to normal after a few weeks.

its really pissing me off this time around though, mainly because of their "i dont give a ****" attitude..

surely there is something we can do? they cant just drop the quality of their service and expect us to keep paying the same ammount for something that is not as good as it previously was?.. having said that, its not really about the money, i just want this problem fixed.

Being ex - "pigpond" tech help, you r better off sending pings & traceroutes via email (to the back office guys in Sydney), the guys/girls on the phones have no idea as they (Teletech) turnover 30 CSR's every month and get basic 2 week training.
The back office ppl are more knowledgable

Quote from South:
yeah, something is definetly wrong with the service. (im with Bigpond)

ive been getting 100-130+ pings on all servers etc for the past 3 weeks.

I phoned Bingpond to ask what the problem is, they said there wasnt a problem and because my download rates were still around the 50k mark there was nothing they could do.

this has happened before. last time i left it and did nothing .. it eventually went back to normal after a few weeks.

its really pissing me off this time around though, mainly because of their "i dont give a ****" attitude..

surely there is something we can do? they cant just drop the quality of their service and expect us to keep paying the same ammount for something that is not as good as it previously was?.. having said that, its not really about the money, i just want this problem fixed.

fixed here as of sometime this morning.

Great News, Ill check when I get home.

i just checked, mines still the same .. :(

"Being ex - "pigpond" tech help, you r better off sending pings & traceroutes via email (to the back office guys in Sydney)"

yeah sure, how do i get in contact with these guys?

yep mine are back to normal as well ;) w00p!! Now back to bf2 and no sk8ing around with crappy pings ;)

Cheers
Rip

Fixed at last ...

C:\Documents and Settings\Mark>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 10.1.1.1
2 53 ms 47 ms 46 ms loop0.lns1.adl2.internode.on.net [203.16.215.223
]
3 46 ms 46 ms 49 ms gi0-2-8.cor1.adl5.internode.on.net [203.16.212.1
65]
4 49 ms 48 ms 50 ms games.internode.on.net [203.26.94.189]

Trace complete.

C:\Documents and Settings\Mark>

so the problem has been fixed for internode customers, but they didnt bother about bigpond customers? or does location play a part in this? ...

lol.. dodgy bastards imo.

lol im with ozemail and its fixed for me ;)

bottom of website where it says email us
http://www.bigpond.com/help/ContactUs/default.asp

Quote from South:
i just checked, mines still the same .. :(

"Being ex - "pigpond" tech help, you r better off sending pings & traceroutes via email (to the back office guys in Sydney)"

yeah sure, how do i get in contact with these guys?

I'll look for the email addy (if they haven't changed it).
All emails go to Sydney first

I wrote an email to bigpond technical support and gave a pretty detailed explaination of the problem. (to the best of my ability)

i went on about how i was getting 'long delays' etc etc, but in one sentence of the email i mentioned that i had also used the Gamearena service, and experienced high latency on that as well, but it happened on all gaming servers not just game arena, this is the reply i got from them lol..

------------------------------------------------------------------

Response (Po Tung) -

BigPond Help Desk is unable to provide assistance with gaming enquiries as they fall
outside our support boundaries. For assistance with GameArena specific enquiries,
please see:

http://www.gamearena.com.au/help/

To contact them, go to:

http://www.gamearena.com.au/help/contact/

:-(

*Inserting rub it in quote*

Hehe, yay fixed :P

Quote from South:
I wrote an email to bigpond technical support and gave a pretty detailed explaination of the problem. (to the best of my ability)

i went on about how i was getting 'long delays' etc etc, but in one sentence of the email i mentioned that i had also used the Gamearena service, and experienced high latency on that as well, but it happened on all gaming servers not just game arena, this is the reply i got from them lol..

------------------------------------------------------------------

Response (Po Tung) -

BigPond Help Desk is unable to provide assistance with gaming enquiries as they fall
outside our support boundaries. For assistance with GameArena specific enquiries,
please see:

http://www.gamearena.com.au/help/

To contact them, go to:

http://www.gamearena.com.au/help/contact/

:-(

funny part is when you contact gamearena about it they will tell you to contact bigpond support as they can't do much about pings/traceroutes lol - (it's happened to me before).

Seriously but, do what i do and use the internode support page. I'm not a node customer but you can lodge a ticket easily enough and just use a tracert that someone will paste here. Just check here first to see if others have the same problem, then node will act on it once they get enough replies. May sound silly but it is the best way to get it solved - more people reporting the fault to a central figure the better. Link: http://cgi.internode.on.net/cgi-bin/support

woohooo! its fixed =)

so happy its finally working properly again.

im actually getting better pings/less latency now then ive ever had .. about 50-60ms on Game Arena servers, previously the best i ever had was 70-80.

Thats the shit thing about Telstra, they gave the contract for phone help to the cheapest "off shore" company(Teletech), where there priority is AHT (ave. handling time) is about 550 sec/call, with staff that have mostly non IT background.

In most cases this is what I would do if they try to fob you off, talk to supervisor on the phone (as they are the IT guys) even if they say they can't help you technically, as most would generaly get it escalated to Telstra.

And "DON'T MENTION GAMEARENA!!!!" :-D

Quote from addas:
funny part is when you contact gamearena about it they will tell you to contact bigpond support as they can't do much about pings/traceroutes lol - (it's happened to me before).

Seriously but, do what i do and use the internode support page. I'm not a node customer but you can lodge a ticket easily enough and just use a tracert that someone will paste here. Just check here first to see if others have the same problem, then node will act on it once they get enough replies. May sound silly but it is the best way to get it solved - more people reporting the fault to a central figure the better. Link: http://cgi.internode.on.net/cgi-bin/support