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
7d window · 2.9 days observed · generated 2026-08-27 17:17:47 UTC
| Metric | PublicNode | Tenderly | dRPC |
|---|---|---|---|
| Rank | 1 | 2 | 3 |
| Score | 99.4 | 96.5 | 92.2 |
| Status | Excellent | Excellent | Excellent |
| Availability | 99.98% | 99.96% | 99.93% |
| p50 latency | 19.1 ms | 19.8 ms | 33.9 ms |
| p95 latency | 35.2 ms | 51.4 ms | 71.8 ms |
| p99 latency | 75.1 ms | 747.7 ms | 169.3 ms |
| Correctness | 99.99% | 99.99% | 99.99% |
| Head lag | 0.49 blocks | 0.50 blocks | 0.36 blocks |
| Rate limited | 0 | 0 | 650 |
| Unsupported | 0 | 0 | 0 |
| Samples | 112,059 | 111,205 | 109,373 |
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
+2.9points
- Latency+2.8
- Head freshness+0.0
- Availability+0.0
- Correctness−0.0
The parts add to +2.9, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsdRPC
+7.2points
- Latency+7.4
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +7.2, exactly — the score is a weighted sum, so it comes apart.