RPC Benchmark Percentiles Explained: p50, p95 and p99
Why averages hide the latency spikes that break trading bots, wallets and production blockchain applications.
Why averages hide the latency spikes that break trading bots, wallets and production blockchain applications.
Median
p50 describes the typical request but says little about congestion and provider degradation.
Tail latency
p95 and p99 reveal slow requests that trigger stale quotes, expired blockhashes and retry storms.
Sample design
Use enough samples across multiple time windows. Separate warm and cold connections and avoid coordinated benchmark bursts.
Decision making
Set application service-level objectives from tolerated tail latency and error rate, not a marketing average.
TierZero provides infrastructure engineering and 24/7 bot maintenance.
Need a bot like this built?
We design, build and run trading bots on Solana, Hyperliquid and Polymarket.
Start a projectMore from the blog
Public vs Paid RPC: How to Run a Fair Benchmark
A fair comparison of public and paid RPC endpoints must account for quotas, workload, freshness and support guarantees.
Read articleHyperliquid REST vs WebSocket Benchmark: What to Measure
A benchmark plan for Hyperliquid market data that separates request latency from streaming freshness and recovery.
Read articleHow to Benchmark Polymarket Gamma, Data and CLOB APIs
A reproducible way to compare Polymarket discovery, account-data and order-book API behavior.
Read article