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.2 days observed · generated 2026-08-27 01:40:11 UTC
| Metric | PublicNode | dRPC | 1RPC |
|---|---|---|---|
| Rank | 1 | 2 | 8 |
| Score | 99.4 | 93.8 | 62.6 |
| Status | Excellent | Excellent | Degraded |
| Availability | 99.97% | 99.93% | 85.50% |
| p50 latency | 18.3 ms | 34.1 ms | 225.7 ms |
| p95 latency | 33.7 ms | 72.6 ms | 4391.3 ms |
| p99 latency | 70.4 ms | 169.1 ms | 7602.5 ms |
| Correctness | 99.99% | 99.99% | 97.48% |
| Head lag | 0.49 blocks | 0.36 blocks | 0.91 blocks |
| Rate limited | 0 | 558 | 14,726 |
| Unsupported | 0 | 0 | 0 |
| Samples | 86,535 | 84,465 | 18,278 |
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.
PublicNodevsdRPC
+5.6points
- Latency+5.7
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +5.6, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+36.8points
- Latency+30.0
- Availability+5.8
- Correctness+0.5
- Head freshness+0.5
The parts add to +36.8, exactly — the score is a weighted sum, so it comes apart.