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.8 days observed · generated 2026-08-27 15:18:38 UTC
| Metric | PublicNode | Tenderly | Merkle |
|---|---|---|---|
| Rank | 1 | 2 | 6 |
| Score | 99.4 | 96.3 | 78.5 |
| Status | Excellent | Excellent | Good |
| Availability | 99.98% | 99.96% | 99.98% |
| p50 latency | 18.9 ms | 19.8 ms | 106.7 ms |
| p95 latency | 34.7 ms | 52.6 ms | 195.8 ms |
| p99 latency | 74.0 ms | 766.2 ms | 243.2 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.50 blocks | 0.48 blocks |
| Rate limited | 0 | 0 | 17,336 |
| Unsupported | 0 | 0 | 210 |
| Samples | 108,818 | 107,989 | 24,984 |
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
+3.1points
- Latency+3.1
- Head freshness+0.0
- Availability+0.0
- Correctness−0.0
The parts add to +3.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+20.9points
- Latency+20.9
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +20.9, exactly — the score is a weighted sum, so it comes apart.