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 06:50:32 UTC
| Metric | PublicNode | Tenderly | dRPC |
|---|---|---|---|
| Rank | 1 | 2 | 3 |
| Score | 99.4 | 99.3 | 91.0 |
| Status | Excellent | Excellent | Excellent |
| Availability | 99.97% | 99.98% | 99.91% |
| p50 latency | 18.2 ms | 19.5 ms | 34.1 ms |
| p95 latency | 35.1 ms | 35.6 ms | 69.4 ms |
| p99 latency | 73.2 ms | 131.5 ms | 172.1 ms |
| Correctness | 100.00% | 99.99% | 99.99% |
| Head lag | 0.49 blocks | 0.49 blocks | 0.38 blocks |
| Rate limited | 0 | 0 | 137 |
| Unsupported | 0 | 0 | 0 |
| Samples | 38,925 | 38,590 | 38,003 |
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.1points
- Latency+0.1
- Head freshness+0.0
- Availability−0.0
- Correctness+0.0
The parts add to +0.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsdRPC
+8.4points
- Latency+8.5
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.4, exactly — the score is a weighted sum, so it comes apart.