Start a League of Legends ping test inside the match
A League of Legends ping test is best treated as a short, repeatable observation during a real match or custom game, not as a web widget that can certify your connection. While in-game, press Ctrl+F to display latency (ping) and FPS. Riot says the shortcut can be rebound at Options > Hotkeys > Display > Toggle FPS Display. Watch both figures through a quiet moment and a busy fight rather than treating the first number you see as a verdict.
This is a guide to an in-game check, not an interactive ping tool.
Know what ping, packet loss, jitter and FPS each describe
Riot defines latency as the time for data to travel from your computer to Riot game servers and back, in milliseconds. Packet loss means packets fail to arrive and may need retransmission. Jitter is the change in latency over time; late or out-of-order packets can create lag. FPS is different: it is the rate at which the local computer renders frames.
| Signal | What it describes | Useful observation |
|---|---|---|
| Ping | Round-trip latency in ms | Note the displayed value at several moments |
| Packet loss | Packets that do not arrive | Check a Riot connection report or relevant NetLog after a troubled game |
| Jitter | Latency changing over time | Look for a pattern across observations, not one isolated spike |
| FPS | Local frame production | Compare it with the same scene and graphics setup |
A low displayed ping at one instant cannot rule out later packet loss or jitter. Write down the match time, what happened on screen, whether you were on Wi-Fi or Ethernet, and any concurrent streaming or downloads. That small record makes a later comparison useful.
Separate network trouble from an FPS drop
A match can feel bad for two very different reasons. Riot describes low FPS as a system that cannot keep up with the work the game asks it to do, often producing consistently low frame rate or drops in demanding moments. Network trouble concerns the delivery of match data. Neither symptom alone proves its cause.
Hypothetical example: ping stays near the same displayed number, but FPS falls from 120 to 25 during a visually busy fight. That is a reason to investigate local performance first, not proof of a route problem. In another hypothetical match, FPS remains steady while the displayed latency swings and the game rubber-bands. Record the pattern and investigate the connection path instead of changing graphics settings at random.
If frame rate is the issue, Riot advises checking system requirements, adjusting graphics settings gradually, and addressing competing background work. Test a graphics change in a custom game before relying on it in a match. Our high-refresh esports monitor guide explains why display refresh rate is another separate part of perceived responsiveness.
Check Riot’s service context before changing your setup
Before changing local settings, check Riot’s regional service-status page. Riot’s Basic Connections Troubleshooting Guide also points players to the regional Lag Report where available. After sign-in, that report aggregates data from recent games and compares a Connection Score with players and ISPs in the area. A score is a clue about a recent sample, not a universal quality rating or a diagnosis.
For a troublesome recent match, Riot’s Connection Troubleshooting Log Reader can process the match NetLog and return network statistics. Use the exact match with the symptom; testing a different, smooth game answers a different question. For general definitions beyond this game-specific workflow, see gaming latency, ping and tick rate. Do not use a general explainer to infer a League match’s server condition.
Make one safe, reversible change at a time
Start with the least invasive checks. Riot recommends a wired connection when practical because wireless interference can contribute to spikes or packet loss. It also identifies connection-heavy activity such as HD streaming, active downloads, voice software, and other apps as possible contributors to packet buffering. Riot advises against using a VPN or proxy as a connection fix.
Hypothetical check: play two comparable custom-game sessions with the same graphics settings and no active download. If the only deliberate difference is Wi-Fi in the first session and Ethernet in the second, keep the notes separate rather than declaring either setup “good” from one sample. This is an observation, not a benchmark.
Do not disable security software, guess IP addresses, alter router firewall rules, forward ports, or make DNS changes from a generic ping guide. Those actions carry system or network risk and require an official, situation-specific support path.
Save focused evidence if the issue repeats
When the same problem repeats, gather only the evidence Riot asks for. Riot says a NetLog is created for each game and records connection information over that match; its League logs guide identifies NetLogs as relevant to lag, rubber-banding, and disconnections. The League-specific guide also says Support usually needs only one or two files, not every log on the computer.
Match time, region, the observed symptom, in-game ping/FPS observations, and the affected game’s NetLog give Support a concrete starting point. Use Riot’s Connection Troubleshooting Log Reader for the affected recent game, or submit a Player Support ticket if the issue persists. Keep logs private: they are support diagnostics, not performance badges to post publicly.
When a League of Legends ping test is not enough
A display check is useful for sorting a symptom, not for proving why it happened. Repeated reconnects, disconnections, or reproducible packet loss deserve Riot’s guided support route with focused logs. A one-off spike may simply be an observation to compare later.
Keep this workflow narrow: display the numbers, sample a match, distinguish local FPS from connection signals, make one safe comparison, then escalate with evidence. The esports hub has adjacent technology explainers, but no guide can replace Riot’s current status information or Support review for a specific account, network, or match.
Sources
Riot Games Support — *Smart Ping* (18 February 2025).
Riot Games Support — *Basic Connections Troubleshooting Guide* (2 June 2026).
Riot Games Support — *Connection Troubleshooting - Log Reader* (29 May 2026).
Riot Games Support — *Low FPS & Framerate Drops - Windows & Mac* (7 March 2025).
Riot Games Support — *League of Legends Logs* (2 June 2026).