League of Legends Network Lag and Packet Loss: Every Fix in Order

When Riot Games measured its own network in the mid-2010s, only 30 to 35 percent of League of Legends players were getting under 80ms to the servers. By the time the company finished building Riot Direct, its private global backbone, that number had climbed to roughly 50 percent (Riot Games Technology). That single detail explains most League lag: the game is not usually slow because Riot’s servers are slow. It is slow because of the short stretch of public internet between your house and the nearest point where your traffic hops onto Riot’s network, plus whatever is going wrong inside your own home.

I have spent 20-plus years in IT operations, and packet loss is the failure I have chased more than any other. It almost never lives where people first look. This guide walks the fixes in the order that actually finds the fault fastest, from reading League’s own network numbers to the handful of things worth escalating to your ISP.

What Riot Direct changes about how you troubleshoot

Most online games send your packets across the public internet, where backbone providers and ISPs route traffic along the cheapest path rather than the fastest one. That is how League traffic between California and Oregon once got sent through Denver, roughly a 500 percent jump in ping for no good reason (Kotaku).

Riot Direct fixes that by peering directly with ISPs. Where a normal game would ride transit links across several networks, Riot lays dedicated fiber and connects straight into ISP regional routers, then uses cold-potato routing to keep your packets inside its own backbone for as long as possible (Riot Games Technology, Part II).

The practical takeaway: once your packets reach a Riot Direct point of presence, the path is about as good as it gets. Your problems live before that handoff. That is why the fixes below start at your PC and work outward, and why “the servers are lagging” is almost never the real answer when a game like League feels broken.

Read League’s own network numbers first

League shows live network data during a match. Press Ctrl + F to toggle the ping and frame-rate readout in the top-right corner. Ping is round-trip time to your regional server; anything under 40ms feels crisp, 40 to 80ms is fine for most players, and above 80ms is where inputs start to feel late.

Ctrl + F does not show packet loss, though, and packet loss is what causes the rubber-band snap where your champion teleports back to where it was two seconds ago. To see it, launch with network logging on:

• Close League fully.
• Open your install folder, usually C:\Riot Games\League of Legends\Game.
• Make a shortcut to League of Legends.exe.
• Right-click the shortcut, choose Properties, and in the Target field add -netlog after the closing quote.
• Launch through that shortcut.

With netlog running you get packet loss percentage and jitter alongside ping. Read them like this:

• Ping: under 40ms ideal, under 80ms playable.
• Packet loss: target 0 percent. Even 1 to 2 percent produces visible stutter and missed inputs, because every dropped packet has to be re-sent before the game can act on it (Riot Support).
• Jitter: under 20ms. Jitter is ping that will not sit still, and it is often worse than a steady high ping because the game cannot predict it. If you want the full explanation, see our breakdown of jitter and why it hurts more than latency.

If ping is low but packet loss or jitter is high, you have a connection-quality problem, not a distance problem, and a gaming VPN will not fix it until you find the source.

Rule out the servers, then find the bad hop

Before you change a single setting, check status.riotgames.com for your region. Riot patches on a fixed cadence now (the 2026 schedule runs Wednesdays, patch 26.01 on January 8 through 26.24 on December 9), and the hours right after a patch are the most likely time for genuine server-side wobble (Riot Support patch schedule). If Riot lists a regional incident, stop; no home fix touches that.

If the servers are healthy, trace the path. WinMTR pings every router hop between you and the server and shows where loss or latency appears. Rather than pasting in an IP that may be stale, grab the real one League is using:

• Get into a game or the practice tool so the client is actively connected.
• Open Command Prompt and run netstat -b.
• Find the entry tied to League of Legends.exe and note the foreign IP address.
• Feed that IP into WinMTR, run it administrator, and let it collect 200-plus packets.

Then read the columns. If loss shows up at hop 1 or 2, the fault is inside your home: your router, your wiring, or Wi-Fi. If clean hops suddenly show loss at hop 3 or beyond, and it holds all the way to the destination, the problem is in your ISP’s network and no amount of Windows tweaking will move it. One caution from experience: a single middle hop showing 100 percent loss while later hops are clean is usually a router that de-prioritizes ping replies, not real loss. Only trust loss that persists from a hop to the end of the trace.

Fix your home network in the order that matters

Get off Wi-Fi

This is first because it is the highest-yield change and the one people resist most. Wi-Fi adds latency and, worse, introduces intermittent packet loss whenever a microwave, a neighbor’s channel, or a thick wall interferes. Riot’s own troubleshooting guide leads with the same instruction: use a wired connection to remove wireless interference from the equation entirely (Riot Support).

Run a Cat5e or Cat6 cable straight from PC to router and re-check netlog. If a cable genuinely is not possible, a MoCA adapter over your home’s coax is a far better fallback than powerline, which itself beats Wi-Fi for stability.

Kill bufferbloat, the lag spike almost nobody checks

Here is the fix that resolves more “my ping randomly jumps to 200 while my roommate is uploading” complaints than any router setting. When any device saturates your upload, cheap modem buffers fill with packets and your game traffic waits in line behind them. Your idle ping can be a perfect 15ms and your loaded ping can be 300ms, and League will rubber-band the entire time.

Test it: run the free Waveform Bufferbloat Test with nothing else running. It grades added latency under load. An A means under 5ms added; an F can mean 400ms-plus (Waveform). If you score C or worse, enable SQM (Smart Queue Management) on a router that supports fq_codel or CAKE, then set your upload and download shaping to about 85 to 95 percent of the real speed your line delivers. That headroom is what keeps the buffer from ever filling. A well-tuned SQM setup routinely takes a connection from F to A, and the in-game result is a flat ping line even when the household is busy.

DNS, briefly

Slow ISP DNS does not raise your in-game ping, but it can slow the client’s initial connect and store lookups. Switching to Cloudflare (1.1.1.1 / 1.0.0.1) or Google (8.8.8.8 / 8.8.4.4) is a two-minute change with no downside. Change it under Windows 11 Settings > Network & internet > your adapter > DNS server assignment, then run ipconfig /flushdns. Our guide to the best DNS servers for gaming covers the trade-offs if you want to benchmark them.

Skip port forwarding

Older League guides, including the previous version of this one, told you to forward a long list of TCP and UDP ports. Drop that step. League connects outbound over standard UDP, and Riot’s current connection troubleshooting does not list port forwarding as a fix at all. Modern routers handle the return path through NAT automatically. The only time it matters is a genuinely strict NAT blocking the connection, and even then, enabling UPnP on the router is the cleaner solution than hand-forwarding ports you will later forget you opened.

The one League-specific culprit worth checking: Vanguard

Vanguard is Riot’s kernel-level anti-cheat, and it has been mandatory for League since April 11, 2024. It works: Riot reported over 175,000 accounts banned in the first months, ranked scripting falling below 1 percent for the first time in nearly four years, and botting hours dropping from more than a million a day to under five thousand (Riot Games dev blog).

The catch is that Vanguard’s driver loads at boot and its client runs the whole time any Riot software is open, which costs some players FPS and adds a little to boot time. If your stutter is frame-rate stutter rather than network stutter (netlog shows fine ping and zero loss, but the game hitches), Vanguard sitting resident is worth ruling out.

As of June 24, 2026, there is a real option here: Vanguard On-Demand. It lets Vanguard run only while you are actually in a Riot game and shut down when you close it, instead of idling in the background all day. It is opt-in and hardware-gated, requiring Windows 11 25H2 or later plus Secure Boot, TPM 2.0, VBS, HVCI, and IOMMU. Riot said about 35 percent of players already meet those requirements and can flip it on immediately (Riot Games; PC Gamer). If you qualify, enabling it gives you back the idle system resources without disabling anti-cheat while you play.

Trim what else is on the wire

Background bandwidth is the most common cause of a mid-game spike on an otherwise healthy connection. Press Windows + R, run resmon.exe, open the Network tab, and sort by Total bytes per second. The usual offenders:

• Steam, the Epic launcher, or another game auto-updating.
• Windows Update pulling a package (throttle it under Settings > Windows Update > Advanced options > Delivery Optimization).
• Cloud sync from OneDrive, Google Drive, or Dropbox.
• A second person in the house streaming 4K or uploading.

If you run a decent router, adaptive QoS that prioritizes your gaming PC handles most of this automatically; see our QoS settings for gaming walkthrough. But QoS on your router cannot fix bufferbloat on your ISP’s side, which is exactly why the SQM step above comes first.

When the fault is your ISP, and what to actually ask for

If WinMTR keeps showing loss or latency starting at a hop several routers out from your home, and it repeats across days and times, the problem is your provider’s routing or congestion. Gather evidence before you call:

• Run ping -t 8.8.8.8 for 30-plus minutes during your normal play hours and screenshot the spikes and timeouts.
• Save two or three WinMTR traces that show the same bad hop.
• Note the times, because peak-hour-only degradation (roughly 6 to 11 PM) usually means local congestion in your neighborhood.

Then be specific with support. Vague “my game lags” tickets go nowhere. Because League runs on Riot Direct, the useful question is whether your ISP peers well with Riot near you, and whether they can see loss on the hop your trace flags. Ask about their peering in your region and whether a line fault or congestion is logged on your segment. You will not get them to re-architect their network, but a documented bad hop is how you get a truck roll or a routing correction instead of a script-reading brush-off. If your base ping to the correct server is already low and the loss is purely an ISP routing artifact, that is also the exact scenario where rerouting the traffic yourself pays off.

The order, condensed

Work top to bottom and stop when netlog goes clean:

1. Read Ctrl + F, then relaunch with -netlog to see packet loss and jitter.
2. Check status.riotgames.com so you are not chasing a server-side incident.
3. Trace the real server IP (via netstat -b) in WinMTR and locate the bad hop.
4. Get wired. This alone fixes a large share of loss and jitter.
5. Test bufferbloat on Waveform; enable SQM if you score C or worse.
6. Point DNS at Cloudflare or Google; flush the cache.
7. If frames hitch rather than the network, check Vanguard and enable On-Demand if your PC qualifies.
8. Close background bandwidth hogs and lean on router QoS.
9. If loss lives in your ISP’s hops, document it and escalate, or reroute around it.

Latency you can measure is latency you can fix. The reason this order works is that it moves outward from the parts you fully control toward the parts you do not, and by the time you reach your ISP you will have the WinMTR trace that turns a shrug into a work order. If you want the wider context on what these numbers mean, our explainers on what ping actually is and why even 1 percent packet loss breaks games go deeper than a single game guide can.