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
- PublicNode
- Tenderly
- dRPC
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- 1RPC
- Cloudflare
Side by side
24h window · 24 hours observed · generated 2026-08-26 22:13:47 UTC
| Metric | PublicNode | dRPC | Merkle | MEV Blocker |
|---|---|---|---|---|
| Rank | 1 | 3 | 6 | 7 |
| Score | 99.4 | 91.4 | 78.0 | 77.2 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 99.98% | 99.93% | 100.00% | 99.87% |
| p50 latency | 18.7 ms | 34.1 ms | 107.1 ms | 119.1 ms |
| p95 latency | 34.7 ms | 68.4 ms | 196.8 ms | 210.6 ms |
| p99 latency | 72.1 ms | 168.0 ms | 241.2 ms | 232.9 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 99.99% |
| Head lag | 0.49 blocks | 0.37 blocks | 0.46 blocks | 0.39 blocks |
| Rate limited | 0 | 120 | 6,059 | 0 |
| Unsupported | 0 | 0 | 79 | 0 |
| Samples | 37,938 | 37,039 | 8,748 | 37,564 |
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
+8.0points
- Latency+8.1
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.0, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+21.4points
- Latency+21.4
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +21.4, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+22.2points
- Latency+22.3
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +22.2, exactly — the score is a weighted sum, so it comes apart.