Menu
Reply
  • 3
  • 0
  • 0
velve
Joining in
324 Views
Message 1 of 11
Flag for a moderator

Summit aint reet :/

I'm always hesitent to blame the ISP when experienceing problems with non UK servers, VM don't own every piece of hardware between me and the location I'm trying to reach. I'm currently playing LoTRO and have been experiencing loss for the last 48hrs or so, making certain aspects of game play (instances/raids) unplayable. I'm not the only one, people all over Europe are reporting similar issues as can be seen in this thread https://www.lotro.com/forums/showthread.php?648913-Connection-issue

Here's my tracert to lotro.com

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

1 9 ms 4 ms 8 ms 192.168.0.1
2 13 ms 8 ms 8 ms 10.86.112.1
3 14 ms 11 ms 25 ms croy-core-2b-xe-112-0.network.virginmedia.net [81.96.226.33]
4 * * * Request timed out.
5 18 ms 18 ms 18 ms nrth-ic-1-ae1-0.network.virginmedia.net [62.254.42.218]
6 71 ms 20 ms 18 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
7 * * * Request timed out.
8 88 ms 88 ms 93 ms us-nyc01b-rd2-ae9-0.aorta.net [84.116.140.170]
9 88 ms 83 ms 88 ms us-nyc01b-ri2-ae3-0.aorta.net [84.116.137.194]
10 88 ms 83 ms 86 ms nyc2-brdr-01.inet.qwest.net [63.235.40.165]
11 88 ms 98 ms 88 ms ewr-cntr-11.inet.qwest.net [205.171.17.2]
12 93 ms 93 ms 87 ms 206.103.215.50
13 88 ms 88 ms 88 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.

As you can see things start to go badly wrong @ 63.236.2.130

A quick IP lookup gives this result http://www.ip-tracker.org/locator/ip-lookup.php?ip=63.236.3.130

But there are a couple of time outs that look to be on this side of the pond, so i'll add a couple of tracert results from .co.uk address in the hope it helps track down the problem.

Tracing route to bbc.co.uk [212.58.244.22]
over a maximum of 30 hops:

1 5 ms 1 ms 1 ms 192.168.0.1
2 10 ms 11 ms 9 ms 10.86.112.1
3 12 ms 11 ms 10 ms croy-core-2a-xe-112-0.network.virginmedia.net [81.96.226.29]
4 * * * Request timed out.
5 * * * Request timed out.
6 21 ms 45 ms 28 ms brhm-bb-1c-ae1-0.network.virginmedia.net [62.254.42.210]
7 47 ms 23 ms 21 ms tcl5-ic-2-ae0-0.network.virginmedia.net [212.250.15.210]
8 23 ms 21 ms 25 ms 212.58.239.249
9 * * * Request timed out.
10 * * * Request timed out.
11 28 ms 23 ms 26 ms ae0.er02.telhc.bbc.co.uk [132.185.254.105]
12 23 ms 26 ms 25 ms 132.185.255.148
13 25 ms 21 ms 20 ms 212.58.244.22

Trace complete.

Tracing route to google.co.uk [216.58.212.195]
over a maximum of 30 hops:

1 4 ms 1 ms 1 ms 192.168.0.1
2 13 ms 10 ms 13 ms 10.86.112.1
3 17 ms 8 ms 8 ms croy-core-2a-xe-112-0.network.virginmedia.net [81.96.226.29]
4 * * * Request timed out.
5 12 ms 13 ms 11 ms tele-ic-7-ae2-0.network.virginmedia.net [62.253.175.34]
6 19 ms 19 ms 15 ms 74.125.52.226
7 19 ms 18 ms 18 ms 72.14.237.253
8 18 ms 23 ms 18 ms 72.14.232.141
9 26 ms 28 ms 28 ms 216.239.51.102
10 26 ms 28 ms 28 ms 209.85.251.24
11 29 ms 28 ms 28 ms 108.170.241.193
12 30 ms 28 ms 28 ms 216.239.42.173
13 27 ms 26 ms 28 ms ams16s21-in-f195.1e100.net [216.58.212.195]

Trace complete.

 

Hope this helps.

0 Kudos
Reply
  • 27
  • 2
  • 7
wyndstryke
On our wavelength
316 Views
Message 2 of 11
Flag for a moderator

Re: Summit aint reet :/

 

It was at the first New York aorta router that I was getting problems ... try a ping -t 84.116.140.170 to see if you have any dropped packets (control-C to stop pinging and get a summary).  I was getting 10% dropped packets to that router.

8 88 ms 88 ms 93 ms us-nyc01b-rd2-ae9-0.aorta.net [84.116.140.170]

The 'request timed out' at the later stages only means that they have ICMP responses turned off on those servers.

 

0 Kudos
Reply
  • 3
  • 0
  • 0
velve
Joining in
310 Views
Message 3 of 11
Flag for a moderator

Re: Summit aint reet :/

Nope, looks fine from here

Ping statistics for 84.116.140.170:
Packets: Sent = 26, Received = 26, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 84ms, Maximum = 108ms, Average = 87ms
0 Kudos
Reply
  • 6.29K
  • 169
  • 422
Forum Team
Forum Team
264 Views
Message 4 of 11
Flag for a moderator

Re: Summit aint reet :/

Hi there velve,

 

Really sorry to hear about the connection issue experienced.

 

I've located your account and there does appear to be a high demand for our service in your area under the fault ticket reference of F004784108 with a review set for 26/04/17.

 

I have passed this information on to another team so that they can monitor the fault in conjunction with your account.

 

I am sincerely sorry for any inconvenience caused.

 

Many thanks,

 

Nat_J

 

 


Who's who? Find out more about our community members. Good folk to know


0 Kudos
Reply
  • 42
  • 0
  • 3
Nejones1981
Tuning in
258 Views
Message 5 of 11
Flag for a moderator

Re: Summit aint reet :/

Review 5  months away haha, what a joke of a service. 


Nat_J wrote:

Hi there velve,

 

Really sorry to hear about the connection issue experienced.

 

I've located your account and there does appear to be a high demand for our service in your area under the fault ticket reference of F004784108 with a review set for 26/04/17.

 

I have passed this information on to another team so that they can monitor the fault in conjunction with your account.

 

I am sincerely sorry for any inconvenience caused.

 

Many thanks,

 

Nat_J

 

 


 

0 Kudos
Reply
  • 13.78K
  • 732
  • 4.79K
Superuser
Superuser
254 Views
Message 6 of 11
Flag for a moderator

Re: Summit aint reet :/

Let's deal with some misconceptions here.

Here's a tracert done to lotro.com using tcp packets instead of ICMP

1       5 ms    4 ms    4 ms    192.168.0.1
2       18 ms   17 ms   19 ms   94.173.103.1    [cpc35-sutt4-2-0-gw.19-1.cable.virginm.net]
3       14 ms   12 ms   18 ms   80.1.68.162     [perr-core-2b-ae14-703.network.virginmedia.net]
4       *       *       *       Request timed out.
5       *       *       *       Request timed out.
6       *       *       *       Request timed out.
7       18 ms   14 ms   27 ms   62.254.42.218   [nrth-ic-1-ae1-0.network.virginmedia.net]
8       17 ms   15 ms   21 ms   62.254.42.162   [m674-mp2.cvx1-b.lis.dial.ntli.net]
9       *       *       *       Request timed out.
10      89 ms   83 ms   85 ms   84.116.140.174
11      86 ms   88 ms   90 ms   84.116.135.114  [us-nyc01b-ri2-et-4-1-0-0.aorta.net]
12      86 ms   88 ms   90 ms   63.235.40.165   [nyc2-brdr-01.inet.qwest.net]
13      86 ms   87 ms   89 ms   205.171.17.2    [ewr-cntr-11.inet.qwest.net]
14      92 ms   88 ms   91 ms   206.103.215.50
15      88 ms   87 ms   91 ms   63.236.3.130
16      *       *       *       Request timed out.
17      *       *       *       Request timed out.
18      Destination Reached in 89 ms. Connection established to 198.252.160.58
Trace Complete.

Note that some midway hops will time out because of various reasons.  So we start with the critical issue.  Does it get to it's destination.  The answer is yes.

Here's the same trace over ICMP

C:\Users\timdu>tracert lotro.com

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

  1     2 ms     1 ms     5 ms  192.168.0.1
  2    13 ms    17 ms    18 ms  cpc35-sutt4-2-0-gw.19-1.cable.virginm.net [94.173.103.1]
  3    11 ms    12 ms     9 ms  perr-core-2b-ae14-703.network.virginmedia.net [80.1.68.162]
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7    17 ms    14 ms    14 ms  nrth-ic-1-ae1-0.network.virginmedia.net [62.254.42.218]
  8    20 ms    22 ms    12 ms  m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
  9     *        *        *     Request timed out.
 10    88 ms    84 ms    93 ms  84.116.140.174
 11    85 ms    86 ms    91 ms  us-nyc01b-ri2-et-4-1-0-0.aorta.net [84.116.135.114]
 12    85 ms    86 ms    89 ms  nyc2-brdr-01.inet.qwest.net [63.235.40.165]
 13    88 ms    86 ms    83 ms  ewr-cntr-11.inet.qwest.net [205.171.17.2]
 14    90 ms    87 ms    90 ms  206.103.215.50
 15    86 ms    86 ms    88 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.

This time the trace doesn't appear to reach the target.  But it's a red herring.  Some server administrators will block ICMP responses.  The way tracert works means that when these are blocked, it doesn't realise it's reached the server and keeps on increasing the hop count until it reaches the hop limit.  The packet doesn't actually go any further then the server in question mind you.  The hop count just represents the maximum number of hops a packet can traverse in order to get to it's destination.

The function of the routers on midway hops is to route packets.  For this reason some don't respond to ICMP pings at all and some will defer or even drop pings.  So apparent packet loss at one router may not actually be seen further up the path.

So @wyndstryke While you may get 10% packet loss at 84.116.140.170 the next question would be is that packet loss repeated further down the chain?

Ravenstar68

Edit BTW - I get no packet loss at that hop either

Ping statistics for 84.116.135.114:
    Packets: Sent = 413, Received = 413, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 109ms, Maximum = 172ms, Average = 114ms

 

________________________________________


Only use Helpful answer if your problems been solved.

  • 27
  • 2
  • 7
wyndstryke
On our wavelength
243 Views
Message 7 of 11
Flag for a moderator

Re: Summit aint reet :/

>So @wyndstryke While you may get 10% packet loss at 84.116.140.170 the next question
>would be is that packet loss repeated further down the chain?

At the time (Sunday before last) yes, that node was the earliest node which was showing partial packet loss, all nodes after that point were problematic.

When service improved on the monday the packet loss to aorta also disappeared (no packets lost in over 1000 pings), as per this reply:

http://community.virginmedia.com/t5/Gaming-Support/Lag-disconnects-to-ESO-US-server/m-p/3257082#M260...

 

... so what's your conclusion?  And what were the misconceptions, because I'm not quite following your meaning there, could you elaborate?

 

0 Kudos
Reply
  • 13.78K
  • 732
  • 4.79K
Superuser
Superuser
201 Views
Message 8 of 11
Flag for a moderator

Re: Summit aint reet :/

Let's deal with some of the misconceptions from various posts in this thread.

1. That the game servers are located at the IP address pointed to by lotro.com
     The game servers are likely to be hosted elsewhere.  In some cases there may be different servers for different regions.  For example Blizzard has servers in Europe, and America.  I wouldn't be surprised if Warner Brothers 

2. The OP was concerned that the hops responding on the tracerts indicated the issue was with Virgin.  
     While Virgin may have a separate issue in his area.  The fact that people are complaining from other places would suggest the issue may lie with LOTR itself or a peering partner along the way.

 

________________________________________


Only use Helpful answer if your problems been solved.

  • 13.78K
  • 732
  • 4.79K
Superuser
Superuser
195 Views
Message 9 of 11
Flag for a moderator

Re: Summit aint reet :/

It definitely helps to know which server you guys are trying to use.

________________________________________


Only use Helpful answer if your problems been solved.

0 Kudos
Reply
  • 27
  • 2
  • 7
wyndstryke
On our wavelength
183 Views
Message 10 of 11
Flag for a moderator

Re: Summit aint reet :/

>The OP was concerned that the hops responding on the tracerts indicated the
>issue was with Virgin.
> While Virgin may have a separate issue in his area. The fact that people are
>complaining from other places would suggest the issue may lie with LOTR itself
>or a peering partner along the way.

Yeah, that was my conclusion for my own problem (iffy connection to elder scrolls online's NA server). The IP I identified from my own issue and mentioned in this thread (84.116.140.170) is the first node after the landing point in NYC, pretty sure it's the first peer since 'aorta' does sound like a specialist peering network.

My own thread was this one:

http://community.virginmedia.com/t5/Gaming-Support/Lag-disconnects-to-ESO-US-server/m-p/3256314

When I saw this thread complaining about connectivity to NA servers for a different game at the same time and going through the same IP which was giving me issues, it caught my attention.  While peers aren't under Virgin's control, the Virgin NOC will be talking to all it's peers pretty much 24/7 so can let them know if there's an issue, hence (in my opinion) why it's worthwhile posting peering issues here as well as direct VM issues.

0 Kudos
Reply