Community Forum

Traceroute issue to Riot Servers

Highlighted
Frequent Visitor

Traceroute issue to Riot Servers

Not sure what's up with the xfinity network but I've been having major ping issues for a month when I try to play League of Legends.  Looking at my traceroute to the Riot servers (104.160.131.1)  I'm getting substantial packet loss (85%) from hostname lag-39.ear2.Seattle1.Level3.net (4.68.37.129).  If there's anyone that could look into this I'd appreciate it!

Highlighted
Expert

Re: Traceroute issue to Riot Servers

Please post that entire trace output.



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Highlighted
Frequent Visitor

Re: Traceroute issue to Riot Servers

1 <1 ms <1 ms <1 ms My Router
2 14 ms 13 ms 12 ms 96.120.103.193
3 18 ms 14 ms 11 ms po-305-1221-rur01.ferndale.wa.seattle.comcast.net [162.151.209.13]
4 25 ms 12 ms 14 ms po-2-rur02.ferndale.wa.seattle.comcast.net [69.139.160.254]
5 26 ms 16 ms 26 ms be-41-ar01.seattle.wa.seattle.comcast.net [69.139.164.33]
6 * * * Request timed out.
7 41 ms 39 ms 46 ms ae-2-3601.edge7.LosAngeles1.Level3.net [4.69.219.45]
8 40 ms 36 ms 38 ms RIOT-GAMES.edge7.LosAngeles1.Level3.net [205.129.3.98]
9 71 ms 69 ms 70 ms 104.160.151.139
10 70 ms 73 ms 74 ms 104.160.159.100
11 69 ms 71 ms 68 ms 104.160.159.142
12 75 ms 69 ms 83 ms ae2.br01.chi01.riotdirect.net [104.160.143.93]
13 78 ms 72 ms 70 ms 104.160.131.1

Trace complete.

Highlighted
Frequent Visitor

Re: Traceroute issue to Riot Servers

 lag-39.ear2.Seattle1.Level3.net (4.68.37.129) <---that is normally where hop 6 is with 85% PL.

Highlighted
Expert

Re: Traceroute issue to Riot Servers

That router is not listed there.



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Highlighted
Frequent Visitor

Re: Traceroute issue to Riot Servers

1 <1 ms <1 ms <1 ms My Router

2 24 ms 14 ms 11 ms 96.120.103.193

3 10 ms 12 ms 10 ms po-305-1221-rur01.ferndale.wa.seattle.comcast.net [162.151.209.13]

4 12 ms 10 ms 12 ms po-2-rur02.ferndale.wa.seattle.comcast.net [69.139.160.254]

5 14 ms 13 ms 14 ms be-41-ar01.seattle.wa.seattle.comcast.net [69.139.164.33]

6 15 ms 14 ms 13 ms lag-39.ear2.Seattle1.Level3.net [4.68.37.129]

7 42 ms 45 ms 39 ms ae-2-3601.edge7.LosAngeles1.Level3.net [4.69.219.45]

8 57 ms 38 ms 38 ms RIOT-GAMES.edge7.LosAngeles1.Level3.net [205.129.3.98]

9 72 ms 68 ms 67 ms 104.160.151.139

10 79 ms 69 ms 67 ms 104.160.159.100

11 88 ms 70 ms 75 ms 104.160.159.142

12 73 ms 69 ms 72 ms ae2.br01.chi01.riotdirect.net [104.160.143.93]

13 69 ms 68 ms 72 ms 104.160.131.1

 

It is now.

Highlighted
Frequent Visitor

Re: Traceroute issue to Riot Servers

My ping should be 59 to 61 not 70+.

Highlighted
Frequent Visitor

Re: Traceroute issue to Riot Servers

1 <1 ms <1 ms <1 ms 192.168.1.1

2 12 ms 10 ms 10 ms 96.120.103.193

3 19 ms 10 ms 11 ms po-305-1221-rur01.ferndale.wa.seattle.comcast.net [162.151.209.13]

4 10 ms 9 ms 10 ms po-2-rur02.ferndale.wa.seattle.comcast.net [69.139.160.254]

5 16 ms 15 ms 15 ms be-41-ar01.seattle.wa.seattle.comcast.net [69.139.164.33]

6 * * 21 ms lag-39.ear2.Seattle1.Level3.net [4.68.37.129]

7 41 ms 41 ms 49 ms ae-2-3601.edge7.LosAngeles1.Level3.net [4.69.219.45]

8 37 ms 37 ms 37 ms RIOT-GAMES.edge7.LosAngeles1.Level3.net [205.129.3.98]

9 86 ms 70 ms 91 ms 104.160.151.139

10 79 ms 68 ms 70 ms 104.160.159.100

11 71 ms 86 ms 67 ms 104.160.159.142

12 89 ms 68 ms 73 ms ae2.br01.chi01.riotdirect.net [104.160.143.93]

13 73 ms 73 ms 87 ms 104.160.131.1

 

Tried it again a minute later and hop 6 times out.