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
30d window · 2.6 days observed · generated 2026-08-27 10:07:35 UTC
| Metric | PublicNode | Merkle | MEV Blocker |
|---|---|---|---|
| Rank | 1 | 6 | 7 |
| Score | 99.4 | 78.6 | 77.8 |
| Status | Excellent | Good | Good |
| Availability | 99.97% | 99.98% | 99.89% |
| p50 latency | 18.4 ms | 106.4 ms | 118.6 ms |
| p95 latency | 33.7 ms | 195.9 ms | 209.3 ms |
| p99 latency | 70.9 ms | 243.0 ms | 232.6 ms |
| Correctness | 99.99% | 100.00% | 99.99% |
| Head lag | 0.49 blocks | 0.48 blocks | 0.40 blocks |
| Rate limited | 0 | 16,006 | 3 |
| Unsupported | 0 | 198 | 0 |
| Samples | 100,340 | 23,038 | 99,400 |
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.8points
- Latency+20.8
- Head freshness−0.0
- Correctness−0.0
- Availability−0.0
The parts add to +20.8, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+21.6points
- Latency+21.7
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +21.6, exactly — the score is a weighted sum, so it comes apart.