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.5 days observed · generated 2026-08-27 08:28:01 UTC
| Metric | NodeReal | Merkle | 1RPC |
|---|---|---|---|
| Rank | 4 | 6 | 8 |
| Score | 88.1 | 78.7 | 62.5 |
| Status | Good | Good | Degraded |
| Availability | 99.81% | 99.98% | 85.27% |
| p50 latency | 87.4 ms | 106.4 ms | 225.7 ms |
| p95 latency | 100.1 ms | 195.7 ms | 4391.3 ms |
| p99 latency | 125.9 ms | 243.2 ms | 7602.5 ms |
| Correctness | 99.99% | 100.00% | 97.48% |
| Head lag | 0.35 blocks | 0.48 blocks | 0.91 blocks |
| Rate limited | 0 | 15,587 | 16,625 |
| Unsupported | 0 | 189 | 0 |
| Samples | 95,268 | 22,400 | 20,453 |
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.4points
- Latency+9.3
- Head freshness+0.2
- Availability−0.1
- Correctness−0.0
The parts add to +9.4, exactly — the score is a weighted sum, so it comes apart.
NodeRealvs1RPC
+25.5points
- Latency+18.6
- Availability+5.8
- Head freshness+0.7
- Correctness+0.5
The parts add to +25.5, exactly — the score is a weighted sum, so it comes apart.