Skip to content

Unexpected Exit IP or Node Selection

Use this page when a Pool connection uses an unexpected exit IP or when traffic appears to use a different Node than expected.

Checks

  1. Confirm whether the application uses a Pool endpoint or a Node's selected method under Connection Methods for Direct Node access.
  2. Close the test connection and open a new one. An existing connection remains on its selected Node.
  3. For a Pool, select the matching Gateway and Pool in Candidate Diagnostics. Review whether the expected Node is present and eligible.
  4. Compare the observed exit IP with the Pool's Current Node information. Remember that Recommended is a current preference, not evidence that traffic is already using that Node.
  5. For Direct Node access, confirm that the displayed connection method belongs to the intended Node and compare the result with that Node's last reported public IP.
  6. If the Node was reassigned or replaced, recopy the selected method's complete current value and recheck Pool membership.
  7. An ADMIN can run the live test in Proxy details to review the Pool endpoint's current exit IP and latency when available. A VIEWER can perform the other read-only checks but cannot run this test.

What the result means

  • A new Pool connection uses the Pool's Current Node. The Pool does not promise a fixed exit IP across later reevaluations.
  • The first eligible row in Candidate Diagnostics is Recommended for that snapshot. If the UI also identifies it as Current, new connections use that Node; established connections may still remain on the Node they already use.
  • Opening several new connections does not guarantee a different Node each time.
  • Expiry of the Active node rotation interval causes reevaluation; it does not guarantee rotation to another Node or exit IP.
  • Direct Node access should use the selected Node and therefore show that Node's current public exit IP. A mismatch can indicate stale connection values, an outdated connection, or a Node/network issue.
  • After reassigning or replacing a Node, its connection methods can change. Always recopy the selected method's complete current value rather than preserving part of an old one.

Supported recovery

For a Pool, have an ADMIN correct unintended membership or restore an expected Node to eligible health. Allow approximately 30 seconds for membership changes, then open a new connection. If a fixed Node is required, use its current displayed connection method with a persistent credential as described in Connecting through a Specific Node.

Contact Support

Contact MyOwnProxy Support when a new direct connection consistently shows an exit IP that does not match the selected Node, or when Pool behavior remains unexplained after reviewing health, membership, and Candidate Diagnostics. Include the observed IP and the information in Contacting Support.