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-28 04:31:44 UTC
| Metric | NodeReal | Merkle | 1RPC |
|---|---|---|---|
| Rank | 4 | 6 | 8 |
| Score | 85.8 | 77.6 | 60.3 |
| Status | Good | Good | Degraded |
| Availability | 99.62% | 100.00% | 79.94% |
| p50 latency | 87.6 ms | 105.3 ms | 1326.0 ms |
| p95 latency | 98.8 ms | 198.1 ms | 7406.7 ms |
| p99 latency | 113.5 ms | 278.7 ms | 9776.0 ms |
| Correctness | 100.00% | 100.00% | 96.96% |
| Head lag | 0.35 blocks | 0.49 blocks | 0.94 blocks |
| Rate limited | 0 | 1,460 | 1,506 |
| Unsupported | 0 | 20 | 0 |
| Samples | 8,795 | 2,097 | 2,073 |
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.1points
- Latency+8.1
- Head freshness+0.2
- Availability−0.2
- Correctness+0.0
The parts add to +8.1, exactly — the score is a weighted sum, so it comes apart.
NodeRealvs1RPC
+25.5points
- Latency+16.3
- Availability+7.9
- Head freshness+0.7
- Correctness+0.6
The parts add to +25.5, exactly — the score is a weighted sum, so it comes apart.