The Good, The Bad, and the League: 9/19 - 10/3

_Your semi-weekly dose of server problem-os, NA League news, and other! (Moved to Mondays for easier updates)_ We’re seeing some exciting Worlds matches, Clash testing is always fun, and 9.20 is right on the horizon! **Follow-Ups:** * **Mac voice still not working properly** Bug grouped with other Mac bugs **Ongoing** * **Transfer service goes down(9/21)** PS notifies the NOC that players are getting errors when attempting to transfer between Europe and Oceania (Not 100% failure rate, but not 0% either). A JIRA ticket is made to track the problem, and teams are assigning resources appropriately during the upcoming sprint. * **TFT Match History intermittent(9/26)** TFT match history goes live on all regions, and reports start to filter in over the next day that TFT matches aren’t always showing up in match history. A code fix is discovered, but Live Production does not deem it high enough of a problem to warrant a hotfix just for it. The fix is slated to roll out with patch 9.20. **Server Stuff: ** * **Automated Monitoring notices error increases(9/19, ~9 minutes)** Automated monitoring notices errors exceeding acceptable levels for logons. Before any need for investigation, the errors decrease back to acceptable levels. * **Match History fails to load after 9.19(9/25, ~58 minutes)** Platform opens after the 9.19 patch, but match history is failing to load. A micropatch rolls out shortly afterwards to update the server config for match history, fixing the problem. * **Issue with Pro View pass not giving item appropriately. (9/26, ~5 days)** A patch rolls out for pro view, and reports drift in that purchases are failing, but RP is still being charged. Pro view and team bundles are disabled while store and dev teams investigate. A fix is tested on PBE and then pushed to TR before rolling out to the remaining Riot realms. * **Automated Monitoring notices Reconnect Spikes. (9/29, ~90 minutes)** Automated monitoring notices game reconnects are spiking. Investigations from network teams identify a networking card issue on a specific server. Network engineers properly route traffic away from the failed network card, and a scheduled replacement task is created for the next time that server case is open for maintenance. **Game Stuff: ** * **TFT ranked disabled due to bugs(9/25, ~36 hours)** The NOC is informed by game teams that TFT ranked needs to be disabled. Live Production teams start triaging the associated issues, testing on both internal realms as a micropatch is prepared. After the bug fixes are verified, the micropatch goes out and ranked is turned back on. _Morgageddon_

Posts are displayed here in chronological (time, oldest first, newest last) order, like a regular web forum.

Were the match history failing to load and the mastery bug (where you get no mastery point or grade after a game) related? If it's the case, is there a chance for the player to get back the point/M token they missed because of that bug or are they lost forever?
> **Flemman \(EUW\) said:** Were the match history failing to load and the mastery bug (where you get no mastery point or grade after a game) related? If it's the case, is there a chance for the player to get back the point/M token they missed because of that bug or are they lost forever? It doesn't look like the two are related (according to the JIRA information available that I can see). I don't really know about the Mastery token/point though, so I can't give you an answer about it :(
not sure if this is the right place seems clash once again broke something with AT&T isp again ping is about 80-90ms higher than normal.
I have the same issue and it seems to be on Riots end because everyone with at&t isp are having problems with ping. I hope they fix whatever is wrong soon. {{sticker:zombie-nunu-bummed}}
Banning me for 14 days for inting in normals what is this kind of ban system you have just tell
> **ßàßà ñasty \(NA\) said:** I have the same issue and it seems to be on Riots end because everyone with at&t isp are having problems with ping. I hope they fix whatever is wrong soon. {{sticker:zombie-nunu-bummed}} A new peering connection between Riot Direct and AT&T finished earlier this morning. Does this change your ping at all?
This...is my issue. I have AT&T and my games have 130 ms that doesn't let up...#helpme
Dear Riot rep, i'm begging you with this one. There needs to be a review of the reception of the "quest" notification that was added a couple patches back to Corki when his Package becomes available. I have spoken to many other players of the champion online and never heard a single positive reaction to it. Obviously this change was intended to help people who have never played the champ before, but where is the precedent for this? - No other champ has instructions on how to use their kit show up on the middle of their screen in game. With there being no way to disable this, and the size and intrusiveness of the message, there REALLY NEEDS to be a review about how this change was received. I've been posting about it for months and no rioter has addressed this simple complaint.
Hi, it appears there's a new "Riot Client" on my system. How do I get rid of it and go back to using the League of Legend client only? Because I'm telling you, that thing looks AWFUL! And it's not like you guys make any other games, so I don't know why a client for the company when it only acts as a LoL launcher regardless...
> **mappellesToxique \(NA\) said:** This...is my issue. I have AT&T and my games have 130 ms that doesn't let up...#helpme Did the ping change after the peering changes earlier yesterday?
I don't know about anyone else, but this new client update is really irritating. Half the time it freezes upon booting up, and the other half it tries to install updates and freezes. The computer I'm using doesn't have any problems with anything else, but I'd like to know what other people think.
I see this message pop up and want to ask where to I have to submit a ticket to in regards to this? message: "We're having trouble speaking to some League servers. If this problem persists, please reach out to player support error code 1B". {{champion:59}}
> **Tol \(NA\) said:** I see this message pop up and want to ask where to I have to submit a ticket to in regards to this? message: "We're having trouble speaking to some League servers. If this problem persists, please reach out to player support error code 1B". {{champion:59}} Just through the support site! https://support.riotgames.com/hc/en-us
It went from persistent 130 lag to spikey lag (checked today in the practice tool, as well). Whatever that supposed fix was, it didn’t work.
I have a great skins and it will work 100% not even joking About Warring kingdoms skins Master Yi Yasuo Qiyana Darius Well if you care about it you can communicate to me. Instagram: almaraghi_550 Discord: almaraghi999
I have a great skins idea and its work 100% and I studying it for mouth and about Warring kingdoms skins Warring kingdom Master yi Warring kingdom Darius Warring kingdom Qiyana Warring kingdom Yasuo If you care about those skins you can massage me for more information and details 👍 Gmail: [email protected] Instagram: almaraghi_550 Discord: almaraghi999 (By the way those skins are awesome and most of league of legends player will love it so much ) .... thanks you
> **mappellesToxique \(NA\) said:** It went from persistent 130 lag to spikey lag (checked today in the practice tool, as well). Whatever that supposed fix was, it didn’t work. Can you run some trace routes (https://support.riotgames.com/hc/en-us/articles/201752674-Network-System-and-League-of-Legends-Logs#wq2) when you're seeing that ping and send the information in with a support ticket? It should help us figure out where the lag you're experiencing is coming from. I'll ping the NOC and see if we're still seeing issue with AT&T after the peering changes earlier this week.
So I tried that one, but I don't have a Mac. I used the tracert (https://support.riotgames.com/hc/en-us/articles/201752674-Network-System-and-League-of-Legends-Logs#obtaining-a-tracert--0-2) option, but in command prompt nothing happened after I hit Paste. I also tried to download the free tracert tool (http://winmtr.net/download-winmtr/), but that link didn't work for me.
Hi, I found this solution to fix the Mic issue with MacOS https://www.reddit.com/r/leagueoflegends/comments/ay9o4s/how_to_fix_voice_chat_in_macos_mojave/ and it works for me!

This is a fanmade archive of the leagcy League of Legends forums/boards. LeagueBoards.net isn't endorsed by Riot Games and doesn't reflect the views or opinions of Riot Games or anyone officially involved in producing or managing League of Legends. League of Legends and Riot Games are trademarks or registered trademarks of Riot Games, Inc. League of Legends © Riot Games, Inc.