sorry about the short post in the other thread. i had my postin cut short by other matters.
the old thread resides here.
http://qgl.ausforums.com/?agn=thread&id=1769841

anyway. heres the gist of it.

C:\>ping www.ozforces.com.au

Pinging www.ozforces.com.au [203.17.15.197] with 32 bytes of data:

Reply from 203.17.15.197: bytes=32 time=188ms TTL=252
Reply from 203.17.15.197: bytes=32 time=172ms TTL=252
Reply from 203.17.15.197: bytes=32 time=141ms TTL=252
Reply from 203.17.15.197: bytes=32 time=157ms TTL=252

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

those are some pings taken right now.

C:\>tracert www.ozforces.com.au

Tracing route to www.ozforces.com.au [203.17.15.197]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms 192.168.1.1
2 78 ms 93 ms 94 ms lns01-wick-bne.comindico.com.au [203.220.79.188]

3 125 ms 157 ms 172 ms ge1-0.wsr01-kent-syd.comindico.net.au [203.194.2
9.249]
4 187 ms 188 ms 187 ms content-delivery-syd.comindico.net.au [203.194.2
6.6]
5 172 ms 171 ms 172 ms web1.ozforces.com [203.17.15.197]

Trace complete.
a trace.

and also, just for clipto who ALWAYS asks
(and it has great bearing on myself as well)

C:\>tracert uswest.battle.net

Tracing route to uswest.battle.net [63.241.83.8]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms 192.168.1.1
2 265 ms 156 ms 172 ms lns01-wick-bne.comindico.com.au [203.220.79.188]

3 329 ms * 344 ms ge2-0.1000.bdr02-west-sea.comindico.net [203.194
.0.82]
4 375 ms 328 ms 329 ms p6-1.sttlwa1-cr1.bbnplanet.net [4.25.88.21]
5 375 ms 391 ms 359 ms so-2-0-0.sttlwa1-hcr1.bbnplanet.net [4.24.10.238
]
6 344 ms 344 ms 343 ms p10-0-9.snjpca1-br1.bbnplanet.net [4.0.9.138]
7 344 ms 375 ms 359 ms so-6-2-0-100.mp1.sjo1.Level3.net [64.159.4.73]
8 406 ms 360 ms 390 ms so-7-0-0.gar1.SanJose1.Level3.net [64.159.1.74]

9 406 ms 375 ms 406 ms so-6-0-0.edge1.SanJose1.level3.net [209.244.3.13
8]
10 703 ms 734 ms 719 ms att-level3-oc48.SanJose1.Level3.net [209.0.227.3
0]
11 703 ms 657 ms 687 ms tbr1-p012201.sffca.ip.att.net [12.123.13.189]
12 703 ms 703 ms 687 ms gar4-p300.sffca.ip.att.net [12.123.13.174]
13 641 ms 688 ms 656 ms idf26-gsr12-1-pos-6-0.rwc1.attens.net [12.122.25
5.222]
14 687 ms 766 ms 687 ms mdf2-bi8k-2-eth-1-1.rwc1.attens.net [216.148.209
.18]
15 * * 63.241.68.178 reports: Destination net unreachable.

Trace complete.

now, this isnt even as bad as its been. this is all on the 512/128 elite gamer plan. how are we meant to play games on that? this isnt even as bad as it has been. its usually quite unstable also, and when the problems first started we were getting quite massive packet loss (in the range of 20-40%). of the 4 months of being with this isp 2 of those have had service worse than dial-up. in the 1st month of connection for the whole month we had horrid packet loss and pings that ranged from 300-1000 and beyond.

aside from performance i am getting incredibly aggrevated with how ozforces handles complaints. after numerous emails over time and a huge number of forum posts only very few of them have been answered. and even then its usually to blame comindico or telstra. of course thats not always the case and i cant read ALL forums ALL the time.

the other issue i have, is that for all this downtime and rubbish service there has been a lot of talk about discounts and credit. during the 1st month of connection when our (i live with fade2black and tollazor) net was unusable a staff member mentioned credits would be given. guess what? havent heard anything since. billing never answers emails. and all matters regarding credits on forums are deleted.

seriously, what can we, the users, do here? all i can think to do is vent my frustration. hopefully i can also save some other poor soul from the hassle. any thoughts on what action we can take, or any1 experiencing similar would be greatly appreciated. post other isp or internet horror stories, it may cheer me up.

edit : sorry for those seeing that i posted 3 of the same pings. my clipboard isnt working ...

yuo should have read up on whirlpool and noticed that ozforces or any comindico ISP do not give a very good broadband soltution

netspace / internode are the only dsl ISP's you should consider

couldnt.

4 months ago = rollout. one of those good idea at the time things.

I'm on netspace 512/128 and am connected through a 11mbit crappy USB wireless thing to my modem so I could probably have 4-10 lower pings but here are my results


Pinging 203.17.15.197 with 32 bytes of data:

Reply from 203.17.15.197: bytes=32 time=70ms TTL=245
Reply from 203.17.15.197: bytes=32 time=71ms TTL=245
Reply from 203.17.15.197: bytes=32 time=70ms TTL=245
Reply from 203.17.15.197: bytes=32 time=71ms TTL=245

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


C:\Documents and Settings\Darius>ping 203.17.15.197

Pinging 203.17.15.197 with 32 bytes of data:

Reply from 203.17.15.197: bytes=32 time=74ms TTL=245
Reply from 203.17.15.197: bytes=32 time=79ms TTL=245
Reply from 203.17.15.197: bytes=32 time=72ms TTL=245
Reply from 203.17.15.197: bytes=32 time=74ms TTL=245

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


Tracing route to 63.241.83.8 over a maximum of 30 hops

1 23 ms 23 ms 21 ms 192.168.1.254
2 26 ms 29 ms 25 ms core1-loopback-0.Brisbane.netspace.net.au [203.17.101.6]
3 28 ms 29 ms 27 ms fastethernet6-0-2.cor2.bri.connect.com.au [203.63.181.218]
4 26 ms 25 ms 27 ms gigabitethernet4-0-0.bdr1.bri.connect.com.au [203.63.11.81]
5 28 ms 25 ms 27 ms so-1-0-1.cre1.for.connect.com.au [202.10.4.45]
6 31 ms 29 ms 28 ms so-0-1-0.cre1.bri.connect.com.au [202.10.0.56]
7 46 ms 45 ms 45 ms so-0-2-0.cre1.syd.connect.com.au [202.10.0.33]
8 45 ms 44 ms 43 ms pos1-0-0.bdr3.syd.connect.com.au [202.10.4.10]
9 44 ms 45 ms 46 ms p4-5.sybr3.global-gateway.net.nz [202.37.246.249]
10 45 ms 47 ms 45 ms p1-6.sybr2.global-gateway.net.nz [202.37.246.205]
11 194 ms 193 ms 195 ms p0-2-2-0.labr3.global-gateway.net.nz [202.50.116.154]
12 197 ms 198 ms 197 ms sl-gw15-ana-6-0.sprintlink.net [144.232.241.81]
13 197 ms 197 ms 197 ms sl-bb22-ana-3-3.sprintlink.net [144.232.1.217]
14 198 ms 199 ms 195 ms sprint-gw.la2ca.ip.att.net [192.205.32.185]
15 199 ms 201 ms 199 ms tbr1-p012801.la2ca.ip.att.net [12.122.11.225]
16 199 ms 196 ms 199 ms gar4-p300.la2ca.ip.att.net [12.123.28.202]
17 205 ms 203 ms 205 ms idf26-gsr12-1-pos-7-0.rwc1.attens.net [12.122.255.142]
18 211 ms 213 ms 209 ms mdf2-bi8k-2-eth-1-1.rwc1.attens.net [216.148.209.18]
19 63.241.68.178 reports: Destination net unreachable.

Trace complete.




So basically yeah, Ozforces seems very bad :/ I think dialup would perform better

Fast, stable, low ping connections at very affordable prices mean that anyone anywhere in Australia can join OzForces Internet, and everyone from around the world can join the OzForces community. >>>

send them that with a variety of sample pings to different servers on different dates. basically - do not stop complaining. emails can be ignored, phone conversations can not
KEEP ON RINGING.. complain. ask to talk to managers, and their managers. make a general pain in the ass

wave around phrases like "breach of contract" every now and again.

if they fail to help or respond in anyway, threaten legal action.. even consider going through with it.. keep logs of pings to a variety of servers on a daily basis so u have some proof. but generally, just make an absolute nuisance of yourself.. they will probably end up giving you a full refund if you ask for it and don't let up.

I thought Comindico were gonna run that Suck My Pipe comp or something stupid like that. So that would mean they'd have to have a nice connection. Maybe not then.

:/

Mine from BPA cable in brisbane:



Pinging 203.17.15.197 with 32 bytes of data:

Reply from 203.17.15.197: bytes=32 time=24ms TTL=243
Reply from 203.17.15.197: bytes=32 time=24ms TTL=243
Reply from 203.17.15.197: bytes=32 time=23ms TTL=243
Reply from 203.17.15.197: bytes=32 time=25ms TTL=243

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



c:\>tracert www.ozforces.com.au

Tracing route to www.ozforces.com.au [203.17.15.197]
over a maximum of 30 hops:

1 * * * Request timed out.
2 7 ms 7 ms 8 ms 61.9.209.7
3 8 ms 7 ms 23 ms GigabitEthernet4-2.cha23.telstra.net [139.130.193.117]
4 10 ms 7 ms 8 ms GigabitEthernet5-0.cha-core4.Brisbane.telstra.net [203.50.44.9]
5 21 ms 21 ms 21 ms Pos4-0.chw-core2.Sydney.telstra.net [203.50.6.225]
6 20 ms 19 ms 19 ms GigabitEthernet1-2.ken12.Sydney.telstra.net [203.50.19.22]
7 19 ms 19 ms 20 ms optvis2.lnk.telstra.net [139.130.2.66]
8 21 ms 19 ms 20 ms GigEth1-0-0.sn2.optus.net.au [202.139.190.16]
9 24 ms 26 ms 21 ms Comindico.sn2.optus.net.au [203.202.186.174]
10 24 ms 23 ms 24 ms ge1-0.wsr01-kent-syd.comindico.net.au [203.194.29.249]
11 21 ms 22 ms 22 ms content-delivery-syd.comindico.net.au [203.194.26.6]
12 27 ms 25 ms 28 ms 203.17.15.197

Trace complete.




Tracing route to 63.241.83.8 over a maximum of 30 hops

1 * * * Request timed out.
2 8 ms 7 ms 7 ms 61.9.209.7
3 8 ms 7 ms 7 ms GigabitEthernet4-2.cha23.telstra.net [139.130.193.117]
4 8 ms 11 ms 8 ms GigabitEthernet5-0.cha-core4.Brisbane.telstra.net [203.50.44.9]
5 22 ms 21 ms 21 ms Pos4-0.chw-core2.Sydney.telstra.net [203.50.6.225]
6 21 ms 22 ms 23 ms 10GigabitEthernet3-0.pad-core5.Sydney.telstra.net [203.50.6.90]
7 22 ms 21 ms 22 ms GigabitEthernet0-1.syd-core02.Sydney.net.reach.com [203.50.13.254]
8 20 ms 21 ms 22 ms GigabitEthernet1-1.syd-core01.net.reach.com [202.84.219.213]
9 210 ms 208 ms 209 ms i-13-1.sjc-core01.net.reach.com [202.84.143.21]

10 207 ms 206 ms 360 ms i-3-1.sjc02.net.reach.com [202.84.251.58]
11 206 ms 207 ms 206 ms sl-st21-sj-6-1.sprintlink.net [144.223.242.1]
12 208 ms 216 ms 208 ms 144.232.9.206
13 201 ms 200 ms 201 ms tbr2-p012201.sffca.ip.att.net [12.123.13.193]
14 199 ms 198 ms 198 ms gar4-p390.sffca.ip.att.net [12.123.13.178]
15 199 ms 203 ms 199 ms idf26-gsr12-1-pos-6-0.rwc1.attens.net [12.122.255.222]
16 204 ms 205 ms 204 ms mdf2-bi8k-2-eth-1-1.rwc1.attens.net [216.148.209.18]
17 63.241.68.178 reports: Destination net unreachable.

Trace complete.

trust me. i'm being vocal. hence posts here. cbf going anywhere else atm. but tommorow the phone calls start. and they wont stop until they do something.
when my bpa cable went crappy cause of overloading (i was in st lucia area) i didnt stop for weeks. every day on the phone. it seemed to work. a month later and i had the best pings on the then qgl cs server (yes i know, cs.).

for those interested or on ozforces and without the knowledge to voice your opinionm here is a lonk to their support forums.

http://www.ozforums.com/showthread.php?s=&postid=710458#post710458

lotta angry people there.

edit: speelang sux0rs! for comedy value i'll leave them

seriously, what can we, the users, do here?

In the immortal words of the Whirlpool guys, usually used in conjunction with the word 'Telstra', "Vote with your feet".

ahh yes, but in which manner? shall i use them to KICK THE CRUD out of some poor dude, or simply leave the isp?

i think we shall be leaving. unfortunetely thats more money down the tiolet.

Well I had the same troubles with iinet a little while back, pinging just iinet was getting 200+

Here are my results, bear in mind I am in Syd - where comindico is:

C:\Documents and Settings\HeardY>ping 203.17.15.197

Pinging 203.17.15.197 with 32 bytes of data:

Reply from 203.17.15.197: bytes=32 time=23ms TTL=250
Reply from 203.17.15.197: bytes=32 time=24ms TTL=250
Reply from 203.17.15.197: bytes=32 time=23ms TTL=250
Reply from 203.17.15.197: bytes=32 time=24ms TTL=250

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


C:\Documents and Settings\HeardY>tracert 203.17.15.197

Tracing route to 203.17.15.197 over a maximum of 30 hops

1 22 ms 18 ms 21 ms syd-uun-ce1.iinet.net.au [203.166.38.115]
2 22 ms 21 ms 21 ms IINET-SYD-at-1-1-0-100.ar1.SYD1.gblx.net [203.19
2.166.201]
3 24 ms 23 ms 23 ms ATM11-0-0-5.sn2.optus.net.au [61.88.168.185]
4 30 ms 29 ms 23 ms Comindico.sn2.optus.net.au [203.202.186.174]
5 25 ms 23 ms 77 ms ge1-0.wsr01-kent-syd.comindico.net.au [203.194.2
9.249]
6 74 ms 22 ms 34 ms content-delivery-syd.comindico.net.au [203.194.2
6.6]
7 23 ms 26 ms 23 ms 203.17.15.197

Trace complete.

C:\Documents and Settings\HeardY>tracert 63.241.83.8

Tracing route to 63.241.83.8 over a maximum of 30 hops

1 20 ms 42 ms 19 ms syd-uun-ce1.iinet.net.au [203.166.38.115]
2 23 ms 21 ms 21 ms IINET-SYD-at-1-1-0-100.ar1.SYD1.gblx.net [203.19
2.166.201]
3 136 ms 136 ms 134 ms so1-3-0-155M.cr2.NRT4.gblx.net [203.192.136.74]

4 301 ms 300 ms 302 ms pos2-0-2488M.cr1.CHI1.gblx.net [208.49.59.250]
5 342 ms 286 ms 286 ms so0-0-0-2488M.br2.CHI1.gblx.net [208.49.59.206]

6 285 ms 306 ms 284 ms 208.51.6.26
7 304 ms 300 ms 296 ms tbr1-p013902.cgcil.ip.att.net [12.122.11.205]
8 284 ms 283 ms 283 ms tbr1-cl1.sffca.ip.att.net [12.122.10.6]
9 293 ms 290 ms 290 ms gar4-p300.sffca.ip.att.net [12.123.13.174]
10 284 ms 284 ms 282 ms idf26-gsr12-1-pos-6-0.rwc1.attens.net [12.122.25
5.222]
11 296 ms 298 ms 300 ms mdf2-bi8k-2-eth-1-1.rwc1.attens.net [216.148.209
.18]
12 * 63.241.68.178 reports: Destination net unreachable.

Trace complete.


These results even suprised me!!!

Looks like iinet may have finally got their arses into gear! :)

heardy you would have seen our pings in action when we play cs (yes i know shut up! i dont play fade does!)

i've seen them first hand, he was killing me $^&(*@*@@ :p

yeah its dongs, the other night optus borked itself, helo 3000 pings :D

but it seems iinet is getting better, they are offering new plans (more data) and when there is downtime, giving us credit :)

kekeke internode pwnage 1500/256

C:\Documents and Settings\Administrator>ping pip.pipenetworks.com

Pinging figjam.pipenetworks.com [202.4.251.50] with 32 bytes of data:

Reply from 202.4.251.50: bytes=32 time=15ms TTL=57
Reply from 202.4.251.50: bytes=32 time=30ms TTL=57
Reply from 202.4.251.50: bytes=32 time=15ms TTL=57
Reply from 202.4.251.50: bytes=32 time=15ms TTL=57

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

Brisbane iiNet:

ping ozforces.com

Pinging ozforces.com [203.17.15.197] with 32 bytes

Reply from 203.17.15.197: bytes=32 time=46ms TTL=2
Reply from 203.17.15.197: bytes=32 time=42ms TTL=2
Reply from 203.17.15.197: bytes=32 time=40ms TTL=2
Reply from 203.17.15.197: bytes=32 time=43ms TTL=2

Ping statistics for 203.17.15.197:
Packets: Sent = 4, Received = 4, Lost = 0 (0%
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 46ms, Average = 42ms

That f***ing sucks man, oh well I remember saying befor if its the worst case scenario at least your not in any sort of real contract. Shame they wont be churning for a while.

I decided to get dial up befor I went for ADSL. Didnt go with ozforces because they wanted contracts or some s*** for their dial up (rolls eyes).

Anyway I went with dart who im trying to get adsl sorted with now, (cant easily get adsl), they seem pretty good at working through a lot of problems and give excellent tech support. Also you can get a free sign up with them but a penalty if you leave within six months on one plan, another comindico reseller so i dunno if you want to take your chances with a reseller again.

In about a week or so they will apprently be selling via connect.com as well so I am keeping my eye on that...

paragon, do a tracert to uswest.battle.net for clipto. if i remember you were the lucky bastard getting about 150 ping to google which would mean aewsome bnet pings.

:P

Internode go through all sorts of carriers, which is good and bad. Cos I think the connection to uswest would change quite a bit.

Go ahead and post it though, i used to get 160 to uswest :p

Here is our traceroute to ozforces.com:

We use I-Exec 1.5/256 DSL

traceroute to ozforces.com (203.17.15.197), 30 hops max, 38 byte packets
1 210-18-214-81.cust.iexec.net.au (210.18.214.81) 1.366 ms 1.315 ms 1.241 ms
2 loopback10-fixed.gw.iexec.net.au (210.18.212.1) 13.141 ms 12.968 ms 13.165 ms
3 border-bne.gw.iexec.net.au (210.18.210.38) 13.499 ms 14.260 ms 13.239 ms
4 fastethernet5-0.cor2.bri.connect.com.au (210.9.224.230) 13.784 ms 14.604 ms 14.822 ms
5 gigabitethernet4-0-0.bdr1.bri.connect.com.au (203.63.11.81) 13.727 ms 19.785 ms 18.501 ms
6 so-0-0-0.cre1.bri.connect.com.au (202.10.4.43) 14.177 ms 14.854 ms 15.122 ms
7 so-0-1-0.cre1.for.connect.com.au (202.10.0.57) 16.150 ms 17.019 ms 15.931 ms
8 so-0-2-0.cre1.hay.connect.com.au (202.10.0.35) 30.485 ms 30.802 ms 29.589 ms
9 so-1-1-0.cre1.bur.connect.com.au (202.10.0.40) 45.607 ms 46.318 ms 46.499 ms
10 pos12-0-0.bdr2.mel.connect.com.au (202.10.4.32) 47.684 ms 44.942 ms 46.527 ms
11 com140028-1.gw.connect.com.au (203.8.183.114) 43.747 ms 44.548 ms 44.903 ms
12 ge1-0.wsr01-kent-syd.comindico.net.au (203.194.29.249) 60.553 ms 60.750 ms 63.219 ms
13 content-delivery-syd.comindico.net.au (203.194.26.6) 63.193 ms 62.757 ms 61.510 ms
14 203.17.15.197 (203.17.15.197) 59.780 ms 62.685 ms 61.291 ms

and to uswest.battle.net:

[root@imperium etc]# traceroute 63.241.83.8
traceroute to 63.241.83.8 (63.241.83.8), 30 hops max, 38 byte packets
1 210-18-214-81.cust.iexec.net.au (210.18.214.81) 1.343 ms 1.266 ms 1.232 ms
2 loopback10-fixed.gw.iexec.net.au (210.18.212.1) 13.414 ms 15.296 ms 14.144 ms
3 border-bne.gw.iexec.net.au (210.18.210.38) 21.176 ms 16.183 ms 14.488 ms
4 fastethernet5-0.cor2.bri.connect.com.au (210.9.224.230) 13.377 ms 15.381 ms 14.964 ms
5 gigabitethernet4-0-0.bdr1.bri.connect.com.au (203.63.11.81) 15.022 ms 16.239 ms 15.865 ms
6 so-0-0-0.cre1.bri.connect.com.au (202.10.4.43) 16.772 ms 15.040 ms 15.964 ms
7 so-0-2-0.cre1.syd.connect.com.au (202.10.0.33) 30.801 ms 31.573 ms 32.318 ms
8 pos1-0-0.bdr3.syd.connect.com.au (202.10.4.10) 29.588 ms 30.328 ms 31.580 ms
9 p4-4.sybr3.global-gateway.net.nz (202.37.246.245) 31.506 ms 32.082 ms 31.258 ms
10 p4-0.sybr2.global-gateway.net.nz (202.50.119.86) 30.451 ms 31.088 ms 30.996 ms
11 p0-2-2-0.labr3.global-gateway.net.nz (202.50.116.154) 180.283 ms 181.670 ms 180.259 ms
12 sl-gw15-ana-6-0.sprintlink.net (144.232.241.81) 182.101 ms 182.572 ms 182.549 ms
13 sl-bb22-ana-3-3.sprintlink.net (144.232.1.217) 212.071 ms 239.710 ms 224.208 ms
14 192.205.32.185 (192.205.32.185) 183.158 ms 183.513 ms 183.962 ms
15 12.122.11.221 (12.122.11.221) 185.019 ms 185.453 ms 184.334 ms
16 gar4-p390.la2ca.ip.att.net (12.123.28.206) 183.307 ms 183.652 ms 183.965 ms
17 idf26-gsr12-1-pos-7-0.rwc1.attens.net (12.122.255.142) 191.624 ms 192.749 ms 191.128 ms
18 216.148.209.18 (216.148.209.18) 230.787 ms 193.523 ms 192.578 ms
19 * *

paragon, pinging your own network serves what purpose here?

iiNet is getting even better :) They've almost doubled the peak download limit at no extra cost :D

iiNut suck cock, but apparently in WA and QLD they are somewhat reasonable.

I just churned over from iiNut to Netspace yesterday and everything is so much faster and the usage meter actually updates more than once a day.

and i get similar pings to what Jim posted

s*** really?

I was tempted to stay with iinet (as i am a lazy a****** and cbf getting a new isp) - but yeh they have been somewhat s*** in nsw in recent months

What provider does capto go with? What do you get to asia.battle.net capto?

We use I-Exec 1.5/256 DSL

As above we use I-Exec. www.iexec.com.au. they are expensive and noti n the home market.

traceroute to asia.battle.net (211.233.0.58), 30 hops max, 38 byte packets
1 210-18-214-81.cust.iexec.net.au (210.18.214.81) 1.319 ms 1.272 ms 1.237 ms
2 loopback10-fixed.gw.iexec.net.au (210.18.212.1) 13.454 ms 14.425 ms 14.480 ms
3 border-bne.gw.iexec.net.au (210.18.210.38) 14.967 ms 13.011 ms 13.941 ms
4 fastethernet5-0.cor2.bri.connect.com.au (210.9.224.230) 12.290 ms 14.452 ms 13.412 ms
5 gigabitethernet4-0-0.bdr1.bri.connect.com.au (203.63.11.81) 13.529 ms 15.334 ms 13.589 ms
6 so-0-0-0.cre1.bri.connect.com.au (202.10.4.43) 15.153 ms 14.881 ms 15.730 ms
7 so-0-1-0.cre1.for.connect.com.au (202.10.0.57) 16.020 ms 15.475 ms 15.443 ms
8 so-0-2-0.cre1.hay.connect.com.au (202.10.0.35) 29.419 ms 28.757 ms 28.348 ms
9 pos4-0-0.bdr3.syd.connect.com.au (202.10.4.12) 27.742 ms 28.822 ms 27.945 ms
10 p4-5.sybr3.global-gateway.net.nz (202.37.246.249) 29.101 ms 29.919 ms 30.788 ms
11 202.37.245.254 (202.37.245.254) 180.785 ms 179.981 ms 179.967 ms
12 p0-3-0-0.pabr3.global-gateway.net.nz (202.37.246.201) 183.999 ms 182.680 ms 184.191 ms
13 206.111.12.65 (206.111.12.65) 184.472 ms 183.276 ms 182.931 ms
14 p5-0-0.rar1.sanjose-ca.us.xo.net (65.106.5.193) 216.741 ms 181.216 ms 180.774 ms
15 p0-0-0.mar1.fremont-ca.us.xo.net (65.106.5.134) 185.576 ms 180.934 ms 183.461 ms
16 p0-0.chr1.fremont-ca.us.xo.net (207.88.80.178) 180.334 ms 180.624 ms 181.266 ms
17 67.104.60.54.ptr.us.xo.net (67.104.60.54) 184.432 ms 183.388 ms 183.955 ms
18 203.255.234.55 (203.255.234.55) 179.544 ms 185.079 ms 186.372 ms
19 203.255.234.197 (203.255.234.197) 301.453 ms 303.510 ms 322.187 ms
20 203.233.35.110 (203.233.35.110) 314.061 ms 312.750 ms 312.336 ms
21 211.233.88.155 (211.233.88.155) 321.643 ms 211.233.88.153 (211.233.88.153) 318.008 ms 328.722 ms
22 k1c9-4231.sw.kidc.net (211.233.55.238) 318.126 ms 312.638 ms 325.440 ms
23 211.233.0.58 (211.233.0.58) 321.587 ms 315.090 ms 317.288 ms

Can paragon or someone give me a real world indication of what the 1500 rate is like for pinging game servers?

Like 512 internode gets you 70-100 ping, what can I expect on 1500?

I-Exec:

PING syd4.ausgamers.com (203.17.15.134) 56(84) bytes of data.
64 bytes from 203.17.15.134: icmp_seq=1 ttl=117 time=59.9 ms
64 bytes from 203.17.15.134: icmp_seq=2 ttl=117 time=62.1 ms
64 bytes from 203.17.15.134: icmp_seq=3 ttl=117 time=61.0 ms
64 bytes from 203.17.15.134: icmp_seq=4 ttl=117 time=60.7 ms
64 bytes from 203.17.15.134: icmp_seq=5 ttl=117 time=62.5 ms
64 bytes from 203.17.15.134: icmp_seq=6 ttl=117 time=58.5 ms

[root@imperium squid]# ping hardcoregamers.com
PING hardcoregamers.com (202.0.34.223) 56(84) bytes of data.
64 bytes from 202-0-34-223.cable.paradise.net.nz (202.0.34.223): icmp_seq=1 ttl=49 time=92.8 ms
64 bytes from 202-0-34-223.cable.paradise.net.nz (202.0.34.223): icmp_seq=2 ttl=49 time=88.6 ms
64 bytes from 202-0-34-223.cable.paradise.net.nz (202.0.34.223): icmp_seq=3 ttl=49 time=90.0 ms
64 bytes from 202-0-34-223.cable.paradise.net.nz (202.0.34.223): icmp_seq=4 ttl=49 time=92.6 ms
64 bytes from 202-0-34-223.cable.paradise.net.nz (202.0.34.223): icmp_seq=5 ttl=49 time=90.3 ms
64 bytes from 202-0-34-223.cable.paradise.net.nz (202.0.34.223): icmp_seq=6 ttl=49 time=151 ms
64 bytes from 202-0-34-223.cable.paradise.net.nz (202.0.34.223): icmp_seq=7 ttl=49 time=88.8 ms

[root@imperium squid]# ping internode.com.au
PING internode.com.au (203.16.214.17) 56(84) bytes of data.
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=1 ttl=52 time=54.6 ms
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=2 ttl=52 time=55.1 ms
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=3 ttl=52 time=54.5 ms
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=4 ttl=52 time=54.7 ms
64 bytes from corp.internode.on.net (203.16.214.17): icmp_seq=5 ttl=52 time=57.4 ms

[root@imperium squid]# ping games.telstra.com
PING games.telstra.com (144.135.23.52) 56(84) bytes of data.
64 bytes from 144.135.23.52: icmp_seq=1 ttl=53 time=29.6 ms
64 bytes from 144.135.23.52: icmp_seq=2 ttl=53 time=30.7 ms
64 bytes from 144.135.23.52: icmp_seq=3 ttl=53 time=27.9 ms
64 bytes from 144.135.23.52: icmp_seq=4 ttl=53 time=31.0 ms
64 bytes from 144.135.23.52: icmp_seq=5 ttl=53 time=29.7 ms
64 bytes from 144.135.23.52: icmp_seq=6 ttl=53 time=30.3 ms

[root@imperium squid]# ping iinet.com.au
PING iinet.com.au (203.59.24.221) 56(84) bytes of data.
64 bytes from www.iinet.net.au (203.59.24.221): icmp_seq=1 ttl=242 time=85.0 ms
64 bytes from www.iinet.net.au (203.59.24.221): icmp_seq=2 ttl=242 time=85.9 ms
64 bytes from www.iinet.net.au (203.59.24.221): icmp_seq=3 ttl=242 time=88.3 ms
64 bytes from www.iinet.net.au (203.59.24.221): icmp_seq=4 ttl=242 time=93.1 ms

[root@imperium squid]# ping tpg.com.au
PING tpg.com.au (203.12.160.59) 56(84) bytes of data.
64 bytes from mail.tpgi.com.au (203.12.160.59): icmp_seq=1 ttl=250 time=41.9 ms
64 bytes from mail.tpgi.com.au (203.12.160.59): icmp_seq=2 ttl=250 time=52.4 ms
64 bytes from mail.tpgi.com.au (203.12.160.59): icmp_seq=3 ttl=250 time=32.5 ms
64 bytes from mail.tpgi.com.au (203.12.160.59): icmp_seq=4 ttl=250 time=63.2 ms
64 bytes from mail.tpgi.com.au (203.12.160.59): icmp_seq=5 ttl=250 time=32.5 ms

PING games.telstra.com (144.135.23.52) from 203.x.x.x : 56(84) bytes of data.
64 bytes from 144.135.23.52: icmp_seq=0 ttl=52 time=17.0 ms
64 bytes from 144.135.23.52: icmp_seq=1 ttl=52 time=17.0 ms
64 bytes from 144.135.23.52: icmp_seq=2 ttl=52 time=19.8 ms
64 bytes from 144.135.23.52: icmp_seq=3 ttl=52 time=16.8 ms
64 bytes from 144.135.23.52: icmp_seq=4 ttl=52 time=19.6 ms
64 bytes from 144.135.23.52: icmp_seq=5 ttl=52 time=15.7 ms
64 bytes from 144.135.23.52: icmp_seq=6 ttl=52 time=18.4 ms
64 bytes from 144.135.23.52: icmp_seq=7 ttl=52 time=16.4 ms

--- games.telstra.com ping statistics ---
8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max = 15.7/17.5/19.8 ms

PING iinet.com.au (203.59.24.221) from 203.x.x.x : 56(84) bytes of data.
64 bytes from www.iinet.net.au (203.59.24.221): icmp_seq=0 ttl=242 time=98.9 ms
64 bytes from www.iinet.net.au (203.59.24.221): icmp_seq=1 ttl=242 time=833.7 ms
64 bytes from www.iinet.net.au (203.59.24.221): icmp_seq=2 ttl=242 time=79.7 ms
64 bytes from www.iinet.net.au (203.59.24.221): icmp_seq=3 ttl=242 time=80.9 ms

--- iinet.com.au ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 79.7/273.3/833.7 ms

PING syd4.ausgamers.com (203.17.15.134) from 203.x.x.x: 56(84) bytes of data.
64 bytes from 203.17.15.134: icmp_seq=0 ttl=115 time=48.1 ms
64 bytes from 203.17.15.134: icmp_seq=1 ttl=115 time=52.4 ms
64 bytes from 203.17.15.134: icmp_seq=2 ttl=115 time=49.5 ms
64 bytes from 203.17.15.134: icmp_seq=3 ttl=115 time=52.1 ms
64 bytes from 203.17.15.134: icmp_seq=4 ttl=115 time=54.8 ms
64 bytes from 203.17.15.134: icmp_seq=5 ttl=115 time=52.1 ms
64 bytes from 203.17.15.134: icmp_seq=6 ttl=115 time=49.8 ms

--- syd4.ausgamers.com ping statistics ---
7 packets transmitted, 7 packets received, 0% packet loss
round-trip min/avg/max = 48.1/51.2/54.8 ms