PONG// pong.com v3.0OPERATIONAL
pong@pong-com blog/league-of-legends-lag-fix-guide$
GamingMay 8, 2026· 12 min read
ByPong.com Editorial Team· Editorial Team

League of Legends Lag Fix Guide: Lower Ping, Fix Latency & Climb Faster

League of Legends lag costing you ranked games? This guide explains how Riot routes your traffic, why your ping spikes during teamfights, and the proven fixes that actually lower your latency. Includes a free speed test to measure before and after each fix.

You flash-Q onto their carry. The combo is clean, the angle is perfect, and you see the damage numbers start to tick. Then your champion freezes for half a second, and when the game catches up, you are standing in the middle of five enemies with Flash on cooldown. Your team pings you. That was not a misplay. That was a 120ms ping spike eating your combo at the worst possible moment, and Riot's server did not care that you pressed the buttons in time.

This guide covers exactly why League of Legends lag happens, how Riot's infrastructure routes your connection, and the 9 fixes ranked by how often they actually work. Run a quick speed test with the tool below to capture your baseline numbers, then re-test after each fix to measure real improvement instead of guessing.

Loading game latency test...

Latency, ping, jitter, and bufferbloat: what they mean for League

Before diving into fixes, you need to understand the four metrics that determine how your game actually feels. Most players only look at the ping number in the corner, but that alone does not explain why your Ahri charm missed or why your last-hit timing feels off.

  • Latency: the round-trip time for a single packet to reach Riot's server and return. Measured in milliseconds. Under 30ms is ideal for League; over 80ms means you are reacting to the game state as it was 80ms ago, which is enough to miss a flash reaction or lose a close last-hit.
  • Ping: technically a specific tool, but in gaming it means the same thing as latency. The number in the top-right of your League client (Ctrl+F to toggle) is your live latency to Riot's server.
  • Jitter: how much your ping fluctuates between packets. Steady 50ms feels playable; ping swinging from 30ms to 90ms every few seconds makes skill shots feel inconsistent and last-hitting feel random. High jitter is often worse than high-but-stable ping.
  • Bufferbloat: when your router's buffer fills up under heavy network load (someone streaming, uploading, or downloading), every packet gets stuck in line. Your ping can jump by 100 to 400ms during these spikes. This is why your League ping seems fine until someone in your house starts a video call.

A speed test that only shows download and upload numbers tells you nothing about these four metrics. You need a tool that measures all of them together to actually diagnose League lag.

How Riot's servers handle your connection

Riot Games moved all NA League of Legends servers to Chicago, Illinois in 2015 (previously in Portland, Oregon). This was a deliberate centralization: instead of running multiple server clusters, Riot chose a single location roughly equidistant from both coasts. If you live in the Midwest or East Coast, you probably got a massive ping improvement. If you live on the West Coast, your ping likely jumped from 20ms to 60 to 70ms overnight.

Other regions run their own server clusters: EUW servers are in Amsterdam, EUNE in Frankfurt, KR in Seoul, BR in Sao Paulo, LAN in Miami, LAS in Santiago, OCE in Sydney, JP in Tokyo, and TR in Istanbul. Unlike Fortnite, you cannot switch regions mid-game. Your account is locked to a region, and transferring costs RP.

Riot also runs a dedicated peering program called Riot Direct (previously the Riot Games ISP Peering Initiative). They negotiate direct connections with major ISPs to bypass the public internet. If your ISP peers with Riot, your traffic takes a shorter, more stable path. If it does not, your packets bounce through multiple third-party networks before reaching Chicago.

Ping lag vs FPS drops: how to tell the difference

This is the most common misdiagnosis in League. Ping lag is a network problem: your inputs reach the server late, other players' movements stutter or teleport, and skill shots feel delayed. FPS drops are a hardware problem: the entire game stutters or freezes, but your ping stays low. The fix for each is completely different.

SymptomPing lag (network)FPS drops (hardware)
Champions teleport or skipYes, other players stutterNo, everything stutters equally
Ping number spikesYes, often 100ms+ jumpsNo, ping stays normal
Input feels delayedYes, actions happen lateNo, the screen just freezes
Worst during teamfightsSometimes (bufferbloat)Almost always (GPU/CPU load)
Reconnect warning appearsOftenRarely

If your FPS counter (Ctrl+F, top-right next to ping) drops below 60 during fights, your issue is hardware, not network. Close background apps, lower your graphics settings, and make sure your GPU drivers are current. This guide focuses on network lag, the kind that shows up in your ping number.

9 common causes of League of Legends lag (and how to fix each)

Ranked from most impactful and easiest to fix down to edge cases. Work through them top-down and re-test your ping after each one. Stop when your ping stabilizes under 40ms.

1. You are playing on Wi-Fi (the #1 cause)

Wi-Fi adds 5 to 25ms of jitter even under ideal conditions, and every device on your network fights for airtime. That jitter is what makes your last-hitting feel inconsistent and your skill shots feel unreliable between games. Every pro and high-elo player uses Ethernet. Fix: connect to your router with a Cat5e or Cat6 cable. Expect a 10 to 30ms ping drop and drastically more stable ping, which matters more than the raw number for League.

If running a cable is not an option, consider a powerline Ethernet adapter (TP-Link AV2000 is a popular choice). Not as good as direct Ethernet, but far more stable than Wi-Fi for gaming. Compare the two with a Wi-Fi speed test.

2. Bufferbloat spiking your ping under load

Bufferbloat is the reason your ping is 35ms in practice tool but jumps to 120ms during a ranked game when your roommate starts streaming. Your router's buffer fills up with their traffic, and your League packets wait in line behind Netflix. Fix: enable SQM (Smart Queue Management) or fq_codel/CAKE in your router's QoS settings. If your router does not support it, a $99 router upgrade with built-in smart queue solves this permanently.

Run our bufferbloat test to check. Grade A or B means you are fine. Grade C or worse is almost certainly causing your mid-game spikes.

3. Your ISP does not peer with Riot Direct

Riot Direct is Riot's private backbone network that provides optimized routing to their servers. Major ISPs like Comcast, Spectrum, AT&T, and Verizon have direct peering agreements. Smaller regional ISPs often do not, which means your traffic takes a longer, less stable path through the public internet. Fix: check if your ISP peers with Riot (Riot has published peering partners in the past). If not, the workarounds are: (a) switch to an ISP that peers with Riot, or (b) try a gaming tunnel like Haste or ExitLag that can sometimes route around bad peering.

4. Background apps eating your bandwidth

The Riot client auto-updating other games. Windows Update downloading in the background. Discord screen-sharing your game to friends. Any of these can saturate your upload, and League uses UDP, so its packets get no priority over bulk downloads. Fix: before queueing ranked, check Task Manager (Ctrl+Shift+Esc) > Network tab. Kill anything using more than 100 KB/s. Pause Windows Update for a week (Settings > Windows Update > Pause). Close any browser tabs running video.

5. Wrong DNS server slowing everything down

Your DNS server does not directly affect your in-game ping (League connects via IP once the game starts), but it affects how fast the client loads, how quickly you connect to the server at game start, and how responsive champion select feels. Slow DNS can also cause the dreaded 'Attempting to Reconnect' message at game start. Fix: switch your DNS to Cloudflare (1.1.1.1) or Google (8.8.8.8). Change it in your network adapter settings or at the router level to cover all devices.

6. VPN adding unnecessary hops

A VPN tunnels your traffic through a third-party server, adding 10 to 80ms depending on how far that server is from you and from Chicago. If you use a VPN for privacy, enable split-tunneling so League traffic goes direct while everything else stays on the VPN. Most VPN clients (NordVPN, ExpressVPN, Mullvad) support this. Fix: disable the VPN entirely for gaming, or configure split-tunnel to exclude League of Legends and the Riot client.

7. Router needs a reboot

Routers accumulate stale NAT table entries, leak memory, and degrade over weeks of uptime. If your ping was fine until recently and you have not restarted your router in a month, this is statistically your issue. Fix: unplug from power for 30 seconds, plug back in, wait 2 minutes for a full reboot, then re-test. Free, takes 3 minutes, and works more often than it should.

8. Packet loss on your line

Even 1 to 2% packet loss makes League feel terrible. Champions teleport, your abilities fire late, and last-hitting becomes a coin flip. Packet loss is more common on cable internet than fiber, especially during peak hours (7 to 11pm). Fix: run our packet loss test. If you see more than 1% loss, call your ISP with specific timestamps and test results. ISPs respond much better to documented evidence than vague complaints about lag.

9. Geographic distance from Chicago

Physics sets a floor. Light in fiber travels at roughly 200km per millisecond round-trip. If you are in Los Angeles (~2,800km from Chicago), your absolute minimum ping is around 28ms even on a perfect connection. Seattle players see a floor near 30ms. East Coast and Midwest players can hit 10 to 20ms because they are physically closer. Fix: there is no fix for distance. But you can make sure nothing else is adding to it. If you are in LA with 70ms ping, your line is adding 40ms of overhead that the fixes above can eliminate.

How ping affects each role in League

Not all roles suffer equally from high ping. Understanding which parts of your gameplay are most affected helps you decide how urgently you need to fix your connection.

RolePing sensitivityWhat breaks first
ADCVery highKiting, orb-walking, and animation cancels require precise timing. At 80ms+ you are auto-attacking significantly later than your opponent.
Mid (assassins)Very highBurst combos like Zed W-E-Q or LeBlanc W-Q-R need tight sequencing. High ping drops your combo DPS because the server processes inputs late.
Mid (mages)MediumSkill shots are aim-predicted client-side, so they feel OK. But dodging enemy skill shots on high ping is much harder since you see them late.
TopMedium to highShort trades and ability spacing matter. Riven, Fiora, and Camille combos degrade noticeably above 50ms.
JungleMediumClear speed is unaffected, but gank timing and smite fights are worse. Smite on 80ms vs 20ms is a real disadvantage at objectives.
SupportMediumEngage supports (Thresh, Nautilus) need fast hooks. Enchanters are the most ping-forgiving role in League.

What is a good ping for League of Legends?

Ping rangeVerdictWhat it feels like in-game
Under 20msPro-tierInstant responsiveness. Orb-walking and animation cancels feel effortless. This is what LCS players get at the studio.
20 to 40msExcellentRanked is a completely fair fight. No perceptible delay on any ability or auto-attack.
40 to 60msGoodPlayable at all ranks. You might lose a very close kiting duel against a 15ms player, but it rarely decides games.
60 to 80msAcceptableYou feel the delay on fast combos. ADC kiting and assassin burst combos are noticeably slower.
80 to 120msPlayable but painfulDodge reactions are late. Last-hitting under tower requires pre-clicking. Competitive ranked is a handicap.
120ms+Very difficultThe game feels unresponsive. Champions stutter, abilities fire late. Consider fixing your connection before playing ranked.

League runs at a 30Hz tickrate (30 server updates per second), which means each server tick is about 33ms. If your ping is 60ms, you are always at least two ticks behind the server. At 120ms, you are nearly four ticks behind. Stable ping matters more than low ping: 50ms with 2ms jitter plays better than 30ms with 15ms jitter because the game client can predict and interpolate a steady connection much more accurately.

How to use a speed test to diagnose League of Legends lag

Most speed tests give you a big download number and call it a day. That number is nearly useless for diagnosing League lag. League uses less than 100 KB/s of bandwidth. Your 500 Mbps download speed is not the problem. The problem is in your latency, jitter, bufferbloat, and packet loss, the four metrics that actually correlate with how the game feels.

Pong's speed test measures all four in a single 30-second run. It tests against Cloudflare's global edge network, so the numbers reflect your real-world connection quality rather than a flattering test against your ISP's internal server. Here is how to use it to fix your League lag:

  1. Run a baseline test right now. Write down your idle ping, loaded ping, jitter, and packet loss numbers.
  2. Apply one fix from the list above (start with Ethernet if you are on Wi-Fi).
  3. Re-run the test. Compare the numbers.
  4. Repeat until your idle ping is under 40ms, your loaded ping is within 15ms of idle, your jitter is under 5ms, and your packet loss is 0%.
  • If your idle ping is over 40ms, you either have a routing problem (ISP path to Chicago) or you are very far from the server geographically
  • If your loaded ping jumps 50ms+ above your idle ping, you have bufferbloat (enable SQM/CAKE on your router)
  • If your jitter is over 5ms, you are on Wi-Fi or have an unstable line (switch to Ethernet first, then investigate your ISP)
  • If packet loss is over 1%, your line has a physical issue or your ISP is overloaded at peak hours (call your ISP with timestamps and test results)

When Riot is the problem, not you

Sometimes the lag is genuinely on Riot's end. Server issues, infrastructure maintenance, or regional outages can spike everyone's ping simultaneously. Before you tear apart your network setup, check status.riotgames.com for any ongoing incidents. If the League subreddit front page has multiple posts about lag spikes at the same time, it is almost certainly server-side.

Common Riot-side patterns: patch days (usually every two weeks, typically on Wednesday), the first few days of a new season or ranked split, major event launches (Worlds watch parties, mid-season updates), and occasionally ISP-level peering disruptions that Riot posts about on their server status page.

Quick wins (do these in the next 5 minutes)

  1. Switch to Ethernet if you are on Wi-Fi (single biggest improvement for most players)
  2. Restart your router (unplug 30 seconds, plug back in, wait 2 minutes)
  3. Close the Riot client background processes, Steam, Discord screen-share, and any browser tabs with video
  4. Disable your VPN or enable split-tunneling to exclude League
  5. Run our bufferbloat test and packet loss test to identify line issues
  6. Switch your DNS to Cloudflare (1.1.1.1) or Google (8.8.8.8)
  7. Pause Windows Update for 1 week (Settings > Windows Update > Pause)
  8. In League, press Ctrl+F to show your live ping, then play a game and note when spikes happen
  9. Re-test your connection with Pong's speed test and compare to your baseline

In-game settings that help with lag

These settings will not fix your network, but they reduce the impact of lag on your gameplay and help you identify problems faster.

  • Enable network stats display: Press Ctrl+F in-game to toggle. Watch your ping and FPS numbers. This tells you instantly whether a problem is network (ping spike) or hardware (FPS drop).
  • Movement prediction: This is enabled by default in League and helps smooth out your champion movement on higher ping. Do not disable it.
  • Close the client during game: In the Riot client settings, enable 'Close client during game.' The client uses CPU and memory in the background, and on older hardware this can cause FPS drops that feel like lag.
  • Lower graphics if you are borderline: If your FPS dips below 60 during teamfights, lower shadows, effects quality, and character quality. This frees up system resources and makes it easier to distinguish between network lag and FPS lag.

Conclusion

League of Legends lag is rarely a mystery once you know where to look. It is almost always one of nine specific problems, and you can usually fix it in under 30 minutes by working through them in order. The diagnostic pattern that works: run a real speed test that measures latency, jitter, bufferbloat, and packet loss. Identify which metric is broken. Apply the matching fix. Re-test. Move to the next one.

If you only do one thing today, switch from Wi-Fi to Ethernet and re-run a speed test. That single change fixes more League lag than every other tweak combined. After that, fixing bufferbloat is the highest-leverage move because it solves the mid-game spike problem that makes teamfights feel like a slideshow while your ping is supposedly fine.

Frequently asked questions

?>Why does my League ping spike during teamfights?
If your ping is stable in lane but spikes during 5v5 fights, you likely have bufferbloat. Teamfights generate a burst of network traffic (ability updates, particle effects, position data for 10 champions), and if your router's buffer is already partially full from other household traffic, that burst pushes it over the edge. Enable SQM or CAKE in your router's QoS settings to fix it. Confirm by running a bufferbloat test before and after.
?>Is 60ms ping playable in League of Legends?
Absolutely. 60ms is playable at every rank. Many Challenger players on the West Coast play at 55 to 65ms ping. You will be at a slight disadvantage in very close kiting duels against a 15ms opponent, but game knowledge, positioning, and macro play matter far more than a 40ms ping difference. That said, if you are experiencing 60ms with high jitter (ping swinging from 40ms to 80ms), that is much worse than a stable 60ms, and the jitter is what you should fix.
?>Will a faster internet plan lower my League ping?
Almost never. League uses less than 100 KB/s of bandwidth. Upgrading from 100 Mbps to 1 Gbps on the same ISP will not change your in-game ping by even 1ms. What actually helps: switching from cable to fiber (lower jitter, better peering), switching to an ISP that peers with Riot Direct, and fixing bufferbloat. Run a speed test and look at your ping, jitter, and bufferbloat grade. Ignore the headline download number.
?>Why is my League ping higher than my speed test ping?
Speed tests typically measure ping to the closest server, often within your ISP's own network. League pings Riot's server in Chicago, which is farther away and routes through different infrastructure. A 20 to 40ms gap between speed test ping and in-game ping is normal. A 60ms+ gap means your ISP's routing to Chicago is inefficient. Try a speed test that measures to a server near Chicago, or use Pong's test which measures to Cloudflare's edge for a more realistic baseline.
?>Does Riot Direct actually help with ping?
Yes, significantly. Riot Direct is Riot's private backbone that bypasses the public internet. ISPs that peer with Riot Direct typically deliver 10 to 30ms lower ping and much less jitter than ISPs that route through the open internet. If you are choosing between two ISPs in your area and one peers with Riot, pick that one. You can check by running a traceroute to the League server IP: if you see 'riotdirect' or 'rdirect' in the hop names, your ISP peers with them.
?>I moved from East Coast to West Coast and my ping doubled. Is there a fix?
Unfortunately, physics is the main factor here. The NA server is in Chicago, which is much closer to the East Coast. West Coast players typically see 50 to 70ms minimum even on perfect connections. You can minimize the overhead above that floor (Ethernet, no bufferbloat, good ISP peering), but you cannot get below the speed-of-light limit from your location to Chicago. If you are seeing 100ms+ from the West Coast, your line has fixable issues. If you are at 55 to 65ms, that is close to optimal for your location.
// SPEED TEST

Measure your real-world speed, ping, jitter, and bufferbloat. Free, no signup required.

> Run Free Speed Test

// Related Posts

Advertisement
// READY TO TEST?

Use our free speed test to measure your ping, download, upload, and bufferbloat. No signup required.

> Run Speed Test