As you may have noticed, there has been a bit of unexpected behavior during champion selection that has been causing some players to be unable to select a champion. Rest assured, we have our top men investigating the issue!
1:20 AM PDT: Servers are back online! Be sure to post in the forums if you have any problems, otherwise, enjoy your time in Runeterra!
9:53 PM PDT: We have identified the root cause and made the necessary changes to fix the problem. Unfortunately, this requires a full restart which will take about 4 hours. Time the servers are expected to be back online: 2:00 AM PDT
As fellow players, we understand the frustration of unexpected downtime and not only apologize for the inconvenience, but empathize with you. Rest assured, we are doing everything we can to make sure the issue is fully resolved.
Thank you for being so patient and understanding. See you all in 4 hours!
9:28 PM PDT: We have identified the problem but are still investigating root cause. Server status still Busy.
9:06 PM PDT: PvP.net going wonky again. Server Status Busy. Investigating.
9:00 PM PDT: Everything is still looking good.
8:15 PM PDT: Service back to normal. Button disabled.
7:57 PM PDT: Started raising the throttle, allowing more players back on slowly. Still possibility that complications could start again. Button still active.
7:45 PM PDT: Still investigating root cause. Queues still throttled as opening them back up would likely result in the same instability we saw the last few times we thought the issue was resolved. Sorry for the long delay guys.
7:05 PM PDT: Server complications seem to be normalizing. Server Status still Busy while we continue investigating.
6:55 PM PDT: Champion select is still suffering varying issues. There is a thorough investigation underway. Server status set to Busy while we diagnose.
6:35 PM PDT: PvP.net continues to experience issues. We are investigating.
5:40 PM PDT: We have reopened the launcher again.
5:32 PM PDT: We are investigating the continuing instability of PvP.net. The launcher is busy.
4:56 PM PDT: We've reopened the launcher. We are continuing to monitor and will be investigating the root cause of all of today's issues.
4:32 PM PDT: We've set the login queue to busy.
4:23 PM PDT: Champion Select is having intermittent issues.
4:07 PM PDT: The launcher is now online, although the login queue is enabled.
3:43 PM PDT: The launcher is set to busy while we continue to troubleshoot the re-emergence of PvP.net instability.
3:33 PM PDT: Compensation Mode has been re-enabled. One of our graphs is still showing abnormal behavior.
3:25 PM PDT: Compensation Mode has been disabled as it appears that this has been resolved.
3:11 PM PDT: The launcher is now online again.
3:05 PM PDT: The site fix is out, and while we'll keep an eye on it everything looks good on that front.
3:04 PM PDT: PvP.net is much more responsive, things are calming down.
2:53 PM PDT: Our internal databases are back up to speed.
2:52 PM PDT: We will be doing a quick restart of the community site.
2:48 PM PDT: The launcher is currently busy while we triage this issue.
2:45 PM PDT: We have a potential fix for the site and are working on releasing it ASAP.
2:44 PM PDT: Compensation Mode ('The Button') has been enabled.
2:36 PM PDT: NA queues begin lengthening, Champion Select has instability.
2:30 PM PDT: One of our databases began slowing down.
2:15 PM PDT: NA website first experienced intermittent outages. Began investigation.
Thanks for your patience, and check back here for updates.
(Edit: Also, be sure to check out the Q&A session with Pendragon and Tamat in our IRC channel here: http://webchat.quakenet.org/?channels=#leagueoflegends )
On the subject of Compensation Mode: Loss Forgiven is a special mode we can enable during times of widespread server issues to reduce the impact of server instability or networking issues. Unfortunately we can not retroactively apply this mode, and our system does not allow us to adjust Elo, wins, losses, or leaves. The system was designed this way to prevent corruption, but we are working to make improvements regarding accidental disconnects and server crashes such as this one. I apologize that Loss Forgiveness is not able to affect statistics already recorded.