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 09:45:23 UTC
| Metric | PublicNode | Merkle | MEV Blocker |
|---|---|---|---|
| Rank | 1 | 6 | 7 |
| Score | 99.4 | 70.1 | 69.5 |
| Status | Excellent | Degraded | Degraded |
| Availability | 99.98% | 100.00% | 99.91% |
| p50 latency | 19.4 ms | 105.0 ms | 119.8 ms |
| p95 latency | 32.7 ms | 194.3 ms | 208.7 ms |
| p99 latency | 68.9 ms | 228.8 ms | 226.2 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.60 blocks | 0.42 blocks |
| Rate limited | 0 | 1,451 | 1 |
| Unsupported | 0 | 18 | 0 |
| Samples | 9,397 | 2,130 | 9,301 |
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
+29.3points
- Latency+29.2
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +29.3, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+29.9points
- Latency+30.0
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +29.9, exactly — the score is a weighted sum, so it comes apart.