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
30d window · 2.2 days observed · generated 2026-08-27 01:55:51 UTC
| Metric | NodeReal | Merkle | 1RPC |
|---|---|---|---|
| Rank | 4 | 6 | 8 |
| Score | 89.1 | 79.2 | 62.6 |
| Status | Good | Good | Degraded |
| Availability | 99.78% | 99.98% | 85.50% |
| p50 latency | 87.4 ms | 106.6 ms | 225.7 ms |
| p95 latency | 99.9 ms | 195.9 ms | 4391.3 ms |
| p99 latency | 123.6 ms | 243.1 ms | 7602.5 ms |
| Correctness | 99.99% | 100.00% | 97.48% |
| Head lag | 0.35 blocks | 0.46 blocks | 0.91 blocks |
| Rate limited | 0 | 13,904 | 14,801 |
| Unsupported | 0 | 170 | 0 |
| Samples | 84,833 | 20,017 | 18,363 |
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.9points
- Latency+9.9
- Head freshness+0.1
- Availability−0.1
- Correctness−0.0
The parts add to +9.9, exactly — the score is a weighted sum, so it comes apart.
NodeRealvs1RPC
+26.4points
- Latency+19.6
- Availability+5.7
- Head freshness+0.7
- Correctness+0.5
The parts add to +26.4, exactly — the score is a weighted sum, so it comes apart.