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
24h window · 24 hours observed · generated 2026-08-27 03:39:36 UTC
| Metric | PublicNode | Merkle | 1RPC |
|---|---|---|---|
| Rank | 1 | 6 | 8 |
| Score | 99.4 | 78.0 | 58.5 |
| Status | Excellent | Good | Degraded |
| Availability | 99.98% | 100.00% | 75.73% |
| p50 latency | 18.3 ms | 107.2 ms | 2024.4 ms |
| p95 latency | 35.2 ms | 194.0 ms | 6590.4 ms |
| p99 latency | 74.2 ms | 239.8 ms | 9196.2 ms |
| Correctness | 100.00% | 100.00% | 96.63% |
| Head lag | 0.49 blocks | 0.46 blocks | 0.95 blocks |
| Rate limited | 0 | 6,163 | 6,577 |
| Unsupported | 0 | 81 | 0 |
| Samples | 38,631 | 8,806 | 7,892 |
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.4points
- Latency+21.5
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +21.4, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+40.9points
- Latency+30.0
- Availability+9.7
- Correctness+0.7
- Head freshness+0.5
The parts add to +40.9, exactly — the score is a weighted sum, so it comes apart.