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.3 days observed · generated 2026-08-27 04:37:23 UTC
| Metric | NodeReal | Merkle | MEV Blocker |
|---|---|---|---|
| Rank | 4 | 6 | 7 |
| Score | 88.6 | 78.9 | 78.0 |
| Status | Good | Good | Good |
| Availability | 99.79% | 99.98% | 99.89% |
| p50 latency | 87.3 ms | 106.5 ms | 118.5 ms |
| p95 latency | 99.8 ms | 195.9 ms | 209.3 ms |
| p99 latency | 123.1 ms | 243.2 ms | 233.0 ms |
| Correctness | 99.99% | 100.00% | 99.99% |
| Head lag | 0.35 blocks | 0.46 blocks | 0.40 blocks |
| Rate limited | 0 | 14,586 | 2 |
| Unsupported | 0 | 180 | 0 |
| Samples | 89,128 | 20,969 | 90,497 |
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
+9.7points
- Latency+9.6
- Head freshness+0.1
- Availability−0.1
- Correctness−0.0
The parts add to +9.7, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsMEV Blocker
+10.6points
- Latency+10.6
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +10.6, exactly — the score is a weighted sum, so it comes apart.