"Lag" describes at least four unrelated problems: high latency, jitter, packet loss and low frame rate. They have different causes and different fixes, so the first job is naming which one you have. An in-game network graph, or a ping and trace run while the symptom occurs, will tell you within a minute.
Diagnose in this order
- Device: is frame time stable? A stutter that persists offline is not a network issue.
- Local network: test wired versus wireless, and check whether another device is saturating upload.
- Route: run a continuous ping to the game server and watch for spikes and dropped replies.
- Server: check the platform status page and community reports before changing anything.
Fixes ranked by likelihood
- Move to Ethernet, or to 5 GHz Wi-Fi with a clear channel.
- Pause cloud backups, updates and other downloads during play.
- Select the closest regional server explicitly instead of trusting auto-select.
- Restart the router, then the modem, in that order, and re-test before other changes.
- Ask your provider to check line errors if packet loss appears at the first external hop.
Congestion in the evening with clean results at midday almost always points to the local access network, not to your equipment.
Writing a ticket that gets answered
Support queues reward specificity. Include the exact time and timezone of the incident, your region and selected server, a trace result, your platform and build version, and what you already tested. One paragraph of evidence outranks three paragraphs of frustration, and it usually skips a full round trip of questions.
Frequently asked questions
Rarely by much. It can prioritise your traffic on a congested home network, but it cannot shorten the physical route to the server.
Occasionally, when your provider routes traffic poorly and the VPN offers a better path. More often it adds a hop and makes things worse. Test both ways.
