A cloud-gaming change can alter the provider, membership tier, client device, display target, controller, network path, or streaming settings. Keep evidence from the actual service and location so a later performance complaint can be compared with a known baseline instead of a generic speed-test result.
Capture the old configuration
Record the provider, membership tier, game, client version, device model, operating system, controller connection, display resolution and refresh rate, streaming resolution, frame-rate target, server region, and whether Ethernet, Wi-Fi, a VPN, or a mobile connection was used. Note which account owns the game or subscription without storing passwords, recovery codes, or payment details.
Take a dated compatibility snapshot from the provider's requirements page. NVIDIA's GeForce NOW system requirements lists different hardware and bandwidth requirements by platform and stream target. As of October 21, 2026, its Windows guidance lists 15 Mbps for HD at up to 60 FPS and 25 Mbps for full HD at 60 FPS, recommends Ethernet or 5 GHz Wi-Fi, and requires latency below 80 ms to an NVIDIA data center. Provider requirements change, so preserve the date and exact service rather than treating these numbers as universal cloud-gaming thresholds.
Save provider-specific network evidence
Run the service's own network test before and after the change, ideally at the same location and time window. NVIDIA's network-test guidance says its built-in test measures the path to its data centers and reports bandwidth, packet loss, jitter, and ping. It warns that a generic speed test may measure a different server and therefore may not represent the cloud-gaming path. Save the result screen or transcribe the metrics, server region, timestamp, and any warnings.
Add a short real-session sample. Record launch time, disconnects, visible resolution drops, audio breakup, input delay observations, and whether the issue affected one game or several. Avoid claiming a precise latency unless the tool measured it. A subjective note such as 'controller response felt delayed' should remain labeled as an observation.
Check continuity and cost separately
Confirm that the required games, saves, entitlements, family settings, and controllers are available on the new setup. Record any membership feature that changes the supported resolution, frame rate, queue, or session duration. Save the current plan name, renewal date, and cancellation or downgrade path, but exclude account credentials and full payment data.
Define rollback and the decision rule
Write down the old client and settings, the change owner, the reason for the change, and the threshold for rolling back. Compare like with like: same game, device, network location, and approximate time. Keep at least one acceptable baseline and one failed or degraded example. The change is complete only when the provider test and real session both support the decision and the previous configuration can still be restored if needed.
Sources
- GeForce NOW System Requirements — NVIDIA
- How do I test my network for GeForce NOW? — NVIDIA, Oct. 5, 2026