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 06:51:21 UTC
| Metric | PublicNode | Merkle | 1RPC |
|---|---|---|---|
| Rank | 1 | 6 | 9 |
| Score | 99.4 | 70.1 | 0.0 |
| Status | Excellent | Degraded | Poor |
| Availability | 99.98% | 100.00% | 0.00% |
| p50 latency | 17.8 ms | 105.0 ms | 0.0 ms |
| p95 latency | 30.5 ms | 192.8 ms | 0.0 ms |
| p99 latency | 54.7 ms | 268.8 ms | 0.0 ms |
| Correctness | 100.00% | 100.00% | not measured |
| Head lag | 0.48 blocks | 0.51 blocks | no cohort |
| Rate limited | 0 | 1,477 | 1,638 |
| Unsupported | 0 | 18 | 0 |
| Samples | 9,563 | 2,092 | 1,878 |
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
+29.3points
- Latency+29.2
- Head freshness+0.0
- Availability−0.0
- Correctness+0.0
The parts add to +29.3, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+99.4points
- Availability+40.0
- Latency*+30.0
- Correctness*+20.0
- Head freshness*+9.4
The parts add to +99.4, exactly — the score is a weighted sum, so it comes apart. Components marked * were measured for only one of the two; the other’s weight is spread across what it does have, which is why the two sides can carry different weights for the same row.