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 13:33:12 UTC
| Metric | Tenderly | PublicNode | dRPC |
|---|---|---|---|
| Rank | 1 | 2 | 3 |
| Score | 99.4 | 96.5 | 88.1 |
| Status | Excellent | Excellent | Good |
| Availability | 99.94% | 99.98% | 99.94% |
| p50 latency | 20.1 ms | 23.6 ms | 33.7 ms |
| p95 latency | 35.0 ms | 45.6 ms | 73.4 ms |
| p99 latency | 102.1 ms | 125.1 ms | 174.6 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.48 blocks | 0.49 blocks | 0.35 blocks |
| Rate limited | 0 | 0 | 42 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,997 | 9,080 | 8,854 |
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
+2.9points
- Latency+2.9
- 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.
TenderlyvsdRPC
+11.2points
- Latency+11.4
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +11.2, exactly — the score is a weighted sum, so it comes apart.