Lag increase to GLS.lotro.com

Question

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

derrickw · Answer

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?

connect_lv · Answer

I don't notice it as much because its not that apparent .&nbsp; Its a wired connection.&nbsp; Thats all we ever use.&nbsp; 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:&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp; 1 ms&nbsp;&nbsp;&nbsp; &lt;1 ms&nbsp;&nbsp;&nbsp;&nbsp; 1 ms&nbsp; 10.0.1.1&nbsp; 2&nbsp;&nbsp;&nbsp; 10 ms&nbsp;&nbsp;&nbsp;&nbsp; 8 ms&nbsp;&nbsp;&nbsp; 10 ms&nbsp; 10.104.0.1&nbsp; 3&nbsp;&nbsp;&nbsp; 10 ms&nbsp;&nbsp;&nbsp;&nbsp; 8 ms&nbsp;&nbsp;&nbsp; 33 ms&nbsp; 100.127.0.0&nbsp; 4&nbsp;&nbsp;&nbsp;&nbsp; 9 ms&nbsp;&nbsp;&nbsp; 10 ms&nbsp;&nbsp;&nbsp; 45 ms&nbsp; 24-234-6-68.ptp.lvcm.net [24.234.6.68]&nbsp; 5&nbsp;&nbsp;&nbsp; 10 ms&nbsp;&nbsp;&nbsp;&nbsp; 8 ms&nbsp;&nbsp;&nbsp; 11 ms&nbsp; ae54.bar2.LasVegas1.Level3.net [205.129.18.109]&nbsp; 6&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp; Request timed out.&nbsp; 7&nbsp;&nbsp;&nbsp; 23 ms&nbsp;&nbsp;&nbsp; 23 ms&nbsp;&nbsp;&nbsp; 23 ms&nbsp; los-brdr-01.inet.qwest.net [63.146.27.33]&nbsp; 8&nbsp;&nbsp;&nbsp; 91 ms&nbsp;&nbsp;&nbsp; 92 ms&nbsp;&nbsp; 109 ms&nbsp; ewr-cntr-11.inet.qwest.net [205.171.17.2]&nbsp; 9&nbsp;&nbsp;&nbsp; 94 ms&nbsp;&nbsp;&nbsp; 92 ms&nbsp;&nbsp;&nbsp; 92 ms&nbsp; 206.103.215.50&nbsp;10&nbsp;&nbsp;&nbsp; 91 ms&nbsp;&nbsp;&nbsp; 92 ms&nbsp;&nbsp;&nbsp; 91 ms&nbsp; 63.236.3.130&nbsp;11&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp; Request timed out.&nbsp;12&nbsp;&nbsp;&nbsp; 93 ms&nbsp;&nbsp;&nbsp; 90 ms&nbsp;&nbsp;&nbsp; 96 ms&nbsp; 198.252.160.30&nbsp;13&nbsp;&nbsp;&nbsp; 93 ms&nbsp;&nbsp;&nbsp; 92 ms&nbsp;&nbsp;&nbsp; 93 ms&nbsp; 198.252.160.30Trace complete.Tracing route to netflix.com [52.89.148.95]over a maximum of 30 hops:&nbsp; 1&nbsp;&nbsp;&nbsp; &lt;1 ms&nbsp;&nbsp;&nbsp; &lt;1 ms&nbsp;&nbsp;&nbsp;&nbsp; 1 ms&nbsp; 10.0.1.1&nbsp; 2&nbsp;&nbsp;&nbsp;&nbsp; 8 ms&nbsp;&nbsp;&nbsp; 15 ms&nbsp;&nbsp;&nbsp;&nbsp; 8 ms&nbsp; 10.104.0.1&nbsp; 3&nbsp;&nbsp;&nbsp; 10 ms&nbsp;&nbsp;&nbsp; 11 ms&nbsp;&nbsp;&nbsp; 11 ms&nbsp; 100.127.0.0&nbsp; 4&nbsp;&nbsp;&nbsp; 11 ms&nbsp;&nbsp;&nbsp; 10 ms&nbsp;&nbsp;&nbsp; 10 ms&nbsp; 24-234-6-68.ptp.lvcm.net [24.234.6.68]&nbsp; 5&nbsp;&nbsp;&nbsp; 30 ms&nbsp;&nbsp;&nbsp; 30 ms&nbsp;&nbsp;&nbsp; 31 ms&nbsp; sanjbprj02-ae0.0.rd.sj.cox.net [68.1.5.186]&nbsp; 6&nbsp;&nbsp;&nbsp; 24 ms&nbsp;&nbsp;&nbsp; 22 ms&nbsp;&nbsp;&nbsp; 24 ms&nbsp; ip70-167-151-25.at.at.cox.net [70.167.151.25]&nbsp; 7&nbsp;&nbsp;&nbsp; 37 ms&nbsp;&nbsp;&nbsp; 43 ms&nbsp;&nbsp;&nbsp; 40 ms&nbsp; 54.240.242.70&nbsp; 8&nbsp;&nbsp;&nbsp; 23 ms&nbsp;&nbsp;&nbsp; 24 ms&nbsp;&nbsp;&nbsp; 23 ms&nbsp; 54.240.242.79&nbsp; 9&nbsp;&nbsp;&nbsp; 50 ms&nbsp;&nbsp;&nbsp; 49 ms&nbsp;&nbsp;&nbsp; 50 ms&nbsp; 54.239.42.6&nbsp;10&nbsp;&nbsp;&nbsp; 55 ms&nbsp;&nbsp;&nbsp; 46 ms&nbsp;&nbsp;&nbsp; 45 ms&nbsp; 52.93.12.44&nbsp;11&nbsp;&nbsp;&nbsp; 41 ms&nbsp;&nbsp;&nbsp; 44 ms&nbsp;&nbsp;&nbsp; 44 ms&nbsp; 52.93.12.37&nbsp;12&nbsp;&nbsp;&nbsp; 71 ms&nbsp;&nbsp;&nbsp; 65 ms&nbsp;&nbsp;&nbsp; 83 ms&nbsp; 52.93.12.144&nbsp;13&nbsp;&nbsp;&nbsp; 46 ms&nbsp;&nbsp;&nbsp; 45 ms&nbsp;&nbsp;&nbsp; 42 ms&nbsp; 52.93.12.173&nbsp;14&nbsp;&nbsp;&nbsp; 57 ms&nbsp;&nbsp;&nbsp; 50 ms&nbsp;&nbsp;&nbsp; 50 ms&nbsp; 52.93.15.219&nbsp;15&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp; Request timed out.&nbsp;16&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp; Request timed out.&nbsp;17&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp; Request timed out.&nbsp;18&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp; Request timed out.&nbsp;19&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp; Request timed out.&nbsp;20&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp; Request timed out.&nbsp;21&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp; Request timed out.&nbsp;22&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp; Request timed out.&nbsp;23&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp; Request timed out.&nbsp;24&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp; Request timed out.&nbsp;25&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp; Request timed out.&nbsp;26&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp; Request timed out.&nbsp;27&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp; Request timed out.&nbsp;28&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp; Request timed out.&nbsp;29&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp; Request timed out.&nbsp;30&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp; Request timed out.Trace complete.

derrickw · Answer

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.

Forum Discussion

Lag increase to GLS.lotro.com

3 Replies

Related Content

Bill Increases

Cox Increases Fiber-Powered Internet Speeds for Most Customers

Price increases

Discord stream Lag high ping

Packet Loss & Lags - Please Help!

Recent Discussions

Welcome to the Archives

Gigablast

Beeping Noise

mic/status led on contour 2 remote

Internet connectivity frustrations