Avaln (EUNE)
: Trying to reconnect in any part of the game bug?
Any of you run a tracert to prod.euw1.lol.riotgames.com and seen where the issue is?
: Keep getting disconnected
Any of you run a tracert to prod.euw1.lol.riotgames.com and seen where the issue is?
: having a lot of trouble
Are all of you still experiencing issues?
Rioter Comments
: I am with telkom yes, but how exactly can this be fixed?
Telkom has to change the route that it's being sent over, I'm going to try and use their live chat service in the morning, as otherwise it will probably sit in an inbox for a week
: 2 * * * Request timed out. 3 20 ms 18 ms 19 ms 105-187-235-41.telkomsa.net [105.187.235.41] 4 22 ms 18 ms 18 ms 105-187-235-42.telkomsa.net [105.187.235.42] 5 23 ms 19 ms 18 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57] 6 18 ms 19 ms 19 ms wbs-os-cer-1-wan.osnet.co.za [196.25.50.217] 7 236 ms * 236 ms 10.189.30.10 8 238 ms 235 ms 238 ms pr02.fra02.riotdirect.net [80.81.193.162] 9 * * * Request timed out. 10 * * * Request timed out. 11 244 ms 310 ms 240 ms 104.160.141.103 12 247 ms 257 ms 248 ms 104.160.141.107 13 244 ms 243 ms 240 ms 185.40.64.65
Exact same points hop 8 would be: 104.160.153.78 and hop 9 would be: ae-30.br02.ams02.riotdirect.net [104.160.159.54] Those 2 seem to timeout the most, though hops 11 and 12 often have some non-responses and rarely hop 8. Riot believes the issue is at 10.189.30.10 (Hop 7) when Telkom hands over it's traffic to wherever it's landing in/near Europe. If it is Telkom, then we're kinda stuck with this for a while, as we know how fast they work
: You're not alone man, i'm from SA too (usually get 192 ms and is completely playable) but up until recently it would state 203ms but feel like 300ms. The spikes have gotten much worse this past day. It is actually becoming unplayable after the recent patch. Not only that, the client also lags a bit more than before. {{sticker:sg-shisa}}
I've been in contact with their support team. It seems to be related to the route Telkom is taking to send the data to Riot, though they're saying it's Telkom's baby, I'm trying to prove otherwise and/or find the actual point of breakdown. Are you both with Telkom? And could you possibly run a tracert and see where there are * or disconnect after the 2nd hop. command prompt: tracert prod.euw1.lol.riotgames.com
: 1 1 ms <1 ms <1 ms 10.50.30.1 2 2 ms 1 ms 1 ms 92-111-106-81.static.v4.ziggozakelijk.nl [92.111.106.81] 3 15 ms 13 ms 13 ms 10.160.45.1 4 15 ms 13 ms 17 ms 212.142.52.33 5 14 ms 17 ms 13 ms asd-rc0001-cr101-be110-2.core.as33915.net [213.51.7.82] 6 * * * Request timed out. 7 20 ms 20 ms 18 ms nl-ams04a-ri3-ae-9-0.aorta.net [84.116.130.242] 8 * * * Request timed out. 9 * * * Request timed out. 10 15 ms 18 ms 15 ms 104.160.141.103 11 14 ms 14 ms 14 ms 104.160.141.107 12 25 ms 16 ms 14 ms 185.40.64.65 i think this shows it better the other one might be a little confusung
So you're also timing out trying to get to 104.160.141.103 and/or 104.160.141.107 {{champion:161}}
: Everyone run the following in command prompt and then share the results, it should help them find the issue. tracert prod.euw1.lol.riotgames.com
My results are: 3 34 ms 32 ms 34 ms 105-187-235-41.telkomsa.net [105.187.235.41] 4 39 ms 37 ms 38 ms 105-187-235-42.telkomsa.net [105.187.235.42] 5 36 ms 37 ms 41 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57] 6 33 ms 40 ms 34 ms wbs-os-cer-1-wan.osnet.co.za [196.25.50.217] 7 202 ms 193 ms 203 ms 10.189.30.10 8 * * 202 ms pr02.fra02.riotdirect.net [80.81.193.162] 9 * * * Request timed out. 10 * * * Request timed out. 11 209 ms 208 ms 209 ms 104.160.141.103 12 208 ms 207 ms 207 ms 104.160.141.107 13 208 ms * 208 ms 185.40.64.65 Which shows an issue going from hops 8 to 11
: having a lot of trouble
Everyone run the following in command prompt and then share the results, it should help them find the issue. tracert prod.euw1.lol.riotgames.com
Jaiyo (EUW)
: > [{quoted}](name=SHADOW201314,realm=EUW,application-id=eZuvYsEr,discussion-id=T6L5tZtK,comment-id=,timestamp=2019-10-07T18:08:37.791+0000) > > Responses from the server seem to be routing badly and possibly out of order, leading to the game being visually laggy, despite ping and inputs being normal. Means game is playable to a degree, but not ideal as you're often working off what you expect the server response and output to be. > > I would presume it's a problem with Riot's ISP and traffic through the south eastern portion of EUW. Would this cause the entire client to be laggy as well? I had no issue playing yesterday and today the client takes an extra 15 secs to open up and every game takes way longer to load into and crashes 9/10 times. I'm based in south England, so north-west EUW really.
Yup, logging in connecting etc can take a while. They've had this issue before (Maybe about a year ago) with their service provider and bad DNS records, and apologised and sorted it out, but looks like it's back. And it's been 5 days, this is not a 5 day problem to fix.
: having a lot of trouble
I made a post with regards to this earlier. It seems to be an issue with bad routing between Riot's service provider and certain areas. Though the last few hours before the server maintenance it did seem to improve slightly.
Rioter Comments
Civara (EUW)
: > [{quoted}](name=SHADOW201314,realm=EUW,application-id=ETj6EdvQ,discussion-id=MsYQFxZl,comment-id=0019,timestamp=2019-09-19T22:21:44.681+0000) > > Hi all, this bug is caused by details of your last played/spectated game being in the LeagueClientSettings.yaml in the Config folder and marked as In Progress. There are 3 solutions: > > 1 -> The Reconnect/Quit button briefly shows up as the client loads, if you can click Quit before it disappears, it will clear the spectator data and fix the issue. > > 2 -> Alternatively edit the file to remove the references (a bit more technical and I would rather recommend option 3) > > 3 -> Delete the LeagueClientSettings.yaml file and the game will recreate it on launch (May have to readjust any client settings you've altered (In game settings should remain the same) Apperantly I'm not fast enough for option one, but option three isn't working for me either. It just updates for a little bit but once I'm logged in I get the same error.
Hmm then it might not be the old spectator bug, and actually be server side, if it is then only Riot can clear that :-(
PooF (EUW)
: Same thing over here. Stuck for about 30 mins.
: stuck over an hour {{sticker:sg-janna}}
Ratatouka (EUW)
: yo wtf is this
There was probably some data corruption in your LeagueClientSettings.yaml file in the Config folder. You could have just deleted this and it would have been recreated (You would have lost some client settings changes you may have made, but not in game settings).
: Spectator bug
Hi this bug is caused by details of your last spectated game being in the LeagueClientSettings.yaml in the Config folder and marked as In Progress. There are 3 solutions: 1 -> The Reconnect/Quit button briefly shows up as the client loads, if you can click Quit before it disappears, it will clear the spectator data and fix the issue. 2 -> Alternatively edit the file to remove the references (a bit more technical and I would rather recommend option 3) 3 -> Delete the LeagueClientSettings.yaml file and the game will recreate it on launch (May have to readjust any client settings you've altered (In game settings should remain the same)

SHADOW201314

Level 190 (EUW)
Lifetime Upvotes
Create a Discussion