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.4 days observed · generated 2026-08-27 06:47:16 UTC
| Metric | PublicNode | Tenderly | dRPC |
|---|---|---|---|
| Rank | 1 | 2 | 3 |
| Score | 99.4 | 94.9 | 92.9 |
| Status | Excellent | Excellent | Excellent |
| Availability | 99.97% | 99.97% | 99.93% |
| p50 latency | 18.2 ms | 19.8 ms | 33.9 ms |
| p95 latency | 33.5 ms | 61.8 ms | 71.7 ms |
| p99 latency | 69.6 ms | 831.8 ms | 167.3 ms |
| Correctness | 99.99% | 99.99% | 99.99% |
| Head lag | 0.49 blocks | 0.50 blocks | 0.36 blocks |
| Rate limited | 0 | 0 | 588 |
| Unsupported | 0 | 0 | 0 |
| Samples | 94,889 | 94,174 | 92,616 |
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
+4.5points
- Latency+4.5
- Head freshness+0.0
- Availability+0.0
- Correctness−0.0
The parts add to +4.5, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsdRPC
+6.5points
- Latency+6.6
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +6.5, exactly — the score is a weighted sum, so it comes apart.