Everyone,

If you play a game and get lag, check which server you were playing on. You do this by going to the following path on your computer:

C:\Riot Games\League of Legends\Logs\Network Logs

and checking the most recent named network log. It will look something like this:

Sat Jan 12 22:53:35 2013: LogOut_File: : logfile started
Sat Jan 12 22:53:35 2013: Net Status: low-level initialize success.
Sat Jan 12 22:53:35 2013: Note that this new version (12/19/2011) has reduced the frequency of updates so the numbers will be larger
Sat Jan 12 22:53:35 2013: time = time of logging
Sat Jan 12 22:53:35 2013: address = address of IP address
Sat Jan 12 22:53:35 2013: incoming = total size of messages set to me in bytes. Spikes can indicate lag.
Sat Jan 12 22:53:35 2013: outgoing = total size of messages set from me in bytes. Spikes can indicate lag.
Sat Jan 12 22:53:35 2013: app_ctos = client to server bytes delta excluding overheads (app data only)
Sat Jan 12 22:53:35 2013: app_stoc = server to client bytes delta excluding overheads (app data only)
Sat Jan 12 22:53:35 2013: 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.
Sat Jan 12 22:53:35 2013: sent = number of packets sent. Spikes can indicate lag.
Sat Jan 12 22:53:35 2013: ping = how long it takes for a packet to get back and forth. Spikes can indicate lag.
Sat Jan 12 22:53:35 2013: variance = how much the ping is changing from avg ping. Spikes can indicate lag.
Sat Jan 12 22:53:35 2013: 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.
Sat Jan 12 22:53:35 2013: unreliable delayed = This occurs when we drop unreliable packets from sending this frame because we are sending to much data.
Sat Jan 12 22:53:35 2013: 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
Sat Jan 12 22:53:35 2013: Time spent in critical section (frame) = This is the time the network thread is blocking the main thread from doing anything.
Sat Jan 12 22:53:35 2013: [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)]
Sat Jan 12 22:53:41 2013: A new client connected from 216.133.234.155.

The IP Address in bold is what you should post to help out the devs the most. You could also attach the network log to your post by using the advanced editor. I attached a sample network log for you to make sure you've got the right file.

Hope this helps expedite the process!

Attached Files

2013-01-13_03-08-32_netlog.txt (23.3 KB, 15 views)

My match history also has been riddled with defeats because I perpetually dc and lag out.

It's good to see this is being addressed. Much appreciated, and sorry for being salty in other threads. (I thought Riot was completely ignoring it).

--------------------------------------------------------------------------
ISP: Sasktel


Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\Users\Tyler>tracert 216.133.234.193

Tracing route to 216.133.234.193 over a maximum of 30 hops

1 2 ms 2 ms 2 ms homeportal [172.16.1.254]
2 * * * Request timed out.
3 52 ms 46 ms 46 ms 207-47-191-218.ngai.static.sasknet.sk.ca [207.47
.191.218]
4 120 ms 130 ms 110 ms 142.165.0.114
5 113 ms 84 ms 85 ms 80.157.130.17
6 140 ms 101 ms 110 ms was-sb1-i.WAS.US.NET.DTAG.DE [62.156.131.162]
7 559 ms 300 ms 105 ms 194.25.211.18
8 165 ms 168 ms 176 ms 0.xe-2-0-0.XL3.LAX15.ALTER.NET [152.63.2.66]
9 154 ms 156 ms 172 ms POS6-0-0.GW3.LAX15.ALTER.NET [152.63.112.105]
10 172 ms 175 ms 145 ms internapGIGE-gw.customer.alter.net [157.130.236.
110]
11 172 ms 148 ms 179 ms border1.po2-20g-bbnet2.lax010.pnap.net [216.52.2
55.103]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
--------------------------------------------------------------------------

I've also tried wiring in, but it doesn't help. And I've experienced the exact same thing at my friends house (almost all of my friends have been experiencing it, some on Sasktel, some Shaw).

In fact yesterday we had a 5 man team dc and freeze session for an entire game. Luckily the other team were good sports about it.

I've attached a couple network logs in case they help.

Attached Files

	2013-01-17_16-25-55_netlog.txt (31.6 KB, 3 views)
	2013-01-17_15-36-53_netlog.txt (17.2 KB, 3 views)

Tracing route to 216.133.234.193 over a maximum of 30 hops

1 5 ms 2 ms 2 ms 192.168.1.1
2 41 ms 40 ms 39 ms 207.191.131.193
3 40 ms 40 ms 40 ms 10.0.50.165
4 * 41 ms 52 ms 10.0.4.1
5 47 ms 41 ms 42 ms 209-81-97-49.static.arvig.net [209.81.97.49]
6 41 ms 42 ms 40 ms 209-81-97-1.static.arvig.net [209.81.97.1]
7 60 ms 59 ms 59 ms 137.192.65.69
8 59 ms 60 ms 60 ms te4-2-ZMS-edge1.btb1.zbi-net.net [199.199.48.1]

9 59 ms 59 ms 112 ms ae6.100-ONVOY-INC.edge2.chi2.net [4.79.160.9]
10 60 ms 61 ms 60 ms vl-3502-ve-116.ebr1.Chicago2.Level3.net [4.69.15
8.6]
11 59 ms 59 ms 59 ms ae-1-51.edge3.Chicago3.Level3.net [4.69.138.136]

12 60 ms 59 ms 76 ms gblx-level3-10g.Chicago3.Level3.net [4.68.62.202
]
13 119 ms 121 ms 119 ms INTERNAP.te1-4.ar4.LAX1.gblx.net [64.215.30.78]

14 120 ms 120 ms 120 ms border1.po2-20g-bbnet2.lax010.pnap.net [216.52.2
55.103]


Mine started this morning, I dont know where it came from because last night I was just fine....

This was from the last game I played last night.

(Thu Jan 17 03:11:08 2013: A new client connected from 64.7.194.135.) Hope that helps.

trying to play lag out disconnect, that makes a leave and ppl reporting me, been a month that im lagging all the time , it being frustating !!!

I have been experiencing this exact same issue except mine seems to have gotten worse over the last 2 weeks or so. I also experience game crashes. It happens alot of times right before I go into champion selection and right after a game ends. Sometimes I get a message about adobe air failing or something like that...Hopefully this gets fixed soon...it's quite annoying to get random lag spikes.

Also, my interwebs are working fine...all speed tests say everything is working great and no issues. Downloading at normal speeds with no intermittency.

So my roommate isn't getting these lag spikes, and I am. I'm running a 3d Traceroute right now. It's definitely not the connection as far as I know, though he is wired and I'm wireless I've had no problems with my wireless ever, and I only seem to be experiencing problems in League and nothing else.

This has only been happening for the past day, but it makes the game completely unplayable. And I have a new Kayle skin to try out!

Now the 3d Traceroute's done. Seems to be having random spikes at my router, but that that's not the only place it's going on. Have at it, network people.

Attached Thumbnails

 

its getting worse, constant spikes which lead to free kills on myself and im getting reported because im "feeding". do i need to not queue or something til this gets fixed? its happened in my past 4 games. its not just 1 or 2 in each, it happens almost nonstop throughout each game. i would prefer not to get banned because i can not control my character

Please fix this. I feel like I lag on a green FPS.