Direct answer
Use the targets as a starting point, not a verdict
Download
10 Mbps
Per active traditional gameplay session
Upload
3 Mbps
Add voice, streaming, and other uploads
Ping
≤ 50 ms
Editorial planning target to the probe
Jitter
≤ 15 ms
Editorial variation target
Inspect the immutable 2026.07.24 JSON release or use the human-readable evidence table.
Controlled protocol
Test the condition that actually causes lag
- 1. Record the game context. Note title, platform, server region, connection type, match time, and the in-game latency or loss indicator.
- 2. Run two or three quiet trials. Keep the device and endpoint fixed; save the median, range, loaded latency, unsuccessful probes, and confidence.
- 3. Recreate normal load. Repeat while the household stream, backup, update, or upload that coincides with lag is active.
- 4. Compare Ethernet and Wi-Fi. Change only the local connection where practical. This separates radio effects from the wider internet path.
- 5. Confirm inside the game.The browser probe and game server are different destinations. The game's status page and telemetry are the final check for its path.
Pattern diagnosis
What the paired results suggest
Quiet is stable; load raises latency
A competing transfer or queue is affecting responsiveness. Pause it to confirm, then evaluate scheduling or supported queue management.
Ethernet is stable; Wi-Fi is not
Investigate signal, interference, placement, band, client drivers, and access-point load before changing the internet plan.
Browser is stable; one game is not
Check that game's region, status, matchmaking, and route. A generic test cannot certify a publisher endpoint.
Every device and wired test degrades
Save several time-stamped results, compare with the provider label and status, and escalate with reproducible evidence.
Match the workload
Traditional play, downloads, and remote video need different tests
- Traditional online match: prioritize stable latency and enough capacity for the game plus concurrent traffic.
- Patch or install: throughput and data use dominate; this can saturate the link and raise latency for an active match.
- Cloud gaming or Remote Play:add a continuous video stream and use that service's current requirements. PlayStation publishes separate Remote Play connection guidance; do not apply those figures to every game.
- Broadcasting gameplay:add the streaming service's upload bitrate and headroom separately from the gameplay row.
For safe router and NAT troubleshooting, continue to the gaming optimization workflow.