Three readings, three different problems
EA defines ping as the round-trip time between a device and the game server. Jitter is the variation in that time from one packet to the next. Packet loss is the percentage of data that never completes the journey.
High ping causes a delayed but potentially consistent response. High jitter alternates normal moments with hitches because data arrives out of rhythm. Packet loss can remove position or input updates and force corrections, appearing as teleporting, speed-up lag or disconnections.

What to test, and in which order
Enable the game's network statistics where available and record ping, jitter and loss during the fault. Ping and jitter are usually measured in milliseconds, while loss is a percentage. Compare them with a good session using the same server region.
Change one variable at a time. Pause downloads and cloud backups, then play again. Next, keeping everything else the same, try Ethernet. A repeatable improvement over cable points towards the Wi-Fi connection, but does not identify coverage, interference or an adapter as the cause. If you need Wi-Fi, test closer to the router and compare bands in the room where you play.
If the fault persists over Ethernet, compare several games and times of day. Note whether it affects one server or multiple services. Cloudflare measures idle and loaded latency, jitter and loss. That complements in-game statistics, but tests another network route and cannot establish how the game server is performing.

When the game settings are not the fix
Lowering graphics does not repair missing packets because it changes GPU work, not the network route. Do not buy a router before testing Ethernet and another device either. If both fail at the same time, keep screenshots of the test and contact the provider.
Input lag also includes controller, engine and display delay, while SBMM may widen its search depending on mode and population. Separating them prevents attempts to repair the network from a graphics menu.
A useful ping target depends on the game. Turn-based play tolerates delays that seriously disrupt a fighting game. If latency repeatedly rises when a download starts, traffic queues may be contributing. Pause it and repeat the test to check that relationship without assuming every hitch has the same cause.
When contacting an internet provider, record the date, time, wired test, loss and loaded latency across several days. One speed test only proves how quickly data moved at that moment. A repeatable series helps separate a home fault from evening congestion or a particular route used by the provider.
The conversation starts here
Sign in with a supporter account to comment. Sign in




Nobody has commented yet. Want to go first?