Menu
Reply
  • 1
  • 0
  • 0
Chillysauce
Joining in
717 Views
Message 1 of 12
Flag for a moderator

Lord of the Rings Online Virgins crazy new routing to servers.

The LOTRO servers have moved Boston to New Jersey. ALL Virgin customers that play the game are reporting an unacceptable increase in ingame lag. From solid 80-120 latency to a minimium of 160 + to I have seen 230. All are saying the same.

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

C:\Users\ROBS>tracert gls.lotro.com

Tracing route to gls.lotro.com [198.252.160.30]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms routerlogin.net [XXX.XXX.X.X]
2 * * * Request timed out.
3 12 ms 9 ms 8 ms popl-core-2a-xe-815-0.network.virginmedia.net [6
2.255.65.213]
4 * * * Request timed out.
5 * * * Request timed out.
6 11 ms 11 ms 12 ms brnt-bb-1c-ae0-0.network.virginmedia.net [62.254
.42.198]
7 19 ms 12 ms 12 ms m686-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.174
]
8 * * * Request timed out.
9 84 ms 82 ms 82 ms 84.116.140.174
10 160 ms 155 ms 154 ms us-sjo01a-ri3-ae12-0.aorta.net [84.116.135.121]

11 154 ms 153 ms 156 ms sjp-brdr-05.inet.qwest.net [63.235.40.153]
12 150 ms 149 ms 150 ms ewr-cntr-11.inet.qwest.net [205.171.17.2]
13 151 ms 150 ms 150 ms 206.103.215.50
14 149 ms 150 ms 157 ms 63.236.3.130
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.

Why I am I being sent to Austria?????? Prior goin to the USA.

There are multiple threads in the LOTRO forums. It would seem to be that Virgin has an issue. Virgin Customers are not very happy with this.  So how do we go about about fixing this.........or is it a simple case that we just  have to switch ISP's.

 

 

0 Kudos
  • 12
  • 0
  • 0
Gilreth
Joining in
655 Views
Message 2 of 12
Flag for a moderator

Re: Lord of the Rings Online Virgins crazy new routing to servers.

Similar issues here...

tracert:

 

Tracing route to gls.lotro.com [198.252.160.30]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 17 ms 17 ms 30 ms brad-core-2a-xe-013-0.network.virginmedia.net [81.97.80.205]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 16 ms 27 ms 18 ms nrth-bb-1b-ae0-0.network.virginmedia.net [62.254.42.130]
8 18 ms 17 ms 19 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
9 * * * Request timed out.
10 85 ms 91 ms 94 ms us-nyc01b-rd2-ae9-0.aorta.net [84.116.140.170]
11 198 ms 165 ms 169 ms us-sjo01a-ri3-ae10-0.aorta.net [84.116.137.222]
12 160 ms 183 ms 159 ms 63-235-40-153.dia.static.qwest.net [63.235.40.153]
13 159 ms 156 ms 166 ms ewr-cntr-11.inet.qwest.net [205.171.17.2]
14 160 ms 159 ms 170 ms 206.103.215.50
15 153 ms 156 ms 153 ms 63.236.3.130
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.

aorta.net is registered in Austria but think servers are in the US (Us-nyc suggests New York and us-sjo is possibly San Jose - which would explain long round trip delay)

0 Kudos
  • 8.23K
  • 511
  • 2.26K
Superuser
Superuser
651 Views
Message 3 of 12
Flag for a moderator

Re: Lord of the Rings Online Virgins crazy new routing to servers.


Gilreth wrote:

Similar issues here...

tracert:

 

Tracing route to gls.lotro.com [198.252.160.30]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 17 ms 17 ms 30 ms brad-core-2a-xe-013-0.network.virginmedia.net [81.97.80.205]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 16 ms 27 ms 18 ms nrth-bb-1b-ae0-0.network.virginmedia.net [62.254.42.130]
8 18 ms 17 ms 19 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
9 * * * Request timed out.
10 85 ms 91 ms 94 ms us-nyc01b-rd2-ae9-0.aorta.net [84.116.140.170]
11 198 ms 165 ms 169 ms us-sjo01a-ri3-ae10-0.aorta.net [84.116.137.222]
12 160 ms 183 ms 159 ms 63-235-40-153.dia.static.qwest.net [63.235.40.153]
13 159 ms 156 ms 166 ms ewr-cntr-11.inet.qwest.net [205.171.17.2]
14 160 ms 159 ms 170 ms 206.103.215.50
15 153 ms 156 ms 153 ms 63.236.3.130
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.

aorta.net is registered in Austria but think servers are in the US (Us-nyc suggests New York and us-sjo is possibly San Jose - which would explain long round trip delay)

 


Ive highlighted the hops that seem to be causing the issue- Ping (more specifically ICMP) is only a ballpark measure of performance at a hop but you can see clearly where the latency increases. Its AFTER it leaves VM's network and starts with peering to aeorta.

And yeah the whois of the servers does fit with the geo-loc (austria or spain depending on DBase used) initially but digging deeper the hostname would indicate its US side (hop to 84.116.140.170 resolves to us-nyc01b-rd2-ae9-0.aorta.net )


0 Kudos
  • 4
  • 0
  • 0
Macdui
Joining in
640 Views
Message 4 of 12
Flag for a moderator

Re: Lord of the Rings Online Virgins crazy new routing to servers.

 

 

82ms into nyc - New York City (aorta), 155ms hop to sjo - San Jose (aorta) then sjp - likely still San Jose? (qwest) and finally ewr Newark NJ (qwest)

for a 10 mile round trip.

Can someone at Virgin Media put in a ticket to aorta.net or use another backbone?

We should be connecting to the game with latency around 85-90ms but we're getting close to double with our visit to the West Coast.

 

Tracert fragment:

  3    10 ms    13 ms     9 ms  lutn-core-2b-xe-001-0.network.virginmedia.net [62.253.98.229]
  4     *        *        *     Request timed out.
  5    12 ms    10 ms    17 ms  nrth-bb-1b-ae0-0.network.virginmedia.net [62.254.42.130]
  6    12 ms    23 ms    12 ms  m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
  7     *        *        *     Request timed out.
  8    82 ms    80 ms    82 ms  us-nyc01b-rd2-ae9-0.aorta.net [84.116.140.170]
  9   156 ms   155 ms   155 ms  us-sjo01a-ri3-ae10-0.aorta.net [84.116.137.222]
 10   157 ms   153 ms   155 ms  sjp-brdr-05.inet.qwest.net [63.235.40.153]
 11   155 ms   151 ms   154 ms  ewr-cntr-11.inet.qwest.net [205.171.17.2]
 12   159 ms   159 ms   154 ms  206.103.215.50
 13   152 ms   154 ms   152 ms  63.236.3.130
 14     *        *

0 Kudos
  • 4
  • 0
  • 0
Macdui
Joining in
639 Views
Message 5 of 12
Flag for a moderator

Re: Lord of the Rings Online Virgins crazy new routing to servers.

The current in game "lag" is all server side atm, due to the hardware update and move. But the avoidable increase latency will effect what we can do once the lag issues are resolved. As players we are much aggrieved because we were promised a datacentre in Amsterdam and it's likely we'll be stuck with a datacentre in New Jersey for the foreseeable future and we want to limit our losses as much as possible.
0 Kudos
  • 8.23K
  • 511
  • 2.26K
Superuser
Superuser
597 Views
Message 6 of 12
Flag for a moderator

Re: Lord of the Rings Online Virgins crazy new routing to servers.


Macdui wrote:

 

 

82ms into nyc - New York City (aorta), 155ms hop to sjo - San Jose (aorta) then sjp - likely still San Jose? (qwest) and finally ewr Newark NJ (qwest)

for a 10 mile round trip.

Can someone at Virgin Media put in a ticket to aorta.net or use another backbone?



It wouldn't make any difference what VM do. If it were going wrong in their network or at peering they could influence it. As its gone out of their network, through peering and the problems lie with aeorta stateside, nowt they can do. The routing tables at the transatlantic hop will be pointing into aeorta, likely because whoever runs the servers peers with them (its bouncing round their network stateside which is a decent indicator they are the peering of choice for the data center the servers reside in). As such its the guys game end you should be asking to use "a different backbone" not VM.

We see it all the time. Although you are paying premium prices for membership, the datacenters and peering are usually as cheap as the provider can get. And there's always a price in latency attached.  Without going VERY in depth, best guess is they are using load balancing instead of increasing capacity and that is why your packets are routing weirdly stateside.

 

 


0 Kudos
  • 12
  • 0
  • 0
Gilreth
Joining in
556 Views
Message 7 of 12
Flag for a moderator

Re: Lord of the Rings Online Virgins crazy new routing to servers.

Interesting thing is it is only VM customers who are getting aorta.net routing - all other tracert's do not have it in so it is not to do with Turbine's peering but more likely VM's as it is the first hop that responds outside the VM network (ntli.net is also VM - old NTL address). So we are bugging both ends of the connection - as not first time we have had issues with VM & LOTRO and routing.

0 Kudos
  • 4
  • 0
  • 0
Macdui
Joining in
540 Views
Message 8 of 12
Flag for a moderator

Re: Lord of the Rings Online Virgins crazy new routing to servers.

The thing is if we get the nod that the datacentres will remain in NJ you might get bunch of us looking to BT, Sky, Plusnet, can't believe I'm saying it TalkTalk for a deal.
0 Kudos
  • 6
  • 0
  • 0
brighamg
Tuning in
467 Views
Message 9 of 12
Flag for a moderator

Re: Lord of the Rings Online Virgins crazy new routing to servers.

As posted on the official lotro Server thread https://www.lotro.com/forums/showthread.php?593588-Servers-are-back-Online-Official-Thread&p=7516195... ...

This has not changed as the same test was done 2 mins ago... with last weeks test I added the ip checkup companies

 

SpeedTest.Net
1/12/2016 00:31 GMT 86.~.~.~ 155.37 Mb/s 11.87 Mb/s 7 ms Manchester < 50 mi 

Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.


C:\Users\Brigham>Tracert gls.lotro.com


Tracing route to gls.lotro.com [198.252.160.30]
over a maximum of 30 hops:


1 6 ms 6 ms 5 ms 10.137.224.1
2 5 ms 7 ms 9 ms bagu-core-2b-ae6-757.network.virginmedia.net [80.5.163.121] (Virgin Media UK)
3 * * * Request timed out.
4 * * * Request timed out.
5 36 ms 10 ms 24 ms nrth-bb-1b-ae1-0.network.virginmedia.net [62.254.42.218] (Virgin Media UK)
6 12 ms 13 ms 12 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162] (Virgin Media UK)
7 * * * Request timed out.
8 82 ms 83 ms 88 ms us-nyc01b-rd2-ae9-0.aorta.net [84.116.140.170] (Liberty Global Europe - Netherlands)
9 158 ms 158 ms 156 ms us-sjo01a-ri3-ae10-0.aorta.net [84.116.137.222] (Liberty Global Europe - Netherlands)
10 155 ms 157 ms 160 ms 63-235-40-153.dia.static.qwest.net [63.235.40.153] (Qwest Communications Company - LA)
11 155 ms 151 ms 152 ms ewr-cntr-11.inet.qwest.net [205.171.17.2] (Qwest Communications Company - LA)
12 151 ms 153 ms 152 ms 206.103.215.50 (Savvis - US)
13 152 ms 152 ms 151 ms 63.236.3.130 (Qwest Communications Company, LLC - LA)
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.

Tags (1)
0 Kudos
  • 6
  • 0
  • 0
brighamg
Tuning in
361 Views
Message 10 of 12
Flag for a moderator

Re: Lord of the Rings Online Virgins crazy new routing to servers.

GM came on tonight to ask how the lag was with VM users --- evernight ... seems someone has been fixing some routes - latency is 95 area ... seems 8/9 of trace has a nice speed now - (to compare previous post)

 

Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
 
C:\Users\Brigham>Tracert gls.lotro.com
 
Tracing route to gls.lotro.com [198.252.160.30]
over a maximum of 30 hops:
 
  1     6 ms     9 ms     6 ms  10.137.224.1
  2     6 ms     6 ms     7 ms  bagu-core-2b-ae6-757.network.virginmedia.net [80.5.163.121]
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5    15 ms    11 ms    11 ms  nrth-bb-1b-ae1-0.network.virginmedia.net [62.254.42.218]
  6    12 ms    13 ms    13 ms  m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
  7     *        *        *     Request timed out.
  8   105 ms    83 ms    82 ms  us-nyc01b-rd2-ae9-0.aorta.net [84.116.140.170]
  9    88 ms    82 ms    86 ms  us-nyc01b-ri2-ae3-0.aorta.net [84.116.137.194]
 10    81 ms    87 ms    83 ms  nyc2-brdr-01.inet.qwest.net [63.235.40.165]
 11    90 ms    84 ms    82 ms  ewr-cntr-11.inet.qwest.net [205.171.17.2]
 12    86 ms    84 ms    83 ms  206.103.215.50
 13    83 ms    82 ms    83 ms  63.236.3.130
 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.
 

 

 

0 Kudos