Providers
Compare RPC providers on measured data
The top 4 on the chosen chain are compared by default. Pick your own — up to 4 — and the selection moves into the URL, so a comparison can be sent to someone else and they will see exactly what you saw.
Providers on Ethereum
- Tenderly
- PublicNode
- dRPC
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-27 14:59:29 UTC
| Metric | PublicNode | dRPC | 1RPC |
|---|---|---|---|
| Rank | 2 | 3 | 9 |
| Score | 95.5 | 88.1 | 0.0 |
| Status | Excellent | Good | Poor |
| Availability | 99.98% | 99.95% | 0.00% |
| p50 latency | 24.7 ms | 34.2 ms | 0.0 ms |
| p95 latency | 49.0 ms | 74.2 ms | 0.0 ms |
| p99 latency | 117.2 ms | 183.6 ms | 0.0 ms |
| Correctness | 99.99% | 100.00% | not measured |
| Head lag | 0.49 blocks | 0.36 blocks | no cohort |
| Rate limited | 0 | 40 | 1,672 |
| Unsupported | 0 | 0 | 0 |
| Samples | 9,794 | 9,547 | 1,917 |
9 providers scored against each other.
Where the gap comes from
Two scores side by side say one is higher. This says why: the score is a weighted sum, so it comes apart, and each component’s share of the difference adds back to the difference exactly. Compared against PublicNode, the highest scorer of those selected.
PublicNodevsdRPC
+7.4points
- Latency+7.5
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +7.4, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+95.5points
- Availability+40.0
- Latency*+26.1
- Correctness*+20.0
- Head freshness*+9.4
The parts add to +95.5, exactly — the score is a weighted sum, so it comes apart. Components marked * were measured for only one of the two; the other’s weight is spread across what it does have, which is why the two sides can carry different weights for the same row.