Verify a Solana node’s advertised contact information

After an IP change, a running process may advertise a stale contact address. A peer’s cluster-node inventory shows what other participants currently know about the node.

Match by node identity

Read getIdentity on the moved backend, then issue the request below to a separate node on the same cluster. Find the row whose pubkey equals the backend’s identity. Compare its gossip and TPU endpoints with the intended public configuration.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "getClusterNodes",
  "params": []
}

Distinguish advertised addresses from reachability

If the peer still lists the previous IP, query a second observer and record both observation times. A stale row at only one peer suggests propagation or local visibility deserves another check. A shared stale address points you back to the node’s advertised configuration.

A null RPC field simply means that this record carries no advertised RPC address. For a service intended to be public, verify its configured client-facing URL independently. An entry in gossip alone cannot establish that a firewall accepts traffic.

Documentation