Jump to content

Pings for Aussies.


AussieAlan

Recommended Posts

So as if we did not know Bioware just do not give a stuff about us and are dumping us in the USA (brilliant solution instead of merger all 3 in 1).

 

So here is a thread so we can see how bad things will get, so post your pings.

IP. 159.153.68.252

iiNet Qld.

C:\>ping 159.153.68.252

 

Pinging 159.153.68.252 with 32 bytes of data:

Reply from 159.153.68.252: bytes=32 time=193ms TTL=241

Reply from 159.153.68.252: bytes=32 time=206ms TTL=241

Reply from 159.153.68.252: bytes=32 time=206ms TTL=242

Reply from 159.153.68.252: bytes=32 time=202ms TTL=242

 

Ping statistics for 159.153.68.252:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss

Approximate round trip times in milli-seconds:

Minimum = 193ms, Maximum = 206ms, Average = 201ms

 

Unbelievable, I was getting 40-50ms on Dal.

Link to comment
Share on other sites

Welcome Aussie,

I just started re-playing one character on an East Coast sever and get over 100ms average with the bar continually moving and the occasional dropped service. Also the activity level 24 hours a day make heroics and WZ very accessible. It is also very fun to hear a completely different POV to the very predictable American politics etc.

 

I am actually sitting next to my friend who does allot of networking jobs and lives in an Oregon town with poor internet service. His educated guess is that u perceive the distance between here and Australia as an potential cause of lag/interference or other issues that may cause problems with game play. He stated that most problems are caused by the number of points that the signal is handed off, the protocols used and the priority given. So u will only possibly experience issues from your home to the ocean and from the American coast to the server with maybe an island in the middle. So yes u could get a bad connection, but if it is good now there is no need to worry.

Link to comment
Share on other sites

where are you guys getting the IP address of the harbinger server? i don't think it was listed on BW's server status site? rather than the results of the ping, it would probably be more informative with a /tracert.

 

if there's a distinguishable bad bounce somewhere, maybe something can actually be done.

 

 

Tracing route to 159.153.68.252 over a maximum of 30 hops

 

1 5 ms 3 ms 4 ms 10.1.1.1

2 <1 ms 1 ms <1 ms 71-84-249-65.static.lsan.ca.charter.com [71.84.249.65]

3 1 ms 1 ms 1 ms dtr02lnbhca-tge-0-0-0-10.lnbh.ca.charter.com [96.34.96.52]

4 1 ms 2 ms 1 ms crr02lnbhca-tge-0-1-0-1.lnbh.ca.charter.com [96.34.99.79]

5 4 ms 7 ms 3 ms crr01rvsdca-tge-0-4-0-8.rvsd.ca.charter.com [96.34.97.88]

6 5 ms 11 ms 10 ms bbr01rvsdca-bue-2.rvsd.ca.charter.com [96.34.2.66]

7 5 ms 5 ms 5 ms 216.156.65.85.ptr.us.xo.net [216.156.65.85]

8 44 ms 4 ms 4 ms 206.111.14.110.ptr.us.xo.net [206.111.14.110]

9 6 ms 6 ms 6 ms xe-2-3-0.cr1.lax112.us.above.net [64.125.31.190]

10 17 ms 44 ms 33 ms xe-0-2-0.cr1.sjc2.us.above.net [64.125.26.26]

11 16 ms 16 ms 16 ms xe-1-1-0.er1.sjc2.us.above.net [64.125.26.198]

12 17 ms 16 ms 17 ms 209.66.92.106.t00673-04.above.net [209.66.92.106]

13 16 ms 16 ms 19 ms 159.153.68.252

 

Trace complete.

 

 

^ over my crappy connection at work.. :D

Edited by oredith
Link to comment
Share on other sites

I play between 200 - 300 ping and have done so since launch. Briefly, after 1.2 was rolled out and the player base evaporated I switched to the Fatman server which is East coast. The ping range on that server was between 350 and 450ms. This was still "playable" but it really wasn't much fun. I would never play east coast again.
Link to comment
Share on other sites

Seriously, my and most Aussies pings will be increased 4 fold, how can it not be worse, especially for a healer who needs the game to be fast and responsive.

 

I got the IP from goggle, which gave me a post on these very forums from a post a staff member on an unrelated topic.

C:\Users\Alan>tracert 159.153.68.252

 

Tracing route to 159.153.68.252 over a maximum of 30 hops

 

1 1 ms 1 ms 1 ms 192.168.0.1

2 24 ms 48 ms 24 ms lo0.bne-pipe-bng2.iinet.net.au [203.215.9.249]

3 38 ms 36 ms 25 ms po2.bne-pipe-bdr2.iinet.net.au [203.215.8.32]

4 37 ms 36 ms 36 ms xe-0-0-3-0.syd-mas-core1.on.ii.net [203.215.20.1

08]

5 37 ms 186 ms 186 ms unknown.telstraglobal.net [134.159.130.113]

6 37 ms 37 ms 188 ms i-0-7-0-1.tlot-core01.bx.telstraglobal.net [202.

84.140.102]

7 175 ms 186 ms 176 ms i-0-3-0-2.paix-core01.bx.telstraglobal.net [202.

84.140.9]

8 187 ms 175 ms 187 ms i-0-7-2-0.paix-core01.bi.telstraglobal.net [202.

84.140.162]

9 186 ms 186 ms 174 ms ge4-0.mpr2.pao1.us.mfnx.net [198.32.176.11]

10 187 ms 174 ms 187 ms ge4-0.mpr2.pao1.us.mfnx.net [198.32.176.11]

11 186 ms 241 ms 186 ms xe-1-0-0.mpr2.pao1.us.above.net [64.125.31.62]

12 188 ms 196 ms 186 ms 159.153.68.53

13 198 ms 203 ms 197 ms 159.153.68.252

 

Trace complete.

Link to comment
Share on other sites

Seriously, my and most Aussies pings will be increased 4 fold, how can it not be worse, especially for a healer who needs the game to be fast and responsive

 

Yes it will and no there is nothing that will be done to fix it. While you are right to complain (and it just would not be the internet if you did not) 200 ping is fine for healing NiM EC. It is still a lot less than the 1.5s you have to wait anyway because of GCD.

 

In PvP it is sometimes annoying if both players decide to knocback as soon as they are in range and obviously the one with lower ping will win. It is far from game breaking experience though.

Link to comment
Share on other sites

Yes but your missing one thing, for us its hard to get groups going because of low population, when its 8pm Wed for me in Queensland its 3am Wed in LA, so how is that going to help us.

 

Let me get this straight, BW gives you guys a logical solution to a problem and your complaining ???

Link to comment
Share on other sites

Yes but your missing one thing, for us its hard to get groups going because of low population, when its 8pm Wed for me in Queensland its 3am Wed in LA, so how is that going to help us.

 

Dude, it's not going to be hard to get groups. The lightest populated time of day is the 2 hours preceeding server rollover. It's still only marginally less populated at that hour than dalborra is at peak hour.

Link to comment
Share on other sites

I'm an Aussie (live in Canberra and no don't have NBN yet), and i have been on this server since probably October last year when i re-rolled. I have not had any issues with PVP or PVE pops at any time of the day. You get the occasional 10min wait sometimes but that is few and far between. And the issues with the ping/latency( I'm usually around 180-220ms sometimes spike to 280 in PVP), well you get used to it. Missing some interrupts/knock backs and fake GCDs can be annoying, but you cant have everything, and most of the people on the server are pretty cool (actually prefer it to the ************ on the Aussie servers :S)
Link to comment
Share on other sites

Seriously, my and most Aussies pings will be increased 4 fold, how can it not be worse, especially for a healer who needs the game to be fast and responsive.
A tank in our guild has been playing with us since beta from Oz, it is way more imperative that a tank be fast and responsive than a healer (My main is a healer), and other than a few lag spikes (that are few and far between) we have never had a issue with him tanking or dpsing any operation. Edited by mikebevo
Link to comment
Share on other sites

Bottom line is you will have people to play with at anytime and you will have a full vibrant server to play on. I was on the server transfer from a dead server and when I transfered just having people on the planets to do heroics and level with was huge. Not to mention going through warzones with new people all the time. Trust me if you can deal with the ping you will be very happy.
Link to comment
Share on other sites

Bottom line is you will have people to play with at anytime and you will have a full vibrant server to play on. I was on the server transfer from a dead server and when I transfered just having people on the planets to do heroics and level with was huge. Not to mention going through warzones with new people all the time. Trust me if you can deal with the ping you will be very happy.

 

How exactly is going through warzones with new people exciting, most people in dalborra would rather q with 8 of their own guild then pugs.

Link to comment
Share on other sites

I'm from Melbourne, I get around 179-192ms on The Harbinger, I've been playing on PvE West servers since Early Access in 2011 and that's the ping range it usually stays around. For PvE it's perfectly fine, though it can be noticed in warzones that you have a worse reaction time due to the lag.
Link to comment
Share on other sites

Pinging 159.153.68.252 with 32 bytes of data:

 

Reply from 159.153.68.252: bytes=32 time=178ms TTL=239

Reply from 159.153.68.252: bytes=32 time=175ms TTL=239

Reply from 159.153.68.252: bytes=32 time=170ms TTL=239

Reply from 159.153.68.252: bytes=32 time=171ms TTL=239

 

Ping statistics for 159.153.68.252:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 170ms, Maximum = 178ms, Average = 173ms

 

 

Melbourne, Telstra Cable.

 

I can live with this.

Link to comment
Share on other sites

Pinging 159.153.68.252 with 32 bytes of data:

Reply from 159.153.68.252: bytes=32 time=161ms TTL=240

Reply from 159.153.68.252: bytes=32 time=159ms TTL=240

Reply from 159.153.68.252: bytes=32 time=158ms TTL=240

Reply from 159.153.68.252: bytes=32 time=157ms TTL=240

 

Ping statistics for 159.153.68.252:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 157ms, Maximum = 161ms, Average = 158ms

 

Melbourne telstra cable here also - it's mainly the perth people who'll be feeling the high ping :(

Edited by parbs
Link to comment
Share on other sites

Heres my average result

Minimum = 183ms, Maximum = 191ms, Average = 186ms

 

I can live with this, I m in Melbourne VIC on Bigpond ADSL2+with 30.5db down line attenuation / 6 db Snr margin down

 

 

here are all results

 

Pinging 159.153.68.252 with 32 bytes of data:

Reply from 159.153.68.252: bytes=32 time=190ms TTL=237

Reply from 159.153.68.252: bytes=32 time=184ms TTL=237

Reply from 159.153.68.252: bytes=32 time=214ms TTL=237

Reply from 159.153.68.252: bytes=32 time=184ms TTL=237

 

Ping statistics for 159.153.68.252:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 184ms, Maximum = 214ms, Average = 193ms

 

Pinging 159.153.68.252 with 32 bytes of data:

Reply from 159.153.68.252: bytes=32 time=181ms TTL=237

Reply from 159.153.68.252: bytes=32 time=189ms TTL=237

Reply from 159.153.68.252: bytes=32 time=185ms TTL=237

Reply from 159.153.68.252: bytes=32 time=185ms TTL=237

 

Ping statistics for 159.153.68.252:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 181ms, Maximum = 189ms, Average = 185ms

 

Pinging 159.153.68.252 with 32 bytes of data:

Reply from 159.153.68.252: bytes=32 time=184ms TTL=237

Reply from 159.153.68.252: bytes=32 time=184ms TTL=237

Reply from 159.153.68.252: bytes=32 time=190ms TTL=237

Reply from 159.153.68.252: bytes=32 time=186ms TTL=237

 

Ping statistics for 159.153.68.252:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 184ms, Maximum = 190ms, Average = 186ms

 

Pinging 159.153.68.252 with 32 bytes of data:

Reply from 159.153.68.252: bytes=32 time=182ms TTL=237

Reply from 159.153.68.252: bytes=32 time=184ms TTL=237

Reply from 159.153.68.252: bytes=32 time=185ms TTL=237

Reply from 159.153.68.252: bytes=32 time=200ms TTL=237

 

Ping statistics for 159.153.68.252:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 182ms, Maximum = 200ms, Average = 187ms

 

C:\Windows\system32>ping 159.153.68.252

 

Pinging 159.153.68.252 with 32 bytes of data:

Reply from 159.153.68.252: bytes=32 time=185ms TTL=237

Reply from 159.153.68.252: bytes=32 time=185ms TTL=237

Reply from 159.153.68.252: bytes=32 time=185ms TTL=237

Reply from 159.153.68.252: bytes=32 time=189ms TTL=237

 

Ping statistics for 159.153.68.252:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 185ms, Maximum = 189ms, Average = 186ms

 

C:\Windows\system32>ping 159.153.68.252

 

Pinging 159.153.68.252 with 32 bytes of data:

Reply from 159.153.68.252: bytes=32 time=184ms TTL=237

Reply from 159.153.68.252: bytes=32 time=188ms TTL=237

Reply from 159.153.68.252: bytes=32 time=186ms TTL=237

Reply from 159.153.68.252: bytes=32 time=186ms TTL=237

 

Ping statistics for 159.153.68.252:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 184ms, Maximum = 188ms, Average = 186ms

 

Pinging 159.153.68.252 with 32 bytes of data:

Reply from 159.153.68.252: bytes=32 time=184ms TTL=237

Reply from 159.153.68.252: bytes=32 time=186ms TTL=237

Reply from 159.153.68.252: bytes=32 time=192ms TTL=237

Reply from 159.153.68.252: bytes=32 time=185ms TTL=237

 

Ping statistics for 159.153.68.252:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 184ms, Maximum = 192ms, Average = 186ms

 

Pinging 159.153.68.252 with 32 bytes of data:

Reply from 159.153.68.252: bytes=32 time=191ms TTL=237

Reply from 159.153.68.252: bytes=32 time=187ms TTL=237

Reply from 159.153.68.252: bytes=32 time=186ms TTL=237

Reply from 159.153.68.252: bytes=32 time=190ms TTL=237

 

Ping statistics for 159.153.68.252:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 186ms, Maximum = 191ms, Average = 188ms

 

Pinging 159.153.68.252 with 32 bytes of data:

Reply from 159.153.68.252: bytes=32 time=183ms TTL=237

Reply from 159.153.68.252: bytes=32 time=188ms TTL=237

Reply from 159.153.68.252: bytes=32 time=184ms TTL=237

Reply from 159.153.68.252: bytes=32 time=191ms TTL=237

 

Ping statistics for 159.153.68.252:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 183ms, Maximum = 191ms, Average = 186ms

 

 

 

Edited by xxpcwizardxx
Link to comment
Share on other sites

Yes it will and no there is nothing that will be done to fix it. While you are right to complain (and it just would not be the internet if you did not) 200 ping is fine for healing NiM EC. It is still a lot less than the 1.5s you have to wait anyway because of GCD.

 

In PvP it is sometimes annoying if both players decide to knocback as soon as they are in range and obviously the one with lower ping will win. It is far from game breaking experience though.

 

Seriously have you ever even been in a warzone? 200ms IS GAME BREAKING ****, especially when your opponents all have 20ms. It was bad enough on wow, I wouldn't even want to stick around to see how ****** it ends up here.

Link to comment
Share on other sites

Seriously have you ever even been in a warzone? 200ms IS GAME BREAKING ****, especially when your opponents all have 20ms. It was bad enough on wow, I wouldn't even want to stick around to see how ****** it ends up here.

 

Game breaking? not sure. But I can't see how carnage/combat will be feasible when so much of it is about hitting thing off GCD, And timing hits off the end of ravage/master strike

Link to comment
Share on other sites

its not game breaking, i have been playing on the harbringer since i rerolled in October/November and i get about 180 ping on the fleet with about 220ish in wzs and youll only notice the occasional false gcd and maybe miss some interupts. like was mentioned earlier, if it starts getting up around the 4/500s then youll def have some issues playing wzs. but anything 200-300 and youll do decent if your an average player
Link to comment
Share on other sites

×
×
  • Create New...