Riot Help!

The Panda 09·6/2/2016, 3:20:21 AM·1 votes·476 views

This has happened to me multiple time in the past few patches. And now Ive been flagged and reported as an afker. Please put in a system that helps people that have random internet issues from being reported or flagged as an afker. I feel like issues like this in witch it makes a bad game experience for me and other people. It will help people from getting banned or unable to play for sometime.

2016-06-01T21-17-14: LogOut_File: : logfile started 2016-06-01T21-17-14: Net Status: low-level initialize success. 2016-06-01T21-17-14: Note that this new version (12/19/2011) has reduced the frequency of updates so the numbers will be larger 2016-06-01T21-17-14: time = time of logging 2016-06-01T21-17-14: address = address of IP address 2016-06-01T21-17-14: incoming = total size of messages set to me in bytes. Spikes can indicate lag. 2016-06-01T21-17-14: outgoing = total size of messages set from me in bytes. Spikes can indicate lag. 2016-06-01T21-17-14: app_ctos = client to server bytes delta excluding overheads (app data only) 2016-06-01T21-17-14: app_stoc = server to client bytes delta excluding overheads (app data only) 2016-06-01T21-17-14: loss = number of packets lost. Can indicate lags. Some node on the network is dropping packets or taking to long and we have to resend them. 2016-06-01T21-17-14: sent = number of packets sent. Spikes can indicate lag. 2016-06-01T21-17-14: ping = how long it takes for a packet to get back and forth. Spikes can indicate lag. 2016-06-01T21-17-14: variance = how much the ping is changing from avg ping. Spikes can indicate lag. 2016-06-01T21-17-14: reliable delayed = This occurs when we drop reliable packets from sending this frame because we are sending to much data. Unreliable are more likely to be dropped than reliable. 2016-06-01T21-17-14: unreliable delayed = This occurs when we drop unreliable packets from sending this frame because we are sending to much data. 2016-06-01T21-17-14: app update delayed = This occurs when the app is taking to long to run code caused by network packets (ie CPU) and packets are delayed until the next frame 2016-06-01T21-17-14: Time spent in critical section (frame) = This is the time the network thread is blocking the main thread from doing anything. 2016-06-01T21-17-14: [time], [address], [incoming], [outgoing], [app_ctos], [app_stoc], [loss], [sent], [ping], [variance], [reliable delayed], [unreliable delayed], [app update delayed], [Time spent in critical section (frame)] 788,X.X.X.X,82,98,0,0,0,2,453,82,0,0,0,0 10808,X.X.X.X,7997,1257,5725,197,1,30,179,124,0,0,1,0 20862,X.X.X.X,137932,6202,71656,1429,5,45,336,265,0,0,13,0 30863,X.X.X.X,222364,12418,73083,2556,8,60,1459,615,0,0,14,0 40864,X.X.X.X,288960,18700,58935,2694,8,70,754,655,0,0,15,0 50907,X.X.X.X,343482,26036,36212,2752,9,79,910,763,0,0,15,0 60967,X.X.X.X,377474,31193,26433,2237,9,93,370,295,0,0,15,0 70984,X.X.X.X,415434,37323,28733,2582,9,106,313,134,0,0,15,0 80986,X.X.X.X,468491,44164,44235,3037,9,124,187,74,0,0,15,0 90987,X.X.X.X,525564,50765,37498,3187,15,149,666,771,0,0,15,0 100993,X.X.X.X,565649,55624,27774,2213,16,162,1377,384,0,0,15,0 111049,X.X.X.X,634722,61163,42927,2231,19,174,566,495,0,0,18,0 121081,X.X.X.X,704063,65800,62558,464,21,181,432,331,0,0,24,0 131141,X.X.X.X,733552,70658,28700,2346,24,192,214,183,0,0,24,0 141143,X.X.X.X,774703,77285,30428,2893,26,209,215,97,0,0,24,0 151144,X.X.X.X,845055,81591,38501,1594,29,219,684,781,0,0,24,0 161148,X.X.X.X,883175,84998,22939,1537,31,226,789,633,0,0,24,0 171192,X.X.X.X,959377,91928,99063,2674,31,240,258,165,0,0,28,0 181213,X.X.X.X,1012577,98843,39467,3211,32,257,123,73,0,0,28,0 191250,X.X.X.X,1078216,105644,43357,2917,33,269,337,213,0,0,28,0 201275,X.X.X.X,1180190,113863,67213,3107,33,281,315,261,0,0,29,0 211277,X.X.X.X,1252428,120900,52234,2953,35,295,245,118,0,0,29,0 221330,X.X.X.X,1303719,126541,38832,2425,37,307,451,428,0,0,29,0 231366,X.X.X.X,1346750,131841,32144,2284,38,320,280,283,0,0,29,0 241381,X.X.X.X,1380259,136605,2393,276,40,333,256,159,0,0,29,0 251423,X.X.X.X,1402836,140927,18158,2170,40,347,185,136,0,0,30,0 261467,X.X.X.X,1444430,147321,32521,2834,41,364,105,84,0,0,30,0 271508,X.X.X.X,1485568,153505,31538,2816,43,378,184,134,0,0,30,0 281509,X.X.X.X,1528584,159115,24936,2568,46,393,503,322,0,0,30,0 291510,X.X.X.X,1559043,163184,12412,2065,52,413,680,283,0,0,30,0 301511,X.X.X.X,1592467,166730,15063,1666,53,422,506,307,0,0,30,0 311513,X.X.X.X,1651010,172085,81546,2481,58,440,272,186,0,0,31,0 321514,X.X.X.X,1711974,178107,54043,2748,60,457,210,133,0,0,31,0 331519,X.X.X.X,1744191,181458,13091,1887,79,504,834,511,0,0,31,0 341522,X.X.X.X,1760933,183542,9372,1188,121,555,983,338,0,0,31,0 351568,X.X.X.X,1886446,190876,53106,1916,142,578,2281,427,0,0,32,0 361572,X.X.X.X,1892996,192472,226,292,154,626,2621,916,0,0,32,0 371580,X.X.X.X,1942667,195840,35351,1204,189,663,11596,1258,0,0,32,0 2016-06-01T21-23-32: Memory Allocations Current Allocations = 98 Total Allocations = 69386 Max Allocations = 1912 Out of Pool Allocations = 2186 Out of Pool dealloc = 2178

2016-06-01T21-23-37: LogOut_File: : logfile stopped

3 Comments

Deep Terror Nami6/2/2016, 3:27:56 AM2 votes

I would suggest checking out the Connection Troubleshooting Guide. Perform the steps there to ensure your connection is set up properly and working, and if you continue to have issues you may perform a ping/traceroute to discover the source of your issues. I recommend the WinMTR program. Run it for 10-15 minutes to the below Riot NA server IP, and if you're having issues post the results on the Help & Support board or submit a ticket;

104.160.131.1