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 19:25:14 UTC
| Metric | PublicNode | Tenderly | dRPC |
|---|---|---|---|
| Rank | 1 | 2 | 3 |
| Score | 99.4 | 96.9 | 92.0 |
| Status | Excellent | Excellent | Excellent |
| Availability | 99.98% | 99.97% | 99.94% |
| p50 latency | 19.3 ms | 19.8 ms | 33.9 ms |
| p95 latency | 35.7 ms | 49.2 ms | 71.8 ms |
| p99 latency | 76.4 ms | 727.5 ms | 170.4 ms |
| Correctness | 99.99% | 99.99% | 99.99% |
| Head lag | 0.49 blocks | 0.50 blocks | 0.36 blocks |
| Rate limited | 0 | 0 | 661 |
| Unsupported | 0 | 0 | 0 |
| Samples | 115,543 | 114,648 | 112,763 |
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.5points
- Latency+2.4
- Head freshness+0.0
- Availability+0.0
- Correctness−0.0
The parts add to +2.5, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsdRPC
+7.4points
- Latency+7.5
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +7.4, exactly — the score is a weighted sum, so it comes apart.