cancel
Showing results for 
Search instead for 
Did you mean: 

MechWarrior Online Latency

SteelRat70
Newbie
Posts: 3
Registered: ‎08-04-2014

MechWarrior Online Latency

Just wondering if anyone else is experiencing problems with connecting to MWO and pings whilst playing it.
I'm on an ADSL 2 connection, and generally get pings of around 100-110.  Since the maintenance at the end of Feb, connections have been extremely erratic, starting with not being able to log in at all (the infamous "A network error occurred") and more recently pings starting off at around 200 and getting to 1500 before the game becomes completely unplayable.
Tracert to the subnet that the MWO server is on gives me this:
Tracing route to relay-1.mwtactics.com [70.42.29.65]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 15 ms 15 ms 15 ms lo0-central10.pcl-ag06.plus.net [195.166.128.187]
3 21 ms 15 ms 15 ms link-b-central10.pcl-gw02.plus.net [212.159.2.182]
4 15 ms 14 ms 14 ms xe-10-3-0.pcl-cr02.plus.net [212.159.0.214]
5 15 ms 16 ms 20 ms ae2.pcl-cr01.plus.net [195.166.129.6]
6 15 ms 18 ms 21 ms ae1.ptw-cr01.plus.net [195.166.129.0]
7 * 17 ms 16 ms te-3-4.car5.London1.Level3.net [217.163.45.181]
8 15 ms 15 ms 14 ms ae-52-52.csw2.London1.Level3.net [4.69.139.120]
9 23 ms 15 ms 15 ms ae-226-3602.edge3.London1.Level3.net [4.69.166.150]
10 82 ms 86 ms 80 ms gblx-level3-50g.London1.Level3.net [4.68.110.158]
11 379 ms 387 ms 340 ms INTERNAP.Gi1-0-11.asr1.YYZ1.gblx.net [64.214.196.26]
12 338 ms 348 ms 352 ms border1.te9-1-bbnet2.tor001.pnap.net [70.42.24.196]
13 357 ms 358 ms 351 ms relay-1.mwtactics.com [70.42.29.65]
Have a call open with PlusNet, and the MWO forums seem to show that the common denominator is PlusNet customers.  Anyone else getting similar behaviour and / or have any info on what is being done to resolve it?
Spoke to support to chase it up and they directed me here in the first instance while they try and get additional info from the tech who's working on my case.
4 REPLIES 4
Kelly
Hero
Posts: 5,497
Thanks: 380
Fixes: 9
Registered: ‎04-04-2007

Re: MechWarrior Online Latency

Hey, I just ran a trace from in the office:
Quote
> tracert 70.42.29.65
Tracing route to relay-1.mwtactics.com [70.42.29.65]
over a maximum of 30 hops:
  1    7 ms    <1 ms    1 ms  10.3.5.253
  2    10 ms    4 ms    1 ms  10.0.3.5
  3    3 ms    10 ms    1 ms  vlan380.pbs-cr01.plus.net [84.93.216.88]
  4    3 ms    1 ms    3 ms  gi6-8.ptp-cr01.plus.net [84.93.216.95]
  5    12 ms    9 ms    10 ms  gi1-22.pcl-gw01.plus.net [84.93.224.49]
  6    22 ms    10 ms    12 ms  ae3.pcl-cr01.plus.net [195.166.129.40]
  7    9 ms    20 ms    9 ms  xe-11-2-0.edge3.London2.Level3.net [212.187.201.
213]
  8    16 ms    16 ms    15 ms  vl-3201-ve-128.ebr2.London2.Level3.net [4.69.202
.177]
  9    20 ms    15 ms    17 ms  ae-43-43.ebr1.Paris1.Level3.net [4.69.159.90]
10    19 ms    27 ms    16 ms  ae-81-81.csw3.Paris1.Level3.net [4.69.161.86]
11    17 ms    25 ms    17 ms  ae-3-80.edge3.Paris1.Level3.net [4.69.168.134]
12    62 ms    23 ms    28 ms  global-crossing-xe-level3.paris1.level3.net [4.6
8.63.230]
13  104 ms  107 ms  103 ms  64.210.12.62
14  103 ms    *      98 ms  border1.te7-1-bbnet1.tor001.pnap.net [70.42.24.1
32]
15  104 ms  100 ms  108 ms  relay-1.mwtactics.com [70.42.29.65]
Trace complete.

That seems to be fine.  Your traffic appears to be taking a different route though and hitting gblx.net which seem to be adding latency!  Can you do a disconnect and reconnect and see if your traffic goes via a different router when you reconnect?
Kelly Dorset
Ex-Broadband Service Manager
Kelly
Hero
Posts: 5,497
Thanks: 380
Fixes: 9
Registered: ‎04-04-2007

Re: MechWarrior Online Latency

I've just tried from our test line which is connected to PTW and the trace doesn't go that route:
Quote
>tracert 70.42.29.65
Tracing route to relay-1.mwtactics.com [70.42.29.65]
over a maximum of 30 hops:
  1    6 ms    1 ms    1 ms  dsldevice.fcod.llnwd.net [192.168.1.254]
  2    27 ms    26 ms    31 ms  lo0.10.central10.ptw-bng01.plus.net [195.166.128.170]
  3    27 ms    27 ms    27 ms  irb.10.ptw-cr02.plus.net [84.93.249.2]
  4    27 ms    44 ms    27 ms  ae2.ptw-cr01.plus.net [195.166.129.4]
  5    33 ms    34 ms    27 ms  te-3-4.car5.London1.Level3.net [217.163.45.181]
  6    27 ms    27 ms    27 ms  ae-52-52.csw2.London1.Level3.net [4.69.139.120]
  7    29 ms    28 ms    26 ms  ae-227-3603.edge3.London1.Level3.net [4.69.166.154]
  8    38 ms    28 ms    28 ms  gblx-level3-50g.London1.Level3.net [4.68.110.158]
  9  126 ms  126 ms  125 ms  64.214.150.82
10  125 ms  125 ms  125 ms  border1.te9-1-bbnet2.tor001.pnap.net [70.42.24.196]
11  128 ms  129 ms  129 ms  relay-1.mwtactics.com [70.42.29.65]
Trace complete.

Kelly Dorset
Ex-Broadband Service Manager
SteelRat70
Newbie
Posts: 3
Registered: ‎08-04-2014

Re: MechWarrior Online Latency

I have done a number of full power cycles of the router and the route tends to stay the same.
I'll give it another go tonight and post results.
SteelRat70
Newbie
Posts: 3
Registered: ‎08-04-2014

Re: MechWarrior Online Latency

Interesting.  I did chase the call up with support again this afternoon and when I got home power cycled the router again.
Completely different route this time that avoids the problem hop it had before.  Pings aren't as good as before the maintenance, but a damn site better than what they've been recently, and rock solid at 118ms on a rolling ping.
Tracing route to relay-1.mwtactics.com [70.42.29.65]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    14 ms    13 ms    14 ms  lo0-central10.pcl-ag07.plus.net [195.166.128.188]
  3    15 ms    16 ms    15 ms  link-a-central10.pcl-gw01.plus.net [212.159.2.184]
  4    13 ms    13 ms    13 ms  xe-9-0-0.pcl-cr01.plus.net [212.159.0.216]
  5    14 ms    14 ms    14 ms  xe-11-2-0.edge3.London2.Level3.net [212.187.201.213]
  6    20 ms    20 ms    20 ms  vl-3201-ve-128.ebr2.London2.Level3.net [4.69.202.177]
  7    20 ms    20 ms    20 ms  ae-42-42.ebr1.Paris1.Level3.net [4.69.159.86]
  8    20 ms    21 ms    20 ms  ae-71-71.csw2.Paris1.Level3.net [4.69.161.82]
  9    27 ms    20 ms    20 ms  ae-2-70.edge3.Paris1.Level3.net [4.69.168.70]
10    20 ms    21 ms    20 ms  global-crossing-xe-level3.paris1.level3.net [4.68.63.230]
11  118 ms  119 ms  118 ms  INTERNAP.Gi1-0-11.asr1.YYZ1.gblx.net [64.214.196.26]
12  103 ms  103 ms  103 ms  border1.te9-1-bbnet2.tor001.pnap.net [70.42.24.196]
13  119 ms  123 ms  119 ms  relay-1.mwtactics.com [70.42.29.65]
Trace complete.