How network directories test RPC latency: Reading the result
An EVM network directory helps you choose an RPC endpoint by timing how quickly your browser gets the latest block and showing how current that block is. On Chainlist, those results help you compare the URL behind a slow MetaMask wallet with other URLs for the same network. Each test is a small JSON-RPC request from your browser, so you need no account or separate test server.
- You get a reply time in milliseconds and a block height for each responding endpoint.
- To choose an endpoint, compare both figures for URLs on the same network.
A fast reply can still come from an outdated node
A fast reply measures one round trip. Say you picked an RPC endpoint showing 40 ms, but your wallet still shows an old balance. Your browser sent a request, received a response, and recorded the elapsed time; the figure says little about what happens when your wallet sends many requests.
The returned block height tells you whether the endpoint has caught up. The JSON-RPC method eth_blockNumber asks for the latest block number. Chainlist’s browser test currently requests the latest block with eth_getBlockByNumber and reads its number from the response. Either way, compare the height with the highest one other endpoints return for that network.
A lagging endpoint can serve stale balances. An endpoint several blocks behind may reply faster than one at the highest height, yet give your wallet older chain data. Blocks keep arriving, so compare heights measured at roughly the same time. A few extra milliseconds matter less than a height that stays behind.
The latency figure also belongs to your location and that moment. Distance to the server, your internet route, and server load affect the time, so another user may see a different order. The page’s light request is a snapshot. Public endpoints can rate-limit the repeated balance, token, and transaction requests a wallet makes even when they answered that request quickly.
Take an illustrative choice: URL A replies in 40 ms but stays three blocks behind; URL B replies in 65 ms at the highest height. Switching MetaMask from A to B changes the server answering the wallet. The network, chain ID, wallet address, and funds stay the same; B can provide fresher data because it has caught up. Choose a low-latency endpoint at the top height, then reload the test later to see whether it remains current.
Related questions about RPC results
What is a good RPC latency?
A good RPC latency is low relative to current endpoints tested from your browser. Compare milliseconds on the same network, then favour a current height and repeatable responses over a tiny timing lead.
Why is my RPC endpoint not responding?
An RPC endpoint may be down, overloaded, rate-limiting requests, or unavailable to browser requests. Reload the directory and compare other URLs. If one remains blank while others return current heights, use a responding URL.
Putting the results into practice
Can I change the RPC of a network already saved in MetaMask?
Yes. Open Manage networks in MetaMask, edit the saved network, add an RPC URL, and select it as the default. The chain ID and wallet address stay the same; the server MetaMask asks changes.
Are paid RPC providers faster than public endpoints?
Paid providers may offer higher request quotas or steadier service under load. Distance and server load still affect reply time. Compare their latency and height from your location, then judge them during normal wallet use.
What does the privacy label next to an RPC mean?
A privacy or tracking label describes the endpoint’s stated handling of request data. It is separate from speed and block height. Read its details and the operator’s policy before using that server for wallet requests.
How do I run my own RPC node?
Running a node means installing client software for your network, obtaining blockchain data, keeping it synced, and giving your wallet its RPC URL. You control that endpoint and take responsibility for its storage, bandwidth, updates, and uptime.