Solana RPC Latency Checker
Test the latency of any Solana RPC endpoint from your browser. Enter an endpoint URL to measure response times for common RPC methods.
How it works
The checker sends a series of RPC calls and measures round-trip time:
| Method | What it tests |
|---|---|
getHealth | Basic endpoint availability |
getSlot | Minimal read latency |
getBalance | Account read latency |
getRecentBlockhash | Block data latency |
simulateTransaction | Compute-heavy request latency |
Each method is called multiple times. The tool reports min, median, p95, and max latency.
Interpreting results
| Latency (median) | Rating | Suitable for |
|---|---|---|
| < 50ms | Excellent | Trading bots, MEV |
| 50–150ms | Good | dApps, general use |
| 150–500ms | Acceptable | Development, testing |
| > 500ms | Poor | Consider switching providers |
Factors affecting latency
Geographic distance: Latency is primarily determined by the physical distance between your application and the RPC node. A node in the same region as your server gives the best results.
Network path: Internet routing between your location and the RPC node affects latency. Direct peering is faster than traversing multiple networks.
Server load: Shared RPC nodes may have variable latency depending on other customers’ traffic. Dedicated nodes provide more consistent results.
Method complexity: Simple methods (getSlot) are faster than complex ones (getProgramAccounts). The checker tests a range to show the full picture.
Testing tips
- Test from your server, not your laptop — your application’s latency matters more than your local latency.
- Test at different times — latency can vary with network load throughout the day.
- Compare multiple providers — run the same test against several endpoints to find the best option for your region.
- Test under load — single-request latency may differ from latency under sustained traffic.
FAQ
Why is my latency different from the provider’s claimed latency? Providers measure latency from their network to the Solana cluster. Your latency includes the round trip from your location to the provider and back. Geographic distance is the main factor.
Does this tool send my RPC URL anywhere? No. All requests are made directly from your browser to the RPC endpoint. The URL is not sent to any server.
Can I test WebSocket latency? This tool tests HTTP RPC latency. WebSocket latency depends on connection establishment time and subscription delivery speed, which requires a different testing approach.
Data powered by Supanode RPC
Updated: