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
24h window · 24 hours observed · generated 2026-08-26 11:51:51 UTC
| Metric | NodeReal | Merkle | MEV Blocker |
|---|---|---|---|
| Rank | 3 | 6 | 7 |
| Score | 88.5 | 78.3 | 77.4 |
| Status | Good | Good | Good |
| Availability | 99.98% | 99.95% | 99.85% |
| p50 latency | 87.7 ms | 106.5 ms | 118.7 ms |
| p95 latency | 100.0 ms | 196.9 ms | 209.9 ms |
| p99 latency | 124.9 ms | 243.0 ms | 235.4 ms |
| Correctness | 99.98% | 100.00% | 99.98% |
| Head lag | 0.36 blocks | 0.47 blocks | 0.39 blocks |
| Rate limited | 0 | 6,234 | 0 |
| Unsupported | 0 | 79 | 0 |
| Samples | 38,056 | 9,056 | 38,591 |
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 NodeReal, the highest scorer of those selected.
NodeRealvsMerkle
+10.2points
- Latency+10.0
- Head freshness+0.1
- Availability+0.0
- Correctness−0.0
The parts add to +10.2, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsMEV Blocker
+11.1points
- Latency+11.0
- Availability+0.1
- Head freshness+0.0
- Correctness+0.0
The parts add to +11.1, exactly — the score is a weighted sum, so it comes apart.