129 replies to this topic

[ball0fire]

couple of bad hops (sometimes the hang on ping requests doesnt mean much) but the end result is a very short trip and lower overall ping


Tracing route to 192.99.109.129 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 32 ms 31 ms 31 ms lo0.lns20.bne7.on.ii.net [150.101.32.35]
3 31 ms 32 ms 31 ms xe-1-3-0.cr1.bne4.on.ii.net [150.101.34.22]
4 49 ms 50 ms 54 ms ae1.br1.syd4.on.ii.net [150.101.33.18]
5 195 ms 195 ms 196 ms te0-1-1-3.br2.lax1.on.ii.net [150.101.33.195]
6 346 ms * 291 ms any2ix.coresite.com [206.72.210.214]
7 255 ms * 255 ms 198.27.73.191
8 264 ms 265 ms 265 ms bhs-g2-6k.qc.ca [198.27.73.207]
9 288 ms 288 ms 289 ms 198.27.73.233
10 264 ms 264 ms 264 ms 192.99.109.129

Trace complete.


i assume thats the correct ip, its the same one you used a page back

Edited by ball0fire, 02 September 2014 - 02:52 AM.

[Oderint dum Metuant]

ball0fire, on 02 September 2014 - 02:50 AM, said:

couple of bad hops (sometimes the hang on ping requests doesnt mean much) but the end result is a very short trip and lower overall ping


Tracing route to 192.99.109.129 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 32 ms 31 ms 31 ms lo0.lns20.bne7.on.ii.net [150.101.32.35]
3 31 ms 32 ms 31 ms xe-1-3-0.cr1.bne4.on.ii.net [150.101.34.22]
4 49 ms 50 ms 54 ms ae1.br1.syd4.on.ii.net [150.101.33.18]
5 195 ms 195 ms 196 ms te0-1-1-3.br2.lax1.on.ii.net [150.101.33.195]
6 346 ms * 291 ms any2ix.coresite.com [206.72.210.214]
7 255 ms * 255 ms 198.27.73.191
8 264 ms 265 ms 265 ms bhs-g2-6k.qc.ca [198.27.73.207]
9 288 ms 288 ms 289 ms 198.27.73.233
10 264 ms 264 ms 264 ms 192.99.109.129

Trace complete.


i assume thats the correct ip, its the same one you used a page back

Aus>US> Canda.

How routing should look.

(i use the mwomercs address, the ip is from other peoples traces)

Edited by DV McKenna, 02 September 2014 - 03:01 AM.

[Amardez]

Just got off the a chat with a Friend in Canada and the server is very close to a Uni over there Strangely enough when i speed test to it I got 233 -238 over 3 test but the MWO server IP was giving me 120+ more so ummmm this is really confounding me now, as a they apperenlty have almost the same number of jumps (most of the the same) in trace rout 2 more on MWO and they
were at the very end.

[Bront]

Yeah, My ping didn't change, but hitreg is bad and there's some serious rubberbanding and teleporting mech issues. Probably the worst I've seen it this year.

[Lily from animove]

latency from germany is around 20ms lower now.

[Grrzoot]

Midwest U.S,

Before server move- stable ping ws 34 unless a high traffic night then would climb to 52.

Sincer migration:
stable ping fluctuates between 132-154

???

[Bilbo]

Michigan. Ping didn't change(35-40), neither did the desyncs and lag.

[DarthPeanut]

Grrzoot, on 02 September 2014 - 05:21 AM, said:

Midwest U.S,

Before server move- stable ping ws 34 unless a high traffic night then would climb to 52.

Sincer migration:
stable ping fluctuates between 132-154

???

Wow, I had the opposite. My ping improved from 50-70 to mid-low 30s. Midwest U.S. also.

Have you checked your routing to see where you are getting the added latency?

Edited by DarthPeanut, 02 September 2014 - 06:50 AM.

[Tarzilman]

EU
Latency before: ~150
Latency now: ~115

*thumbs up*

Edited by Tarzilman, 02 September 2014 - 05:58 AM.

[p4r4g0n]

Amardez, on 02 September 2014 - 03:46 AM, said:

Just got off the a chat with a Friend in Canada and the server is very close to a Uni over there Strangely enough when i speed test to it I got 233 -238 over 3 test but the MWO server IP was giving me 120+ more so ummmm this is really confounding me now, as a they apperenlty have almost the same number of jumps (most of the the same) in trace rout 2 more on MWO and they
were at the very end.

Just FYI

The ping readings in-game are based on packets received by the server most likely using a protocol OTHER than ICMP which is more accurate in so far as the server is concerned. Pinging using other tools usually use the ICMP protocol which is less accurate thus explaining the difference seen when using the "ping" command and the in-game ping numbers.

[PocketAces]

Went from 265-300 to well over 350. Philippines cable

Quote

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\K>tracert 192.99.109.129

Tracing route to 192.99.109.129 over a maximum of 30 hops

1 14 ms * 11 ms 172.23.0.1
2 38 ms * 16 ms 111.68.59.161
3 27 ms * 7 ms 10GE0-3-3.MND1.skybroadband.com.ph [111.68.59.137]
4 260 ms 243 ms 236 ms xe-5-1-2.edge5.LosAngeles1.Level3.net [4.59.48.41]
5 341 ms 308 ms 303 ms vlan90.csw4.LosAngeles1.Level3.net [4.69.144.254]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 306 ms 309 ms 331 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
10 * * 352 ms level3.as3356.nj.us [178.32.135.18]
11 362 ms 349 ms 344 ms bhs-g1-6k.qc.ca [198.27.73.205]
12 344 ms 370 ms 359 ms 198.27.73.231
13 360 ms 362 ms 363 ms 192.99.109.129

Trace complete.

C:\Users\K>

[Unleashed3k]

Ping is better now, moved from 130 to around 115 but I get extrem Lags now, never had that problem before, but now i stop somewhere, still hear I can fire and when I suddenly can move again, my mech is 300-800m away from its last position. That is absolutely new for me since you moved your servers.... thumbs down PGI...

[Amardez]

p4r4g0n, on 02 September 2014 - 06:05 AM, said:

Just FYI

The ping readings in-game are based on packets received by the server most likely using a protocol OTHER than ICMP which is more accurate in so far as the server is concerned. Pinging using other tools usually use the ICMP protocol which is less accurate thus explaining the difference seen when using the "ping" command and the in-game ping numbers.

Yeah i wasn't just using the In game ping as my reading it was based on two external tools though i should have been clear.

[CG Anastasius Focht]

As i read it PGI are not going to write off the Aus/NZ mechwarriors.

Mechwarrior/BattleTech has a very strong following down under, always has.

And while i may be over enthusiastic .........

http://mwomercs.com/...-fochts-bt-art/

The replies in this thread show how the franchise has a strong fan base here in the southern hemisphere

I'm confident reading this

http://mwomercs.com/...67#entry3685967

That the team is looking at this and will do whatever they can to fix it. These people are not just game developers, they are hard core fans of the Battletech franchise too.

Hang in there folks, this issue hasnt gone un-noticed

Edited by CG Anastasius Focht, 02 September 2014 - 11:31 PM.

[mazza11]

Aussie fanatic

Latency before - 250 to 300, now 350 to 480+

Cannot play lights or quick mediums anymore or brawl really. So LRM's? now my game has become nothing but LRMwarrior online.

[POWR]

mazza11, on 02 September 2014 - 11:41 PM, said:

Aussie fanatic

Latency before - 250 to 300, now 350 to 480+

Cannot play lights or quick mediums anymore or brawl really. So LRM's? now my game has become nothing but LRMwarrior online.

Nikolai Lubkiewicz, on 02 September 2014 - 03:16 PM, said:

Hey everyone,

We've done some investigations into our NZ and AU situation. It appears that something odd is taking place and started recently with one of the major Australian ISPs. Players on this service may notice their ISP is redirecting internet traffic to and from the Americas through Asia and Europe, as opposed to across the Pacific Ocean. The concerns affecting connectivity related to this issue are not specific to just our game and will affect any games for those Australian players which use North American servers. This explains the odd jumps in pings we have seen for some Australian players as great as 100-300 higher than before, while other Oceanic players have remained unaffected. We are hoping that the ISP will have this resolved on their own as soon as they notice where their traffic is going, but in the meantime, our web-team is also investigating ways they can further assist players experiencing this issue. We thank our Oceanic friends for standing by and for their understanding.

[Grrzoot]

DarthPeanut, on 02 September 2014 - 05:52 AM, said:

Wow, I had the opposite. My ping improved from 50-70 to mid-low 30s. Midwest U.S. also. Have you checked your routing to see where you are getting the added latency?

according to the tracert i ran to here there are some black-out or no response areas as soon as i hit near the end of the line. not sure what that means but it seems im getting routed through some bad area right near the end.

[Oderint dum Metuant]

Grrzoot, on 03 September 2014 - 10:38 AM, said:

according to the tracert i ran to here there are some black-out or no response areas as soon as i hit near the end of the line. not sure what that means but it seems im getting routed through some bad area right near the end.

It may just be some of them are setup not to respond.
Without looking at it can't help you

[Amardez]

This is one of the many Trace routs i have done and I am not convinced that it is affecting other games World of tanks,
LOL , as well as 4 or 5 other games i Play on the NA servers just because of populations / that is were the first servers were.

Though none of them seem to be affected.

I want to Believe you PGI I really do but I can't see any evidence of this. Other OZ/NZ players could you please take a look at your other online games similar to MWO if you play NA servers and see how they are looking.


1 <1 ms <1 ms <1 ms Modem
2 57 ms 39 ms 39 ms
3 63 ms 62 ms 63 ms ie2-g-0-0-0.telstraclear.net [203.98.50.2]
4 62 ms 59 ms 59 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.
50.251]
5 60 ms 65 ms 62 ms unknown.telstraglobal.net [134.159.174.37]
6 196 ms 200 ms 198 ms i-0-6-1-0.tlot-core01.bx.telstraglobal.net [202.
84.142.157]
7 196 ms 196 ms 195 ms i-0-5-0-1.eqla01.bi.telstraglobal.net [202.84.25
3.6]
8 288 ms 288 ms 288 ms tisparkle-peer.eqla01.pr.telstraglobal.net [134.
159.61.26]
9 302 ms 291 ms 291 ms xe-9-3-0.paloalto2.pao.seabone.net [89.221.35.14
1]
10 292 ms 292 ms 291 ms pal-5-6k.ca.us [178.32.135.206]
11 * 354 ms * 198.27.73.188
12 355 ms 355 ms 356 ms mtl-1-6k.qc.ca [198.27.73.183]
13 357 ms 356 ms 357 ms bhs-g2-6k.qc.ca [198.27.73.3]
14 365 ms 365 ms 366 ms 198.27.73.233
15 357 ms 356 ms 357 ms 192.99.109.129

[p4r4g0n]

Using a whois tool -

Hops 3 to 9 are all either under Telstra or something Telstra should be able to do something about. You may want to ask them whether they are able to find a better route.

Hop 3 NZ
Hop 4 & 5 NZ
ping increases by approx 140ms
Hop 6 HK
Hop 7 China
ping increases by approx 88ms
Hop 8 HK
ping increases by approx 10ms
Hop 9 Germany

Hops 10 to 15 are registered to OVH or a OVH related company, ping increases by about 60ms within the OVH owned hops .... maybe PGI / IGP should talk to them.