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
6h window · 6.0 hours observed · generated 2026-08-27 23:00:12 UTC
| Metric | PublicNode | Merkle | MEV Blocker |
|---|---|---|---|
| Rank | 2 | 6 | 7 |
| Score | 96.0 | 71.0 | 69.5 |
| Status | Excellent | Degraded | Degraded |
| Availability | 100.00% | 100.00% | 99.94% |
| p50 latency | 23.2 ms | 107.8 ms | 123.7 ms |
| p95 latency | 44.7 ms | 187.6 ms | 216.3 ms |
| p99 latency | 101.9 ms | 236.0 ms | 239.2 ms |
| Correctness | 100.00% | 100.00% | 99.98% |
| Head lag | 0.47 blocks | 0.52 blocks | 0.40 blocks |
| Rate limited | 0 | 1,287 | 0 |
| Unsupported | 0 | 12 | 0 |
| Samples | 8,183 | 1,933 | 8,100 |
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
+24.9points
- Latency+24.9
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +24.9, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+26.5points
- Latency+26.5
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +26.5, exactly — the score is a weighted sum, so it comes apart.