connect_lv's profile

New Contributor II

 • 

27 Messages

Closed

Lag increase to GLS.lotro.com

The previous 7  or so days my connection was between 72 and 88 MS to Lotro.com.  I guess you went back to the bad routing again. back up to 109 + using this route.  Gaming is bad if this is the speed. with an increase of packet drops.  I live in Las Vegas NV. 

Valued Contributor

 • 

1.2K Messages

Do you experience these connection issues outside of when you're gaming? Do you use a wired or wireless connection? Can you provide some trace route tests to at least 2 different sites so we can compare them?

New Contributor II

 • 

27 Messages

I don't notice it as much because its not that apparent .  Its a wired connection.  Thats all we ever use.  Sorry I didn't get a trace route from the times with good connections.

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

  1     1 ms    <1 ms     1 ms  10.0.1.1
  2    10 ms     8 ms    10 ms  10.104.0.1
  3    10 ms     8 ms    33 ms  100.127.0.0
  4     9 ms    10 ms    45 ms  24-234-6-68.ptp.lvcm.net [24.234.6.68]
  5    10 ms     8 ms    11 ms  ae54.bar2.LasVegas1.Level3.net [205.129.18.109]
  6     *        *        *     Request timed out.
  7    23 ms    23 ms    23 ms  los-brdr-01.inet.qwest.net [63.146.27.33]
  8    91 ms    92 ms   109 ms  ewr-cntr-11.inet.qwest.net [205.171.17.2]
  9    94 ms    92 ms    92 ms  206.103.215.50
 10    91 ms    92 ms    91 ms  63.236.3.130
 11     *        *        *     Request timed out.
 12    93 ms    90 ms    96 ms  198.252.160.30
 13    93 ms    92 ms    93 ms  198.252.160.30

Trace complete.

Tracing route to netflix.com [52.89.148.95]
over a maximum of 30 hops:

  1    <1 ms    <1 ms     1 ms  10.0.1.1
  2     8 ms    15 ms     8 ms  10.104.0.1
  3    10 ms    11 ms    11 ms  100.127.0.0
  4    11 ms    10 ms    10 ms  24-234-6-68.ptp.lvcm.net [24.234.6.68]
  5    30 ms    30 ms    31 ms  sanjbprj02-ae0.0.rd.sj.cox.net [68.1.5.186]
  6    24 ms    22 ms    24 ms  ip70-167-151-25.at.at.cox.net [70.167.151.25]
  7    37 ms    43 ms    40 ms  54.240.242.70
  8    23 ms    24 ms    23 ms  54.240.242.79
  9    50 ms    49 ms    50 ms  54.239.42.6
 10    55 ms    46 ms    45 ms  52.93.12.44
 11    41 ms    44 ms    44 ms  52.93.12.37
 12    71 ms    65 ms    83 ms  52.93.12.144
 13    46 ms    45 ms    42 ms  52.93.12.173
 14    57 ms    50 ms    50 ms  52.93.15.219
 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.

Valued Contributor

 • 

1.2K Messages

The trace routes you provided shows the latency taking place outside of our network. Using a wired connection will allow you to have the fastest speed, the timeouts that we are seeing are happening on the other side of the trace once the packets have left our network. The return times are low with the trace route results as well.