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
Side by side
24h window · 24 hours observed · generated 2026-08-27 15:24:47 UTC
| Metric | PublicNode | Merkle | MEV Blocker |
|---|---|---|---|
| Rank | 2 | 6 | 7 |
| Score | 98.5 | 77.9 | 76.8 |
| Status | Excellent | Good | Good |
| Availability | 99.97% | 100.00% | 99.92% |
| p50 latency | 19.8 ms | 107.1 ms | 121.0 ms |
| p95 latency | 38.7 ms | 193.2 ms | 212.0 ms |
| p99 latency | 91.8 ms | 234.1 ms | 235.2 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.49 blocks | 0.40 blocks |
| Rate limited | 0 | 5,988 | 3 |
| Unsupported | 0 | 73 | 0 |
| Samples | 38,254 | 8,653 | 37,863 |
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.
PublicNodevsMerkle
+20.6points
- Latency+20.6
- Availability−0.0
- Head freshness−0.0
- Correctness−0.0
The parts add to +20.6, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+21.7points
- Latency+21.8
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +21.7, exactly — the score is a weighted sum, so it comes apart.