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 · 2.2 days observed · generated 2026-08-27 01:40:31 UTC
| Metric | PublicNode | Tenderly | Merkle |
|---|---|---|---|
| Rank | 1 | 3 | 6 |
| Score | 99.4 | 93.6 | 79.2 |
| Status | Excellent | Excellent | Good |
| Availability | 99.97% | 99.96% | 99.98% |
| p50 latency | 18.3 ms | 19.9 ms | 106.6 ms |
| p95 latency | 33.7 ms | 73.0 ms | 196.1 ms |
| p99 latency | 70.4 ms | 879.9 ms | 243.1 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.51 blocks | 0.47 blocks |
| Rate limited | 0 | 0 | 13,834 |
| Unsupported | 0 | 0 | 169 |
| Samples | 86,541 | 85,897 | 19,909 |
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.
PublicNodevsTenderly
+5.8points
- Latency+5.8
- Head freshness+0.0
- Availability+0.0
- Correctness−0.0
The parts add to +5.8, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+20.2points
- Latency+20.3
- Head freshness−0.0
- Correctness−0.0
- Availability−0.0
The parts add to +20.2, exactly — the score is a weighted sum, so it comes apart.