A subscription lets a client retrieve multiple node entries from one URL. It can be refreshed manually or, in some clients, on a schedule. A successful update means the list was retrieved and parsed, not that every node is reachable. If an update fails, determine whether the request timed out or returned a response that contained no parseable entries.
A node is a remote connection profile in the client, typically containing an address, port, protocol, authentication details, and transport settings. The name in the list is just a label; entries with the same name may point to different addresses or ports. Before comparing connection results, confirm that you selected the same profile, not just one with the same name.
TCPing attempts to establish a TCP connection to a specified address and port, and records how long it takes. A successful test confirms that a TCP connection could be established at that moment; it does not verify proxy credentials or prove that a destination website will load. This test alone cannot determine whether a connection using UDP is working properly.
Real connection latency measures a request sent through a specified node to a test destination. Results depend on the protocol handshake, test destination, and timing method. It checks more of the connection than a port-only test, but it is not a download speed test and does not mean every website is reachable. For node comparisons, use the same test destination and network conditions where possible.