Quantcast
Channel: Basic Internet Connectivity And Modem Help topics
Viewing all articles
Browse latest Browse all 12065

Heavy lag and ping spikes - packet loss to web services (Riot games and Twitch.tv)

$
0
0

Hello everyone, I wanted to collect some information to see if I am not the only one experiencing these issues. I play the game League of Legends and have been experiencing these issues for the last several months at the most random times. Basically when I am in game, my ping will either spike to 800-1000ms, or the ping will remain the same, but the actions will be delayed for a few moments while everything is frozen on screen (server side commands are at a standpoint).

 

I have run many tests since these issues were presented, to see where I was at with my connection, and searched online for solutions. I have found out that many were outraged by the same issues that I am experiencing, and have complained to Reddit's subreddit board /r/leagueoflegends to the League of Legends forums themselves, as well as Contacting Comcast's NOC to even get answers. 

 

While they become temporary fixes, it only seems that Comcast has either rerouted connections around these known nodes, or Riot has done it themselves. But it can not just be Riot, as this issue persists when I try to use web services from the West Coast (such as Twitch.tv). So why is it that these issues are never actually resolved and fixed?

 

I understand that it is recommended to reboot my modem, send a new signal, and these other little fixes for my apparent "slow speed" as called from Comcast support, when they don't understand that I have a packet loss issue, does not directly relate to download/upload speed. 

 

Here are the tests that I ran provided from Riot Games

 

race complete.

192.64.168.0/24 Game Servers (PDX):

Tracing route to 192.64.168.1 over a maximum of 20 hops

1 <1 ms <1 ms <1 ms 10.0.0.1
2 28 ms 33 ms 26 ms *.hsd1.pa.comcast.net [71.224.96.1]
3 9 ms 9 ms 9 ms xe-11-2-0-32767-sur01.newhanover.pa.panjde.comcast.net [68.85.153.69]
4 39 ms 52 ms 31 ms 69.139.192.193
5 13 ms 13 ms 15 ms pos-2-3-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.94.233]
6 37 ms 35 ms 35 ms he-0-6-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.88.154]
7 54 ms 55 ms 59 ms he-1-10-0-0-cr01.denver.co.ibone.comcast.net [68.86.86.182]
8 83 ms 83 ms 83 ms he-0-10-0-0-cr01.seattle.wa.ibone.comcast.net [68.86.88.70]
9 80 ms 81 ms 81 ms be-14-pe03.seattle.wa.ibone.comcast.net [68.86.83.2]
10 103 ms 94 ms 98 ms 23-30-206-34-static.hfc.comcastbusiness.net [23.30.206.34]
11 85 ms 83 ms 84 ms Riot-Games-FDCP-10000M-1.demarc.spectrumnet.us [208.76.153.130]
12 * * * Request timed out.
13 * * * Request timed out.
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.

Trace complete.

192.64.169.0/24 Game Servers (PDX):

Tracing route to 192.64.169.1 over a maximum of 20 hops

1 1 ms <1 ms <1 ms 10.0.0.1
2 29 ms 28 ms 29 ms *.hsd1.pa.comcast.net [71.224.96.1]
3 9 ms 8 ms 10 ms xe-11-2-0-32767-sur01.newhanover.pa.panjde.comcast.net [68.85.153.69]
4 9 ms 10 ms 9 ms 69.139.192.193
5 14 ms 16 ms 15 ms pos-3-13-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.95.165]
6 36 ms 35 ms 35 ms he-0-1-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.88.134]
7 74 ms 70 ms 57 ms he-1-11-0-0-cr01.denver.co.ibone.comcast.net [68.86.86.186]
8 83 ms 83 ms 83 ms he-0-15-0-0-cr01.seattle.wa.ibone.comcast.net [68.86.86.214]
9 79 ms 81 ms 80 ms be-13-pe03.seattle.wa.ibone.comcast.net [68.86.84.110]
10 80 ms 80 ms 81 ms 23-30-206-34-static.hfc.comcastbusiness.net [23.30.206.34]
11 84 ms 113 ms 83 ms Riot-Games-FDCP-10000M-1.demarc.spectrumnet.us [208.76.153.130]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * General failure.

 

Essentially this is what I should be seeing, but most times, the ping spikes will average from 400 - 800 off each Comcast node.

 

192.64.168.0/24 Game Servers (PDX):

Tracing route to 192.64.168.1 over a maximum of 20 hops

1 <1 ms <1 ms <1 ms

10.0.0.1 2 513 ms 267 ms 61 ms *.hsd1.pa.comcast.net [71.224.96.1]

3 22 ms 10 ms 9 ms xe-11-2-0-32767-sur01.newhanover.pa.panjde.comcast.net [68.85.153.69]

4 374 ms 164 ms 71 ms 69.139.192.193

5 361 ms 371 ms 371 ms pos-3-12-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.95.161]

6 110 ms 67 ms 35 ms he-0-6-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.88.154]

7 545 ms 464 ms 291 ms he-1-10-0-0-cr01.denver.co.ibone.comcast.net [68.86.86.182]

 

Basically one example of the high spikes that I have been receiving. Yet again, every time I have contacted Comcast to "fix the issue", nothing was ever actually accomplished. From the general "repair" services, to having technicians look at the lines in my home, and provided tickets that just told me general information and nothing technical in any way.

 

I am severly disapointed by the lack of service I have received, and can not stand for these issues when they persist for months, and nothing is done about it. Please Comcast, look into these issues and actually fix them. I know I am not the only one, and this issue needs to be addressed for millions of users that use the same services as myself. 

 

Fyi, even with a 28mbps down service, I have to rebuffer a 2mbps 1080p stream from Twitch every five minutes.


Viewing all articles
Browse latest Browse all 12065

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>