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 09:48:04 UTC
| Metric | PublicNode | Tenderly | Merkle |
|---|---|---|---|
| Rank | 1 | 2 | 6 |
| Score | 99.4 | 99.3 | 70.1 |
| Status | Excellent | Excellent | Degraded |
| Availability | 99.98% | 99.95% | 100.00% |
| p50 latency | 19.4 ms | 18.8 ms | 105.1 ms |
| p95 latency | 32.9 ms | 33.3 ms | 194.3 ms |
| p99 latency | 71.3 ms | 122.3 ms | 228.8 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.49 blocks | 0.60 blocks |
| Rate limited | 0 | 0 | 1,478 |
| Unsupported | 0 | 0 | 18 |
| Samples | 9,468 | 9,385 | 2,161 |
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
+0.1points
- Latency+0.1
- Availability+0.0
- Head freshness−0.0
- Correctness−0.0
The parts add to +0.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+29.3points
- Latency+29.2
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +29.3, exactly — the score is a weighted sum, so it comes apart.