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 18:38:54 UTC
| Metric | PublicNode | dRPC | 1RPC |
|---|---|---|---|
| Rank | 1 | 3 | 8 |
| Score | 99.4 | 92.0 | 62.4 |
| Status | Excellent | Excellent | Degraded |
| Availability | 99.98% | 99.94% | 84.99% |
| p50 latency | 19.2 ms | 33.9 ms | 225.7 ms |
| p95 latency | 35.5 ms | 71.9 ms | 4391.3 ms |
| p99 latency | 76.1 ms | 170.3 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 | 660 | 19,479 |
| Unsupported | 0 | 0 | 0 |
| Samples | 114,280 | 111,534 | 23,721 |
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.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.
PublicNodevs1RPC
+37.0points
- Latency+30.0
- Availability+6.0
- Correctness+0.5
- Head freshness+0.5
The parts add to +37.0, exactly — the score is a weighted sum, so it comes apart.