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 20:21:57 UTC
| Metric | PublicNode | NodeReal | Merkle |
|---|---|---|---|
| Rank | 2 | 4 | 6 |
| Score | 94.4 | 83.0 | 70.7 |
| Status | Excellent | Good | Degraded |
| Availability | 100.00% | 100.00% | 100.00% |
| p50 latency | 25.4 ms | 87.2 ms | 110.5 ms |
| p95 latency | 52.3 ms | 99.1 ms | 192.2 ms |
| p99 latency | 114.7 ms | 123.9 ms | 236.0 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.33 blocks | 0.60 blocks |
| Rate limited | 0 | 0 | 1,401 |
| Unsupported | 0 | 0 | 18 |
| Samples | 8,778 | 8,538 | 2,067 |
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
+11.4points
- Latency+11.6
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +11.4, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+23.7points
- Latency+23.6
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +23.7, exactly — the score is a weighted sum, so it comes apart.