Use the default as a baseline
If the client offers a suggested route, keep it for the initial check. Save that result before deciding whether a manual change is needed.
Capture the conditions of a failure first. Keep the destination and local network fixed before trying another route, so the comparison remains useful.
If the client offers a suggested route, keep it for the initial check. Save that result before deciding whether a manual change is needed.
Review the destination’s account and location requirements before choosing an exit region. Moving the exit does not grant extra account rights.
After the client reports a connection, complete a real task such as loading a webpage or joining a call. A status marker alone is insufficient.
Note the test time, access method and destination. Similar conditions make a before-and-after comparison more useful than unrelated results.
Give support error codes and versions, not passwords or private material from full logs. Check attachments for account and payment information.
Frame rate reflects hardware and game load, while latency and loss describe network conditions. Keep records for the same server instead of using one metric to explain every symptom.



Capture conditions and symptoms. Substitute a non-sensitive test for work material and inspect support attachments for account and payment details.
| Field | Details to retain |
|---|---|
| Test conditions | Date and time, access method, system and app versions |
| Baseline result | Loading, latency and errors with the route inactive |
| Route result | Selected region, the same destination and test duration |
| Next decision | Reproducibility, the single changed setting and support needs |