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 01:20:46 UTC
| Metric | PublicNode | Merkle | 1RPC |
|---|---|---|---|
| Rank | 2 | 6 | 8 |
| Score | 98.4 | 77.6 | 58.7 |
| Status | Excellent | Good | Degraded |
| Availability | 99.99% | 100.00% | 76.33% |
| p50 latency | 17.2 ms | 106.2 ms | 2024.4 ms |
| p95 latency | 36.7 ms | 193.1 ms | 6590.4 ms |
| p99 latency | 101.8 ms | 219.0 ms | 9196.2 ms |
| Correctness | 100.00% | 100.00% | 96.63% |
| Head lag | 0.49 blocks | 0.53 blocks | 0.95 blocks |
| Rate limited | 0 | 1,357 | 1,459 |
| Unsupported | 0 | 15 | 0 |
| Samples | 8,735 | 1,937 | 2,033 |
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
+20.8points
- Latency+20.8
- Head freshness+0.0
- Availability−0.0
- Correctness+0.0
The parts add to +20.8, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+39.7points
- Latency+29.0
- Availability+9.5
- Correctness+0.7
- Head freshness+0.5
The parts add to +39.7, exactly — the score is a weighted sum, so it comes apart.