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 · 3.1 days observed · generated 2026-08-27 22:21:00 UTC
| Metric | PublicNode | Merkle | MEV Blocker |
|---|---|---|---|
| Rank | 1 | 6 | 7 |
| Score | 99.4 | 78.3 | 77.4 |
| Status | Excellent | Good | Good |
| Availability | 99.98% | 99.98% | 99.90% |
| p50 latency | 19.5 ms | 106.9 ms | 119.4 ms |
| p95 latency | 36.0 ms | 195.0 ms | 210.8 ms |
| p99 latency | 78.2 ms | 239.8 ms | 234.2 ms |
| Correctness | 99.99% | 100.00% | 99.99% |
| Head lag | 0.49 blocks | 0.49 blocks | 0.40 blocks |
| Rate limited | 0 | 19,178 | 3 |
| Unsupported | 0 | 233 | 0 |
| Samples | 120,328 | 27,723 | 119,175 |
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
+21.1points
- Latency+21.1
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +21.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+22.0points
- Latency+22.1
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +22.0, exactly — the score is a weighted sum, so it comes apart.