Separate route settings from network faults

Routing changes the path, not the bandwidth of your local connection. Test the original network before comparing a different route.

Using settings to diagnose a connection

Start with automatic selection

Use the client’s automatic choice as a starting point, then compare the same website before and after connecting.

Choose a region for a reason

Check the destination service’s regional rules first. A different exit location does not guarantee access rights.

Confirm more than the status button

A connected status is only the first check. Open the sites you need and confirm that they load and work correctly.

Read each privacy scope separately

Visits to this website and traffic through the app are different data flows. Consult official app privacy documentation.

Bring useful details to support

Record system and client versions, the time of failure and the error text. Hide account, payment and private information.

Keep gaming measurements separate

Record latency, packet loss and disconnection times. Visual stutter can also come from device performance. Keep the game server unchanged for a useful route comparison.

Check local latency before cross-region play
Check local latency before cross-region play
Compare peak-hour results under equal conditions
Compare peak-hour results under equal conditions
Watch for packet loss during longer sessions
Watch for packet loss during longer sessions

Checks for calls and web access

Test the destination on the original network before trying one alternate route. Follow workplace data rules for accounts, files and call content.