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
1h window · 60 minutes observed · generated 2026-08-27 20:22:21 UTC
| Metric | PublicNode | NodeReal | Merkle |
|---|---|---|---|
| Rank | 2 | 4 | 6 |
| Score | 93.2 | 82.9 | 71.4 |
| Status | Excellent | Good | Degraded |
| Availability | 100.00% | 100.00% | 100.00% |
| p50 latency | 25.4 ms | 87.0 ms | 108.7 ms |
| p95 latency | 56.0 ms | 98.9 ms | 181.6 ms |
| p99 latency | 127.1 ms | 123.7 ms | 194.9 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.34 blocks | 0.65 blocks |
| Rate limited | 0 | 0 | 278 |
| Unsupported | 0 | 0 | 2 |
| Samples | 1,619 | 1,567 | 400 |
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 PublicNode, the highest scorer of those selected.
PublicNodevsNodeReal
+10.3points
- Latency+10.5
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +10.3, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+21.8points
- Latency+21.6
- Head freshness+0.2
- Availability+0.0
- Correctness+0.0
The parts add to +21.8, exactly — the score is a weighted sum, so it comes apart.