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 · 44 hours observed · generated 2026-08-26 17:02:21 UTC
| Metric | PublicNode | Merkle | 1RPC |
|---|---|---|---|
| Rank | 1 | 6 | 8 |
| Score | 99.4 | 78.4 | 64.0 |
| Status | Excellent | Good | Degraded |
| Availability | 99.98% | 99.97% | 88.84% |
| p50 latency | 18.4 ms | 106.5 ms | 189.3 ms |
| p95 latency | 32.3 ms | 196.8 ms | 2922.0 ms |
| p99 latency | 68.4 ms | 245.4 ms | 6561.8 ms |
| Correctness | 99.98% | 100.00% | 97.72% |
| Head lag | 0.49 blocks | 0.47 blocks | 0.90 blocks |
| Rate limited | 0 | 11,667 | 12,352 |
| Unsupported | 0 | 144 | 0 |
| Samples | 72,436 | 16,811 | 15,197 |
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.
PublicNodevsMerkle
+21.0points
- Latency+21.1
- Head freshness−0.0
- Correctness−0.0
- Availability+0.0
The parts add to +21.0, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+35.4points
- Latency+30.0
- Availability+4.5
- Head freshness+0.5
- Correctness+0.5
The parts add to +35.4, exactly — the score is a weighted sum, so it comes apart.