Skip to content

Candidate Diagnostics

Candidate Diagnostics shows which returned Nodes are currently eligible and how they are ranked for a selected Pool. Use it when a Pool has no available Node, a Node is unexpectedly ineligible, or a new connection uses an unexpected exit IP.

The tool is read-only. It does not select, reserve, force, or move a Node, and it does not change Pool membership or routing.

Review a Pool

  1. Open Observability and select Candidate Diagnostics.
  2. Select a Gateway. Decommissioned Gateways are not offered.
  3. Select a Pool associated with that Gateway. If the system-managed pool-all Pool exists, MyOwnProxy selects it initially; you can instead select a customer-created Pool.
  4. Review the eligible and excluded counts and the generated candidate rows.
  5. Review each returned Node's ID, exit IP when available, eligibility, final score, state, dataplane status, network score, and information age.

The header shows when the result was generated, when that snapshot expires, and its displayed TTL. These values describe the candidate snapshot and reevaluation guidance. TTL expiry does not guarantee selection of a different Node or a different exit IP.

Interpret the candidate rows

The table summarizes each returned Node's eligibility, final score, current state and dataplane status, network score, information age, and exit IP when available.

The first eligible row is the highest-ranked, currently preferred candidate in that generated snapshot. It is not a record of which Node an existing connection is using. Existing connections can continue through a previously selected Node, and the diagnostics result does not make or force a new selection.

Eligibility is evaluated before ranking. A strong network score cannot make a Node eligible when its lifecycle state, dataplane result, health-information age, Gateway assignment, or Pool membership prevents selection.

Among eligible Nodes, network quality is the principal current ranking input. Eligibility and ranking rules can affect the result, so the highest displayed network score is not an unconditional selection guarantee. Treat the displayed final score as a relative explanation of this snapshot, not a permanent selection contract.

Use the displayed state, dataplane status, network score, and information age when investigating an ineligible returned Node. A Node that is absent from the table may not belong to the selected Pool or Gateway, or may be outside the current candidate set. Verify its Pool membership and Gateway assignment in that case.

Investigate unexpected selection

  1. Confirm that the selected Gateway and Pool match the application's connection details.
  2. Compare the observed exit IP with the candidate rows and current Node information.
  3. Review whether the expected Node is present and eligible.
  4. Review its displayed state, dataplane status, network score, and information age.
  5. Check the Node and Gateway in Health Explorer.
  6. Open a new connection and follow Verifying Connection.

Repeated new connections can use the same Node, and an existing connection does not move merely because the candidate snapshot changes. See Unexpected Exit IP or Node Selection for troubleshooting, manage membership through Managing Proxies and Pool Nodes, and see Understanding Proxies and Pools for the selection model.