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 12:27:09 UTC
| Metric | NodeReal | Merkle | MEV Blocker |
|---|---|---|---|
| Rank | 4 | 6 | 7 |
| Score | 82.5 | 70.0 | 69.5 |
| Status | Good | Degraded | Degraded |
| Availability | 100.00% | 100.00% | 99.93% |
| p50 latency | 87.8 ms | 106.8 ms | 122.8 ms |
| p95 latency | 99.8 ms | 202.1 ms | 212.2 ms |
| p99 latency | 123.1 ms | 231.3 ms | 234.0 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.34 blocks | 0.50 blocks | 0.40 blocks |
| Rate limited | 0 | 1,428 | 1 |
| Unsupported | 0 | 17 | 0 |
| Samples | 8,678 | 2,092 | 8,817 |
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
+12.6points
- Latency+12.4
- Head freshness+0.2
- Availability+0.0
- Correctness+0.0
The parts add to +12.6, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsMEV Blocker
+13.0points
- Latency+12.9
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +13.0, exactly — the score is a weighted sum, so it comes apart.