Bad Pings and Slow Downloads

Page 1 of 2; 111 public posts in this discussion.

Post 1

My pings are in the 100+ area, and my downloads are going very slow, about 40-50kb/s. I'm on iiNet's 1.5Mbit plan and everything was running nicely (downloads speeds of 150+kb/s, pings of about 50+) untill late last week. I just reinstalled Windows XP with SP2 and was wondering if something via Windows SP2 could be causing this (I was running SP1 before). Or has any one else been experiancing this problem as well?

Any feedback will be appreciated.

Post 2

what exchange are you on?

Post 3

I'm on the iiNet 1.5Mbit plan, running through the Palmo exchange, and haven't had any slowdowns lately - have had constant 100+ k/b downloads for the last few weeks (yes - constant for the entire two weeks, give or take a few days ;-)).

Post 4

im gettin the typical latency jump to ~100ms as of the weekend. Cas Exchange.

As for the download speed, SP2 limits the number of TCP connections to 10 i think, this apparently slows down most P2P programs a fair bit. There is a patch to fix this:

http://www.lvllord.de/download.php?url=en/EvID4226Patch212-en.zip

See how that goes i guess. While i'm at it, i presum the rest of you Cas Exchange fellas are gettin dodgy pings too? OD's funky connection log thingo is down.

Post 5

Fixed.... new perl install...

https://ios.homelinux.com/smokeping/cgi-bin/smokeping.cgi?target=Internode.NodeADL

90ms - not good...

Post 6

Node 1.5 here on the Cas exchange:

[root@localhost wrathlon]# ping -c 4 internode.on.net
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=0 ttl=62 time=90.2 ms
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=1 ttl=62 time=89.8 ms
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=2 ttl=62 time=87.7 ms
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=3 ttl=62 time=87.9 ms

--- internode.on.net ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3002ms
rtt min/avg/max/mdev = 87.772/88.940/90.259/1.154 ms, pipe 2
[root@localhost wrathlon]#

Mine is stuffed as well :-/

Post 7

On tel$tra ADSL on the cas exchange and its really slow. Grrr at telstra

Post 8

Forgot to add that I'm on the Cas exchange as well. The slows speeds continue, even on fast web servers. >_<

Post 9

iinet on cas exchange and I am getting ~100ms

Post 10

palmerston is ~100 as well. w00t first day on and back to the same old shiet .. hehe

Post 11

Same deal with ping but I've been getting over 130KB/s on 1.5mbit Node Flatrate (with a 37GB rolling 7 day total :D)

Post 12

a question... if we are with iinet and the dslams are installed.... we will be excluded from the high pings? i really dont no and would like to find out

Post 13

Man im getting lost packets everwhere i go... anyone else getting really bad lost packets.. i can only see half of these forums.. :\

Post 14

mm same 100ms to internode on 1.5Mbit from Darwin CBD but speed still 155KB/s

Post 15

Just changed over to nodes new 1.5 plan and speeds are more like the 512 plan. Job logged and time spent with the techs on the phone.

Result is a possible Telstra line/exchange fault.

Telstra promise to check it out tomorrow between 10am and and 2 pm. With luck the fault at the exchanges will be found and fixed.

I will not hold my breath for a quick fix with telstra.

Nodes service was excellent. They know how to look after and keep a customer.

To all node and iinet customers log a job to get the NT problem fixed yet again. Unseen told you all this many times.

Post 16

I'm sorry to say that talking to iiNet does nothing at all. They just deny that they can do anything.

Post 17

because they cant.

Post 18

They can push the point like Internode does. Make their customers feel fuzzy inside

Post 19

Quote from Longtom:
They can push the point like Internode does. Make their customers feel fuzzy inside

True they can do that .. got me there..

but atleast they arnt beating around the bush .. telling you how "it is" really.

Post 20

Alright, download speeds are back to normal, I just reset my modem, last thing I could think of and it worked! :D

Anyway, pings are still high 93 on average, but thats still better to the 110+ I was getting. Guessing something screwed with the modem when the power went out during the lightning storms.

Anyway, all good (except for pings) so I'm happy!

Post 21

Rang node yesterday at 6 pm darwin Time about the slow download speeds. Node rang back at 7:30 pm darwin time saying telstra tech would be around in the am to check the line.

Today at 11 am telstra tech arrives checks line finds no problems with line. Check internet connection with his brand new adsl modem all ok.

Same test done with my modem, failed. Result is now buying a new modem as the original alcatel speed home touch has finally given up the ghost.

I was impressed with the service from node and telstra (not often but praise when it does).

Amazing what speaking to a tech can sometimes achieve.

Post 22

Internode have finally put it on the outages and technical advisories page
found here http://cgi.internode.on.net/advisories/list.html and like it say it's because we are being routed through eastern states as apposed to straight down the guts to SA.

Post 23

https://ios.homelinux.com/smokeping/cgi-bin/smokeping.cgi?target=Internode.NodeADL

not fixed for me yet tho :(

I got this from node helpdesk:

Apologies for the delay in getting back to you, I have been away on Annual
Leave although you should've been contacted by another Helpdesk staff
member. None the less, yes there has been progression made towards getting
this on-going drama fixed once and for all. A fault has been logged with
Telstra yet again and this time they have acknowledge that a routing issue
has been identified. 4 of the affected services have been rectified already
and they're in the process of repairing the remaining 4 or 5 customers also
affected.

Post 24

I was playing Dc and getting pings over 180 to a Qld server :(

Post 25

Woohoo - at least I'M fixed ;)

Post 26

OD, did you have to submit your line number and username to Node, they just asked me for mine so it can be fixed...surely they arent rectifying it on a per user basis.

Post 27

Nah mate - just reported the problem and gave my graph for them to view a few days ago.

Post 28

goodo :P, honestly im a netspace customer but use nodes support ticket system, logically it makes more sense as they actually acknowledge the problem and know a bit about it and it affects everyone

Post 29

LOL

Mental health day and my dsl is fixed .. Loving it :D

Post 30

Woohoo, mine fixed as well! :D

Post 31

mmm :( still dodgy here

Post 32

at uni for another 2 hours..... im keen on getting home to play some css after i upgraded from a 2200xp (getting 15 frames) to a 3200xp (getting 70fps+)

:D

Post 33

anyone on Cas exchange still getting dodgy pings?? it might just be my connection

Post 34

fixed..

Post 35

All fix0red here:

[root@wrathlon Desktop]# ping -c 4 internode.on.net
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=0 ttl=62 time=44.1 ms
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=1 ttl=62 time=44.2 ms
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=2 ttl=62 time=42.7 ms
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=3 ttl=62 time=43.1 ms

--- internode.on.net ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 42.718/43.573/44.271/0.670 ms, pipe 2
[root@wrathlon Desktop]#

Post 36

all fixed in Palmo as well...for now

Post 37

not here. cas exchange.

Post 38

possibly cas exchange broke still?

Post 39

Not for me it isn't...

Post 40

i forgot i was on ADSL. i will check my pings tonight.

Post 41

Forgot to add that I'm on Cas exhange as well, everything running smoothly. Average pings of 46 to node. Download speed screwed again though, think I may need a new modem :/

Post 42

yeah im on cas and im still rooted :( not sure why most of us are fixed and some arent. No reply from support as of yet. What ISP btw Paladin

Post 43

node

Post 44

I figured I'd post in this thread, seeing as it was one of my original problems. Downloads go fine through BitTorrent, Steam etc, anything not using the webserver port. Whenever I download something through a browser the download speed limites it self to 40kb/s or so. Any suggestions?

Post 45

I'm with iinet 1.5 im getting decent downloads and i get better pings to node then i do to iinet :S... i know they decrease your speed slowly if you have gone over your download limit ?

im using wireless card on my laptop if that increases the ping i dunno :S

[Image: http://www.users.on.net/~gkorn/ping.JPG]

Post 46

Your wirless usually adds about 2 - 4ms.

Post 47

well that sucks but i can live with it *LOOK MUM NO CAT 5 CABLE*

Post 48

Yes it seems re-routing by Telstra is the issue but no-one seems to be able to fix it !
Im With Netspace - 512/128 (M) plan and have been 93ms for last 3-4 weeks, I'm CBD metro exchange. I logged job(s) with Netspace Support etc (told them it wasn't my router or PC and they still made me reset and check everything !!)
This happened before and was resolve when Darwin experienced a blackout in the CBD and the pings went back to 43ms !.

I have tested other ISP links (I'm a network tech for many different clients around Darwin) and doing a trace route to Adelaide results are ;

Internode 1500/256 is 45ms
Connexus 256/64 is 100ms
Arafura Wireless 11MB is 78ms
Netspace 512/128 is 95ms

Which suggest issue is resolved with Internode and not Netspace and isn't Teltras issue alone ?
It would help if Netspace acknowledge issue instead of getting the end user to jump through hoops even after end user tell them what the issue is...

Post 49

I am also a dusgruntled customer of netspace & hav posted issues about high ping times & slo download speeds! & after many, many fone calls & reports 2 netspace, they just dont seem 2 care! So ive moved myplan frm 512/128 to the el'grando netspace 1500/256 plan, & now, even thou my ping times dont seem much bettr, but i think it is helping with choke, like, with the 512 sumtimez i couldnt even get a single server under 250, but usually around 70-80 on CSS but now, i guess i always can get a game under 100ping, usually around 55-70! Nextmonth im gunna try the netspace 512/512 plan to see how that goes, & if not ill probably churn to Internode as their customer service is way better than gheyspace & most ppl seem 2 run with them here!
I hav also posted a link named "Test your internet speed here" on this forum, i got at most 400k on 512 & now 1100k is mybest, see how ugo!

Post 50

Quote from $tãtï©:
I am also a dusgruntled customer of netspace & hav posted issues about high ping times & slo download speeds! & after many, many fone calls & reports 2 netspace, they just dont seem 2 care! So ive moved myplan frm 512/128 to the el'grando netspace 1500/256 plan, & now, even thou my ping times dont seem much bettr, but i think it is helping with choke, like, with the 512 sumtimez i couldnt even get a single server under 250, but usually around 70-80 on CSS but now, i guess i always can get a game under 100ping, usually around 55-70! Nextmonth im gunna try the netspace 512/512 plan to see how that goes, & if not ill probably churn to Internode as their customer service is way better than gheyspace & most ppl seem 2 run with them here!
I hav also posted a link named "Test your internet speed here" on this forum, i got at most 400k on 512 & now 1100k is mybest, see how ugo!

You've pointed out that you werent happy with the cust service, yet you still stayed with them and upgraded your plan? How does this make any sense?
WTF didnt you churn to somewhere that will give 2 ****s about what is happening?
You want to wait for another month then upgrade again?
Bite the bullet and churn, make your problems go away...simple

very contradictory..

Post 51

Quote from brownie:
a question... if we are with iinet and the dslams are installed.... we will be excluded from the high pings? i really dont no and would like to find out
I think the answer to that one Brownie, is whether iiNet use the telstra infrastructure to route to SA, or whether they light up some dark fibre

Post 52

Well ive upgraded to the netspace el'grande netspace 1500/256 plan 4 the past couple o months & evrything seemed to be fine, ping times on CSS, pings around 55+ & ALWAYS able 2 surf, but im curious on wat the better upload speed of the 512/512 wud do 4me, so ive upgraded to this 4 this, 4a month to see how that goes!

But anyway thx to the ohh masterfull wizard, "hawkeye", 4 your usefull advice, as it wud only cost me hundred$ to churn in the middle of my contract as netspace charge %50 of remaining contract.

i just think that Darwin is gettin ripped off with internet as we are a capitol city with no servers & the ISPs shud consider this.

Post 53

Quote:
i just think that Darwin is gettin ripped off with internet as we are a capitol city with no servers & the ISPs shud consider this.
Why should they, Darwin is only the size of a regional city.

Post 54

any one with TPG gettin bad pings latly? been playing wow with a ping of 500 the lowest over the past week and that was for about 30 minutes, besides that little amout of time my pings been well over 700+

Post 55

I thought that WOW always had pretty bad pings as it connected with servers in the U.S. But then again i could be wrong....

Post 56

yeah my pings normally about 300-450 but still plays all right but when you get to pings around 900+ it starts to lag a little

Post 57

Okay - time to dust off that ol' thread.

I'm with iiNet 1.5Mb plan here - no matter where I download from, or what I try, I'm averaging about 16 - 20 KB/s, down from the 150ish that I'm used to.

Have tried resetting the router - no change. Anybody else (especially on iiNet) getting slow speeds at the moment?

BTW, it's not throttling either - not even close to that yet ;-)

Post 58

Yep, iiNet 1.5 Here too.

Test run on 13/7/2005 @ 6:54 P.M.

Mirror: Internode
Test type: ADSL

Your connection speed:

kbps: 167.6
KB/s: 20.95
Mbps: 0.163671875

Post 59

Thanks Neo - I've sent an email to Tech Support, so should find out shortly what's up.

Post 60

Quote from hawkeye:
You've pointed out that you werent happy with the cust service, yet you still stayed with them and upgraded your plan? How does this make any sense?
WTF didnt you churn to somewhere that will give 2 ****s about what is happening?
You want to wait for another month then upgrade again?
Bite the bullet and churn, make your problems go away...simple

very contradictory..

50% of remaing contract = $360! lend me $360 & be an internode customer

Post 61

Test run on 14/7/2005 @ 12:55 A.M.

Mirror: iiNet
Test type: ADSL

Your connection speed:

kbps: 4455.9
KB/s: 556.9875
Mbps: 4.35146484375

No problems with iiNet here..

Post 62

Thanks for that, Jug - yep, your ePenis is still intact ;-)

(Rub it in, go on - rub it in...)

Post 63

Lol, this time I was actually trying to help out with comment on iinet's service...not brag...I guess I just got lucky. Hopefully you guys in Darwin get hooked up soon.

Post 64

anyone else got a reoccurence of the high ping times?

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

Reply from 203.26.94.189: bytes=32 time=91ms TTL=59
Reply from 203.26.94.189: bytes=32 time=94ms TTL=59
Reply from 203.26.94.189: bytes=32 time=92ms TTL=59
Reply from 203.26.94.189: bytes=32 time=91ms TTL=59

Post 65

Yep. Just noticed the jump in latency while attempting to play BF2.

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

Reply from 203.26.94.189: bytes=32 time=99ms TTL=60
Reply from 203.26.94.189: bytes=32 time=98ms TTL=60
Reply from 203.26.94.189: bytes=32 time=100ms TTL=60
Reply from 203.26.94.189: bytes=32 time=98ms TTL=60

512Kbit on Nightcliff exchange.

Post 66

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

Nightcliff exchange 1.5
:( not again

Post 67

lol

Post 68

lodge a support request straight away with your usernames, i've already got a reply saying that they will look into it if/when more people send in requests.

Post 69

... Lodged.

Post 70

Loged at 4pm

Post 71

Hi Matt,

Thankyou for the information. We have had some reports of the issue so it
is possible the issue has resurfaced!

Your details will be forwarded to our technicians to investigate and resolve.

Thank your for your time and patience, again, in this matter.

Regards
Internode Team

Post 72

just spoken to someone from Node Support VIA msn, and he needs one more node customer to lodge a support request before it can be lodged properly.

i've given him a link to these forums and he may reply here too...

Post 73

ill lodge one, never done it before though
where do i go to to lodge a support request?

Post 74

http://cgi.internode.on.net/cgi-bin/support

Post 75

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

Reply from 203.26.94.189: bytes=32 time=102ms TTL=60
Reply from 203.26.94.189: bytes=32 time=99ms TTL=60
Reply from 203.26.94.189: bytes=32 time=105ms TTL=60
Reply from 203.26.94.189: bytes=32 time=130ms 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 = 99ms, Maximum = 130ms, Average = 109ms

Lodged @ 7:40pm

Post 76

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

Reply from 203.16.214.17: bytes=32 time=38ms TTL=57
Reply from 203.16.214.17: bytes=32 time=35ms TTL=57
Reply from 203.16.214.17: bytes=32 time=35ms TTL=57
Reply from 203.16.214.17: bytes=32 time=35ms TTL=57

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

BLOODY UNI...

Post 77

Hi Craig,

Thankyou for the information. We have had some reports of the issue so it is possible the issue has resurfaced!

Your details will be forwarded to our technicians to investigate and resolve.

Can you please reply to this email and provide a trace so we can investigate further.

Thank your for your time and patience, again, in this matter.

Kind regards,
Amanda Eastham
Helpdesk Support

Post 78

De ja vu

Quote:
Hi Dan,

Thankyou for the information. We have had some reports of the issue so it
is possible the issue has resurfaced!

If you are able to reply and send in some example pings and traceroutes,
the details will be forwarded to our technicians to investigate and resolve.

Thank your for your time and patience, again, in this matter.

Regards

Kylie Frost

Post 79

All better now!!!

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=47ms TTL=60
Reply from 203.16.214.17: bytes=32 time=47ms 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

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

Post 80

hrm what exchange you on? still shoddy here on CAS exchange for me.

Post 81

Nightcliff...

Post 82

CAS exchange - fixed for me (Node).

Post 83

sigh :(

Post 84

Hooraa! Fixed for me as well ;)

Post 85

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

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

:(

Post 86

Freakey thing.. Node just rang me to check if the pings were back to normal Just as i was looking at this thread.. and just as phen was saying how he stuffed up his order for adsl

They are fine for me!!

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

Post 87

They stuffed up our order :P

Post 88

Just rang me too...

Post 89

Was it kylie... She sounds nice :) WE want pic :D

Post 90

Matt says: hey
Matt says: question
Matt says: Kylie is she hot?
Matt says: she works node helpdesk
UgLyPuNk says: hahahahahahaahahhahah
UgLyPuNk says: i dont find unattractive or attractive not my sort
Matt says: u got pic
UgLyPuNk says: nope
Matt says: :(

LOL

Post 91

C:\Documents and Settings\Craig>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=43ms TTL=60
Reply from 203.26.94.189: bytes=32 time=43ms TTL=60
Reply from 203.26.94.189: bytes=32 time=42ms TTL=60
Reply from 203.26.94.189: bytes=32 time=42ms 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 = 42ms, Maximum = 43ms, Average = 42ms

YAY

Post 92

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=0 ttl=59 time=91.5 ms
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=1 ttl=59 time=93.1 ms
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=2 ttl=59 time=91.1 ms
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=3 ttl=59 time=91.2 ms
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=4 ttl=59 time=92.4 ms

--- internode.on.net ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3999ms
rtt min/avg/max/mdev = 91.136/91.903/93.161/0.774 ms, pipe 2

:(

Post 93

C:\Documents and Settings\Administrator>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=88ms TTL=62
Reply from 203.16.214.17: bytes=32 time=87ms TTL=62
Reply from 203.16.214.17: bytes=32 time=88ms TTL=62
Reply from 203.16.214.17: bytes=32 time=88ms TTL=62

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 = 88ms, Average = 87ms

Post 94

Ahh, much better.

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=0 ttl=59 time=47.5 ms
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=1 ttl=59 time=47.5 ms
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=2 ttl=59 time=48.2 ms
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=3 ttl=59 time=47.5 ms

--- internode.on.net ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 47.524/47.715/48.254/0.380 ms, pipe 2

Post 95

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

Reply from 203.26.94.189: bytes=32 time=49ms TTL=59
Reply from 203.26.94.189: bytes=32 time=46ms TTL=59
Reply from 203.26.94.189: bytes=32 time=47ms TTL=59
Reply from 203.26.94.189: bytes=32 time=53ms 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 = 46ms, Maximum = 53ms, Average = 48ms

512/512 is twice as nice

Post 96

sigh

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

Reply from 203.26.94.189: bytes=32 time=96ms TTL=59
Reply from 203.26.94.189: bytes=32 time=91ms TTL=59
Reply from 203.26.94.189: bytes=32 time=90ms TTL=59
Reply from 203.26.94.189: bytes=32 time=96ms TTL=59

Post 97

Back to bad here - Node Cas.

Post 98

fine again for me, shrug, cas exchange too.

Post 99

dammit, was looking forward to a sunday of bf2 and camperstrike :(

Post 100

Okay i dont get this im with iinet

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

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

ping www.iinet.net.au

Pinging www.iinet.net.au [203.59.24.221] with 32 bytes of data:

Reply from 203.59.24.221: bytes=32 time=73ms TTL=55
Reply from 203.59.24.221: bytes=32 time=74ms TTL=55
Reply from 203.59.24.221: bytes=32 time=76ms TTL=55
Reply from 203.59.24.221: bytes=32 time=75ms TTL=55

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

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=49ms TTL=59
Reply from 203.26.94.189: bytes=32 time=47ms TTL=59
Reply from 203.26.94.189: bytes=32 time=45ms 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 = 45ms, Maximum = 49ms, Average = 46ms