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
7d window · 2.2 days observed · generated 2026-08-27 01:36:32 UTC
| Metric | PublicNode | Merkle | MEV Blocker |
|---|---|---|---|
| Rank | 1 | 6 | 7 |
| Score | 99.4 | 79.2 | 78.2 |
| Status | Excellent | Good | Good |
| Availability | 99.97% | 99.98% | 99.88% |
| p50 latency | 18.3 ms | 106.6 ms | 118.5 ms |
| p95 latency | 33.8 ms | 196.0 ms | 209.4 ms |
| p99 latency | 70.5 ms | 243.1 ms | 233.5 ms |
| Correctness | 99.99% | 100.00% | 99.99% |
| Head lag | 0.49 blocks | 0.47 blocks | 0.40 blocks |
| Rate limited | 0 | 13,816 | 2 |
| Unsupported | 0 | 169 | 0 |
| Samples | 86,433 | 19,886 | 85,634 |
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.2points
- Latency+20.3
- Head freshness−0.0
- Correctness−0.0
- Availability−0.0
The parts add to +20.2, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+21.2points
- Latency+21.2
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +21.2, exactly — the score is a weighted sum, so it comes apart.