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
- dRPC
- NodeReal
- Blast API
- Tenderly
- Merkle
- MEV Blocker
- 1RPC
- Cloudflare
Side by side
7d window · 42 hours observed · generated 2026-08-26 14:54:06 UTC
| Metric | PublicNode | dRPC | Merkle | MEV Blocker |
|---|---|---|---|---|
| Rank | 1 | 2 | 6 | 7 |
| Score | 99.4 | 93.5 | 78.4 | 77.6 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 99.98% | 99.94% | 99.97% | 99.87% |
| p50 latency | 18.3 ms | 33.8 ms | 106.4 ms | 118.0 ms |
| p95 latency | 32.0 ms | 71.9 ms | 196.9 ms | 208.6 ms |
| p99 latency | 67.9 ms | 166.1 ms | 245.5 ms | 233.1 ms |
| Correctness | 99.98% | 99.99% | 100.00% | 99.98% |
| Head lag | 0.49 blocks | 0.35 blocks | 0.47 blocks | 0.40 blocks |
| Rate limited | 0 | 493 | 11,094 | 0 |
| Unsupported | 0 | 0 | 137 | 0 |
| Samples | 68,939 | 67,302 | 15,991 | 68,309 |
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
+5.9points
- Latency+6.0
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +5.9, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+21.0points
- Latency+21.0
- Head freshness−0.0
- Correctness−0.0
- Availability+0.0
The parts add to +21.0, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+21.8points
- Latency+21.9
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +21.8, exactly — the score is a weighted sum, so it comes apart.