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:26:47 UTC
| Metric | PublicNode | NodeReal | Merkle |
|---|---|---|---|
| Rank | 1 | 4 | 6 |
| Score | 99.4 | 88.1 | 78.7 |
| Status | Excellent | Good | Good |
| Availability | 99.97% | 99.81% | 99.98% |
| p50 latency | 18.3 ms | 87.4 ms | 106.4 ms |
| p95 latency | 33.5 ms | 100.1 ms | 195.7 ms |
| p99 latency | 69.7 ms | 125.9 ms | 243.2 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.35 blocks | 0.48 blocks |
| Rate limited | 0 | 0 | 15,579 |
| Unsupported | 0 | 0 | 189 |
| Samples | 97,594 | 95,236 | 22,390 |
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.3points
- Latency+11.4
- Head freshness−0.2
- Availability+0.1
- Correctness−0.0
The parts add to +11.3, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+20.7points
- Latency+20.7
- Head freshness−0.0
- Correctness−0.0
- Availability−0.0
The parts add to +20.7, exactly — the score is a weighted sum, so it comes apart.