VERY frequent Pvp.net timeouts

notsoraka·Feb 27, 2016·1 votes·554 views

So, immediately after patch 6.4, I noticed a critical change in the client. All of the sudden, my connection to Pvp.net was acting very strange. So here is the issue. My Pvp.net connection repeatedly times out, about every ten seconds or so. I can't queue for anything besides an ARAM(because Pvp.net disconnect boots me from queue in draft), I can't change masteries in champ select or runes, or change my summoner spells. To get into an aram I probably have to try queueing 5-6 times before I finally get the timing right. When I head into a game, my connection is fine. I would really like to get this resolved. I have over 5k matches played and several years under my belt, this game is literally my heart. My heart is broken.

5 Comments

Deep Terror NamiFeb 27, 20162 votes

Hey notsoraka,

Could you perform the steps (if there are any you haven't completed) on the Connection Troubleshooting Guide to make sure your connection is set up properly for me? Reset your router and modem by unplugging them for 5 minutes as well.

If those steps don't help, running a traceroute and sharing the results might show us where it's going wrong. I suggest downloading the WinMTR Network Diagnostic Tool, then use that to run a traceroute to the following IP's (allow this to run for 5-15 minutes);

104.160.131.1

Export the results to a text file and paste them here.

notsorakaFeb 27, 20161 votes

When I try to go to the winmtr page, it gives me a name not resolved error. Anyone other software that may be useful here?

Deep Terror NamiFeb 27, 20162 votes

It looks like the site is down at the moment. In the meantime you can run a tracert from your Command Prompt manually, though it's not as good since it doesn't take readings over a period of time (so can miss lag spikes/packet loss).

Press the [Windows Key] (that is the key on the left side of the space bar, between ctrl and alt) + R
Type cmd in the search bar and click "Ok". You should now see a black window with white letters.
Highlight and copy the command;

(tracert 104.160.131.1) > "%USERPROFILE%\desktop\Tracert.txt"

Paste this into the cmd window (black box with white letters) by right clicking and selecting "Paste". Do not use the Ctrl+V shortcut as it will not work!
Depending on your connection, the trace may take 5-15 minutes to complete. A text file with the Tracert log will be created on your Desktop when it finishes.
Please check that the command ran properly - if Tracert.txt contains a single line, it did not run properly.
Paste the text from that file here.

notsorakaFeb 27, 20161 votes

Here are the results; Tracing route to 104.160.131.1 over a maximum of 30 hops

1 1 ms 4 ms <1 ms router [10.5.12.1] 2 2 ms 4 ms 2 ms 192.168.0.1 3 35 ms 51 ms 33 ms hlrn-lns-gw01.inet.qwest.net [206.196.132.7] 4 34 ms 37 ms 31 ms hlr-bigip-01-86.inet.qwest.net [206.196.142.193] 5 59 ms 55 ms 44 ms hlr-svcs-10.inet.qwest.net [206.196.142.204] 6 48 ms 46 ms 42 ms hlr-core-01.inet.qwest.net [205.171.253.61] 7 39 ms 36 ms 34 ms 63.145.218.10 8 75 ms 72 ms 90 ms 104.160.138.35 9 74 ms 72 ms 84 ms ae34-br01.chi01.riotdirect.net [104.160.159.22] 10 73 ms 72 ms 76 ms 104.160.131.1

Trace complete.

notsorakaFeb 28, 20161 votes

Today, the website for that program is down as well.