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 07:57:53 UTC
| Metric | PublicNode | Tenderly | dRPC |
|---|---|---|---|
| Rank | 1 | 2 | 3 |
| Score | 99.4 | 98.6 | 87.8 |
| Status | Excellent | Excellent | Good |
| Availability | 99.99% | 99.99% | 99.96% |
| p50 latency | 18.0 ms | 18.3 ms | 31.3 ms |
| p95 latency | 29.5 ms | 31.9 ms | 63.8 ms |
| p99 latency | 59.6 ms | 70.5 ms | 157.1 ms |
| Correctness | 100.00% | 100.00% | 99.99% |
| Head lag | 0.48 blocks | 0.48 blocks | 0.37 blocks |
| Rate limited | 0 | 0 | 37 |
| Unsupported | 0 | 0 | 0 |
| Samples | 9,735 | 9,650 | 9,497 |
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.8points
- Latency+0.8
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +0.8, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsdRPC
+11.6points
- Latency+11.8
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +11.6, exactly — the score is a weighted sum, so it comes apart.