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
1h window · 60 minutes observed · generated 2026-08-28 00:59:54 UTC
| Metric | PublicNode | dRPC | 1RPC |
|---|---|---|---|
| Rank | 1 | 3 | 8 |
| Score | 99.4 | 91.7 | 60.2 |
| Status | Excellent | Excellent | Degraded |
| Availability | 99.94% | 99.87% | 79.89% |
| p50 latency | 17.7 ms | 32.3 ms | 1317.0 ms |
| p95 latency | 29.1 ms | 59.0 ms | 7406.7 ms |
| p99 latency | 55.0 ms | 179.2 ms | 9776.0 ms |
| Correctness | 99.94% | 99.87% | 96.95% |
| Head lag | 0.49 blocks | 0.39 blocks | 0.94 blocks |
| Rate limited | 0 | 1 | 239 |
| Unsupported | 0 | 0 | 0 |
| Samples | 1,632 | 1,591 | 624 |
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
+7.7points
- Latency+7.7
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +7.7, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+39.1points
- Latency+30.0
- Availability+8.0
- Correctness+0.6
- Head freshness+0.5
The parts add to +39.1, exactly — the score is a weighted sum, so it comes apart.