56 replies to this topic

[ShaggyMoose]

This has happened on and off over the years with Mechwarrior Online, however now seems to be particularly bad. Not sure I running trace route against the right servers... Anyway, the pings I am getting seem to be reflected in game. I see Europe in the routing for US and the Oceanic ping is lousy! People are starting to complain I am warping, which wasn't the case before. Anyone having the same issue from Sydney? My ISP is Internode.

Oceanic – 101.100.201.86 – Ping ~220 (best ever is 140)

Tracing route to 86.201.100.101.in-addr.arpa [101.100.201.86]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.254
2 24 ms 25 ms 25 ms lo0.lns20.syd4.on.ii.net [150.101.32.75]
3 25 ms 24 ms 25 ms xe-11-2-1.cr1.syd4.on.ii.net [150.101.35.11]
4 251 ms 238 ms 238 ms ae5.br1.syd4.on.ii.net [150.101.33.48]
5 224 ms 224 ms 224 ms te0-0-0-0.br1.hkg2.on.ii.net [150.101.33.199]
6 178 ms 177 ms 178 ms te1-1-0.bdr1.sin1.on.ii.net [150.101.33.222]
7 225 ms 226 ms 226 ms gw-4657.starhub.com.sg [203.16.211.190]
8 180 ms 180 ms 180 ms w118012041.w118012.starhub.net.sg [203.118.12.41]
9 226 ms 225 ms 225 ms an-atl-int11.starhub.net.sg [203.118.15.82]
10 180 ms 179 ms 180 ms 203.116.7.78
11 225 ms 225 ms 226 ms 86.201.100.101.in-addr.arpa [101.100.201.86]

US (Canada) – 192.99.109.129 – Ping ~320 (best ever is 250)

Tracing route to 192.99.109.129 over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.254
2 24 ms 25 ms 24 ms lo0.lns20.syd4.on.ii.net [150.101.32.75]
3 25 ms 25 ms 25 ms xe-11-2-1.cr1.syd4.on.ii.net [150.101.35.11]
4 26 ms 25 ms 26 ms ae5.br1.syd4.on.ii.net [150.101.33.48]
5 171 ms 172 ms 172 ms te0-1-1-2.br2.lax1.on.ii.net [203.16.213.190]
6 * * * Request timed out.
7 241 ms 237 ms 238 ms be100-1013.nwk-5-a9.nj.us [198.27.73.165]
8 242 ms 243 ms 243 ms be10-1018.bhs-g2-a9.qc.ca [192.99.146.101]
9 243 ms 243 ms 242 ms vl21.bhs-g2-a75.qc.ca [198.27.73.91]
10 322 ms 322 ms 321 ms be11.sbg-g1-a9.fr.eu [213.251.128.0]
11 318 ms 318 ms 318 ms rbx-g5-a9.fr.eu [37.187.36.16]
12 * * * Request timed out.
13 322 ms 322 ms 346 ms 192.99.109.129

[Daidachi]

I'm in Sydney and with internode as well - will check when I get home later and advise my results.

Edit: Just tested, average for OC is 175ms, NA 244ms. EU I don't bother about generally since it's consistently 320ms +.

Edited by Daidachi, 19 August 2016 - 05:01 AM.

[Liveish]

IP addresses:
North American:
192.99.109.192
192.99.40.103
European:
5.135.129.195
Oceanic:
101.100.201.86

BTW your ping in lower than mine and i have no problems.

Does you ping go up and down ? run a ping test when playing Ping IP address -t

Edited by live1991, 19 August 2016 - 04:47 AM.

[ShaggyMoose]

Pings are fairly consistent without a lot of jitter.

[justcallme A S H]

I'm not bad to Oceanic




4 10 ms 14 ms 13 ms bundle-ether4.win-edge901.melbourne.telstra.net [203.50.76.10]
5 10 ms 13 ms 12 ms bundle-ether11.win-core10.melbourne.telstra.net [203.50.11.107]
6 28 ms 23 ms 23 ms bundle-ether6.fli-core1.adelaide.telstra.net [203.50.11.90]
7 51 ms 51 ms 47 ms bundle-ether5.wel-core3.perth.telstra.net [203.50.11.19]
8 52 ms 51 ms 59 ms tengige0-8-0-5-1.pie-core1.perth.telstra.net [203.50.6.198]
9 50 ms 50 ms 50 ms tengige0-0-1-0.pthp-core01.perth.net.reach.com [203.50.13.250]
10 102 ms 103 ms 100 ms i-0-0-1-0.skdi-core01.bx.telstraglobal.net [202.84.143.2]
11 102 ms 102 ms 101 ms i-0-3-0-0.6ntp02.bi.telstraglobal.net [202.84.243.82]
12 100 ms 99 ms 101 ms 203.116.5.157
13 99 ms 102 ms 111 ms 203.118.15.181
14 101 ms 108 ms 101 ms an-ats-int11.starhub.net.sg [203.118.15.114]
15 102 ms 101 ms 102 ms 203.116.5.246
16 * * * Request timed out.
17 99 ms 99 ms 99 ms 86.201.100.101.in-addr.arpa [101.100.201.86]

I'm in Melb

NFI why I go WA, MEL, ADL, PER and then out... If I'm reading that correctly?



My US is this:



4 10 ms 12 ms 13 ms bundle-ether4.win-edge901.melbourne.telstra.net [203.50.76.10]
5 11 ms 11 ms 12 ms bundle-ether11.win-core10.melbourne.telstra.net [203.50.11.107]
6 25 ms 27 ms 23 ms bundle-ether12.ken-core10.sydney.telstra.net [203.50.11.122]
7 24 ms 25 ms 25 ms bundle-ether1.pad-gw11.sydney.telstra.net [203.50.6.61]
8 22 ms 21 ms 22 ms bundle-ether1.sydp-core04.sydney.reach.com [203.50.13.90]
9 181 ms 171 ms 168 ms i-12.paix-core01.bx.telstraglobal.net [202.84.136.194]
10 169 ms 169 ms 170 ms i-0-5-0-5.paix02.bi.telstraglobal.net [202.40.149.126]
11 * * * Request timed out.
12 216 ms 216 ms 217 ms be100-1233.chi-5-a9.il.us [198.27.73.151]
13 234 ms 239 ms 233 ms be10-1313.bhs-g2-a9.qc.ca [198.27.73.198]
14 240 ms 239 ms 238 ms vl20.bhs-g2-a75.qc.ca [192.99.146.51]
15 232 ms 233 ms 233 ms po7.bhs-s3-6k.qc.ca [198.27.73.142]
16 239 ms 239 ms 239 ms ns7000224.ip-192-99-40.net [192.99.40.103]


US is pretty consistent usually. Again the WA stuff first... :/

Edited by justcallme A S H, 16 January 2017 - 10:56 PM.

[ShaggyMoose]

Today my US and Oceanic pings are more or less equal around 240...

[Liveish]

you got NBN or ADSL ?

What profile are you set too ?

[ShaggyMoose]

ADSL2+

What would "profile" mean in that context?

[Liveish]

http://www.internode...adsl2_profiles/

I used to use[color=#444444] Low Latency[/color]

[ShaggyMoose]

Apparently my plan doesn't support this.

Will call them and see if there is something they can do. Their support is usually pretty good.

[Kynesis]

My issue isn't with the ping per-se but the fact that the game (and website) are frequently unavailable (for extended periods).

I'm in Sydney and use cable, I rarely have any trouble with other games or services and when I do, it's just a little higher ping than I'd like. The only game that's properly unplayable due to ping is SWTOR and that just hasn't been a concern for several years now because they've nearly all of their non-US players (and other reasons to do with primitive, un-evolved gameplay).

With MWO the website tends only to be available about half the time and days go by where I can't log into the game - during the last event for example, I missed out on several days participation because I simply couldn't log in.

I've come to the forums (counting myself lucky that the website is available at all) for a thread just like this because I was booted out of the game and can't log in. My internet connectivity is totally fine at this time, as noted earlier I have no trouble accessing other games or services while MWO is unavailable.

When the game works, my ping isn't an issue - it's higher than the people I'm playing against of course but the lag is almost imperceptible.

While the game is unavailable right now, here are a few traces, as you'll see there's on apparent reason why the severs should not be available to external contact but the login servers still deny access.



Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 8 ms 7 ms 10.58.0.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 9 ms 10 ms 9 ms 211.29.126.153
7 9 ms 11 ms 10 ms 198.142.139.118
8 9 ms 10 ms 10 ms 198.142.139.134
9 164 ms 165 ms 166 ms 203.208.190.137
10 175 ms 174 ms 172 ms 203.208.171.13
11 168 ms 171 ms 171 ms 203.208.172.234
12 169 ms 168 ms 168 ms paloalto1.pao.seabone.net [198.32.176.70]
13 242 ms 234 ms 235 ms et9-3-0.miami15.mia.seabone.net [195.22.199.179]
14 233 ms 235 ms 231 ms et10-3-0.miami15.mia.seabone.net [89.221.41.177]
15 * * 239 ms po99-155.mia-5-6k.fl.us [178.32.135.208]
16 241 ms 240 ms 241 ms be100-1263.chi-1-a9.il.us [178.32.135.5]
17 258 ms 262 ms 260 ms be10-1312.bhs-g1-a9.qc.ca [198.27.73.196]
18 251 ms 259 ms 259 ms vl21.bhs-g1-a75.qc.ca [198.27.73.63]
19 258 ms 260 ms 259 ms bhs-g5-a9.qc.ca [178.32.135.194]
20 259 ms 257 ms 256 ms mwomercs.com [192.99.109.192]

Trace complete.



Tracing route to ns7000224.ip-192-99-40.net [192.99.40.103]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 8 ms 7 ms 10.58.0.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 11 ms 11 ms 12 ms 198.142.250.233
8 18 ms 11 ms 19 ms 198.142.139.118
9 9 ms 16 ms 9 ms 198.142.139.134
10 187 ms 165 ms 159 ms 203.208.177.81
11 171 ms 173 ms 169 ms 203.208.149.253
12 166 ms 168 ms 165 ms 203.208.172.234
13 167 ms 167 ms 167 ms paloalto1.pao.seabone.net [198.32.176.70]
14 241 ms 246 ms 243 ms et4-3-0.miami15.mia.seabone.net [195.22.199.177]
15 240 ms 244 ms 239 ms et4-3-0.miami15.mia.seabone.net [195.22.199.177]
16 244 ms * * po99-155.mia-5-6k.fl.us [178.32.135.208]
17 245 ms 244 ms 245 ms be100-1265.chi-1-a9.il.us [178.32.135.9]
18 286 ms 266 ms 274 ms be10-1312.bhs-g1-a9.qc.ca [198.27.73.196]
19 263 ms 264 ms 264 ms vl20.bhs-g1-a75.qc.ca [198.27.73.229]
20 293 ms 267 ms 270 ms po5.bhs-s4-6k.qc.ca [198.27.73.144]
21 266 ms 263 ms 262 ms ns7000224.ip-192-99-40.net [192.99.40.103]

Trace complete.



Tracing route to 86.201.100.101.in-addr.arpa [101.100.201.86]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 7 ms 7 ms 10.58.0.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 12 ms 12 ms 20 ms 198.142.250.241
8 10 ms 10 ms 11 ms 198.142.139.118
9 12 ms 11 ms 9 ms 198.142.139.134
10 122 ms 123 ms 123 ms BHA-0017.gw1.hkg3.10026.telstraglobal.net [61.14.134.92]
11 153 ms 165 ms 151 ms ae2-0.gw2.sin0.10026.telstraglobal.net [61.14.157.182]
12 154 ms 153 ms 155 ms ip-202-147-32-139.asianetcom.net [202.147.32.139]
13 154 ms 152 ms 159 ms 203.116.6.206
14 151 ms 151 ms 157 ms 116.92.245.103.sgsvr.com [103.245.92.116]
15 152 ms 154 ms 152 ms 86.201.100.101.in-addr.arpa [101.100.201.86]

Trace complete.

Edited by Kynesis, 19 October 2016 - 07:48 PM.

[cleghorn6]

justcallme A S H, on 19 August 2016 - 11:40 PM, said:

3 66 ms 12 ms 12 ms CPE-58-160-248-1.wa.bigpond.net.au [58.160.248.1]

3 11 ms 11 ms 12 ms CPE-58-160-248-1.wa.bigpond.net.au [58.160.248.1]

US is pretty consistent usually. Again the WA stuff first... :/

You would probably find that the "wa" in *.wa.bigpond.net.au doesn't indicate location. Looking at where it comes up in your routes, it will be some kind of border device between the ADSL side and the core network. Something-starting-with-W Aggregator perhaps? There isn't enough latency added for it to actually be in WA and as bad as Telstra can be, ever they aren't bad enough to bounce things across the Nullarbor for no reason (unless they've broken something).

I'm impressed that your Oceanic ping is better than mine (at the moment), I'm in Perth. My Oceanic ping has been as low as 60 but sits at about 140 currently. There have been a lot of disturbances to trans-national infrastructure in SE Asia in the last couple years so routes and pings have been all over the place.

[justcallme A S H]

Ah OK cool. A logical explanation.

I'm extreme cable, not the standard. Perhaps that helps with everything?

That said lately its been a bit higher than normal.

[Kynesis]

I've had a lot of trouble accessing the game and even just the website recently - each seems to be available for about 1-3 hours each day.

Here are some recent trace results:

Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 17 ms 7 ms 10 ms 10.58.0.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 11 ms 12 ms 12 ms 211.29.126.153
7 9 ms 13 ms 27 ms 198.142.139.118
8 19 ms 11 ms 11 ms 198.142.139.134
9 165 ms 168 ms 166 ms 203.208.190.137
10 174 ms 190 ms 197 ms 203.208.171.13
11 177 ms 169 ms 177 ms 203.208.172.234
12 168 ms 173 ms 169 ms paloalto1.pao.seabone.net [198.32.176.70]
13 234 ms 235 ms 232 ms et10-3-0.miami15.mia.seabone.net [89.221.41.177]
14 247 ms 236 ms 235 ms et9-3-0.miami15.mia.seabone.net [195.22.199.179]
15 257 ms * 264 ms po99-155.mia-5-6k.fl.us [178.32.135.208]
16 268 ms 276 ms 270 ms be100-1263.chi-1-a9.il.us [178.32.135.5]
17 284 ms * 280 ms be10-1312.bhs-g1-a9.qc.ca [198.27.73.196]
18 266 ms 272 ms 266 ms vl21.bhs-g1-a75.qc.ca [198.27.73.63]
19 276 ms 300 ms * bhs-g5-a9.qc.ca [178.32.135.194]
20 * * * Request timed out.
21 * * 262 ms mwomercs.com [192.99.109.192]

Trace complete.

Tracing route to APoitiers-656-1-619-101.w86-201.abo.wanadoo.fr [86.201.100.101]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 16 ms 8 ms 10.58.0.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 10 ms 10 ms 12 ms 211.29.126.149
7 13 ms 13 ms 12 ms 198.142.139.118
8 10 ms 14 ms 11 ms 198.142.139.134
9 218 ms 212 ms 228 ms 203.208.190.161
10 194 ms 188 ms 190 ms ae8.cr2-lax2.ip4.gtt.net [199.229.229.221]
11 216 ms 204 ms 204 ms xe-8-1-2.lax10.ip4.gtt.net [89.149.130.102]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Tracing route to 192.99.109.192 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 28 ms 10 ms 15 ms 10.58.0.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 18 ms 10 ms 22 ms 211.29.126.153
7 11 ms 10 ms 10 ms 198.142.139.118
8 31 ms 27 ms 18 ms 198.142.139.134
9 222 ms 221 ms 233 ms 203.208.190.137
10 224 ms 229 ms 225 ms 203.208.171.13
11 230 ms 261 ms 217 ms 203.208.172.234
12 218 ms 223 ms 227 ms paloalto1.pao.seabone.net [198.32.176.70]
13 270 ms 293 ms 280 ms et9-3-0.miami15.mia.seabone.net [195.22.199.179]
14 280 ms 303 ms 292 ms et9-3-0.miami15.mia.seabone.net [195.22.199.179]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

This for comparison of a session that was working relatively well, for about half an hour

Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 8 ms 10 ms 10.58.0.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 9 ms 12 ms 10 ms 211.29.126.153
7 16 ms 11 ms 14 ms 198.142.139.118
8 8 ms 11 ms 10 ms 198.142.139.134
9 164 ms 170 ms 162 ms 203.208.190.137
10 173 ms 176 ms 173 ms 203.208.149.253
11 170 ms 206 ms 170 ms 203.208.172.234
12 197 ms 172 ms 171 ms paloalto1.pao.seabone.net [198.32.176.70]
13 234 ms 233 ms 231 ms et9-3-0.miami15.mia.seabone.net [195.22.199.179]
14 233 ms 231 ms 231 ms et10-3-0.miami15.mia.seabone.net [89.221.41.177]
15 261 ms * 254 ms po99-155.mia-5-6k.fl.us [178.32.135.208]
16 276 ms 267 ms 267 ms be100-1263.chi-1-a9.il.us [178.32.135.5]
17 260 ms 291 ms 262 ms be10-1312.bhs-g1-a9.qc.ca [198.27.73.196]
18 268 ms 266 ms 267 ms vl21.bhs-g1-a75.qc.ca [198.27.73.63]
19 270 ms 267 ms 279 ms bhs-g5-a9.qc.ca [178.32.135.194]
20 265 ms 267 ms 270 ms mwomercs.com [192.99.109.192]

Trace complete.


Even when I have been able to log into the game, I've been greeted by an empty mech bay.
I've finally been able to participate in a few matches this afternoon (with varying quality latency) but simultaneously find that access to the website is very spotty; Sometimes I can reach the front page but nothing else - the tabs for the MWO forums that I opened on my other computer just before trying them on my PC are still trying to connect.
Here's a current trace:


Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 7 ms 10 ms 10.58.0.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 13 ms 12 ms 11 ms 211.29.126.153
7 17 ms 26 ms 25 ms 198.142.139.118
8 10 ms 9 ms 10 ms 198.142.139.134
9 166 ms 165 ms 183 ms 203.208.190.137
10 220 ms 174 ms 175 ms 203.208.171.13
11 169 ms 179 ms 172 ms 203.208.172.234
12 172 ms 169 ms 172 ms paloalto1.pao.seabone.net [198.32.176.70]
13 251 ms 230 ms 231 ms et10-3-0.miami15.mia.seabone.net [89.221.41.177]
14 230 ms 228 ms 243 ms et9-3-0.miami15.mia.seabone.net [195.22.199.179]
15 277 ms * 268 ms po99-155.mia-5-6k.fl.us [178.32.135.208]
16 270 ms

That is the entirety of the trace. I don't know why it doesn't even say "trace complete" or finish line 16.


Tracing route to ns7000224.ip-192-99-40.net [192.99.40.103]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 12 ms 10 ms 10.58.0.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 12 ms 10 ms 12 ms 198.142.250.233
8 12 ms 11 ms 10 ms 198.142.139.118
9 21 ms 12 ms 10 ms 198.142.139.134
10 161 ms

Ditto for this one. Even with a trace like this though the game seems to be working just fine right now; I guess other servers are taking up the slack.

Edited by Kynesis, 22 October 2016 - 11:32 PM.

[Kynesis]

Turns out there was a significant DDoS attack vs the US starting last Friday
https://www.wired.co...e-ddos-dns-dyn/

I don't know if this is the source of our problems with MWO but it's worth considering as a likely source.

I'd like to thank PGI's communications team for jumping right onto this issue and let us know that PGI's network engineers exist, or at least that somebody has confirmed that the blue cables and flashing lights are still blue and/or flashing respectively.

Edited by Kynesis, 23 October 2016 - 04:32 AM.

[ChillAAA]

Kynesis, on 23 October 2016 - 04:30 AM, said:

Turns out there was a significant DDoS attack vs the US starting last Friday
https://www.wired.co...e-ddos-dns-dyn/

I don't know if this is the source of our problems with MWO but it's worth considering as a likely source.

I'd like to thank PGI's communications team for jumping right onto this issue and let us know that PGI's network engineers exist, or at least that somebody has confirmed that the blue cables and flashing lights are still blue and/or flashing respectively.

Outside of the DDoS timeframe have you seen any further issues? I'm unable to access the website and game during peak times still. Im Sydney/Optus cable. Made the mistake of not going Telstra

[cleghorn6]

That's interesting. Can you run a few traces like Kynesis did above? When it's working and when it's not.

[General Solo]

ShaggyMoose, on 23 August 2016 - 03:57 AM, said:

Apparently my plan doesn't support this.

Will call them and see if there is something they can do. Their support is usually pretty good.

If your with Internode I'm 99% sure profiles are supported
Im with them as well

Go to www.internode.on.net and logon
Once you have logged on, look on the left side of the page for SERVICES
And under SERVICES you will find INTERNODE ADSL2+ PROFILES

I use the Low Latency Annex M profile - which reduce ping by 20-40ms and increased my upload which is good for hit reg

Hope this helps

Edited by OZHomerOZ, 02 November 2016 - 05:54 PM.

[Wski]

Since the most recent patch my ping from sydney has benn stable at 260.......up from 120 anyone else seeing this?

[Liveish]

What ISP ?