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
24h window · 24 hours observed · generated 2026-08-27 21:37:23 UTC
| Metric | Tenderly | PublicNode | dRPC |
|---|---|---|---|
| Rank | 1 | 2 | 3 |
| Score | 99.4 | 97.7 | 91.3 |
| Status | Excellent | Excellent | Excellent |
| Availability | 99.98% | 99.99% | 99.95% |
| p50 latency | 19.3 ms | 21.5 ms | 33.4 ms |
| p95 latency | 33.2 ms | 41.7 ms | 69.4 ms |
| p99 latency | 74.1 ms | 101.5 ms | 174.0 ms |
| Correctness | 100.00% | 100.00% | 99.99% |
| Head lag | 0.48 blocks | 0.48 blocks | 0.36 blocks |
| Rate limited | 0 | 0 | 127 |
| Unsupported | 0 | 0 | 0 |
| Samples | 38,245 | 38,593 | 37,655 |
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 Tenderly, the highest scorer of those selected.
TenderlyvsPublicNode
+1.7points
- Latency+1.7
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +1.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsdRPC
+8.1points
- Latency+8.2
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.1, exactly — the score is a weighted sum, so it comes apart.