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 01:53:32 UTC
| Metric | NodeReal | Merkle | MEV Blocker |
|---|---|---|---|
| Rank | 4 | 6 | 7 |
| Score | 86.2 | 77.6 | 76.7 |
| Status | Good | Good | Good |
| Availability | 99.99% | 100.00% | 99.97% |
| p50 latency | 87.0 ms | 105.9 ms | 118.4 ms |
| p95 latency | 99.3 ms | 193.5 ms | 210.2 ms |
| p99 latency | 122.1 ms | 220.4 ms | 231.8 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.33 blocks | 0.51 blocks | 0.40 blocks |
| Rate limited | 0 | 1,481 | 2 |
| Unsupported | 0 | 18 | 0 |
| Samples | 9,380 | 2,128 | 9,517 |
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
+8.5points
- Latency+8.3
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +8.5, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsMEV Blocker
+9.5points
- Latency+9.4
- Head freshness+0.1
- Availability+0.0
- Correctness−0.0
The parts add to +9.5, exactly — the score is a weighted sum, so it comes apart.