Start with the account's League region, then separate platform services, the live match route, local FPS, and game-server processing. A responsive client does not prove a low match ping, and a teamfight frame drop is not automatically packet loss.
Identify the layer first
- Lobby is fine, match ping is high: focus on the game-server route.
- Every measured direction slows down: check Wi-Fi, uploads, and the ISP path.
- Rubber-banding with a ping spike: investigate network variation.
- FPS falls while ping stays stable: investigate the device and graphics load.
Test the region your account actually uses
A League account remains associated with a specific game region. The League of Legends ping test compares supported regional directions; it cannot transfer an account or bypass Riot's region rules. Unsupported targets are left unmeasured instead of being represented by an unrelated city.
Run a regional test and one low-risk match in the same time window. Compare PartyPing's median and P10–P90 range with match ping and FPS. Several directions worsening together points toward a shared local or ISP problem; only the League match worsening calls for more match samples and service-status evidence.
Separate teamfight network lag from FPS loss
Rubber-banding or delayed commands accompanied by a ping spike suggests the network. A slideshow-like picture with stable ping suggests client frame time. PartyPing cannot measure client FPS or the CPU load of a particular game server.
Riot has described below roughly 15 ms as ideal and around 60 ms as still very playable, but these are reference points, not PartyPing's complete 20/40/70/120 ms engineering scale.
Sources
Sources reviewed: 2026-09-16.