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.
Building this for production?
We turn this architecture into tested, non-custodial software with monitoring, documentation and deployment support.
Related technical guides
TON Contract Security Pitfalls: Bounces, Replay, Gas Griefing
TON smart contract security pitfalls that EVM-trained reviewers miss: unhandled bounces, message replay, and gas griefing explained.
Read articleEVM Audit Checklist: What Foundry and Slither Actually Test
An EVM smart contract audit checklist: what Foundry fuzzing and Slither actually catch, and where manual review still has to close the gap.
Read articleHow to Choose a Smart Contract Auditor: A Vetting Checklist
A concrete vetting checklist for how to choose a smart contract auditor: past reports, tooling stack, manual-review ratio, and remediation terms.
Read article