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
30d window · 2.6 days observed · generated 2026-08-27 10:43:38 UTC
| Metric | dRPC | 1RPC | Cloudflare |
|---|---|---|---|
| Rank | 3 | 8 | 9 |
| Score | 92.5 | 62.5 | 55.2 |
| Status | Excellent | Degraded | Degraded |
| Availability | 99.93% | 85.27% | 23.10% |
| p50 latency | 33.8 ms | 225.7 ms | 15.0 ms |
| p95 latency | 72.0 ms | 4391.3 ms | 86.8 ms |
| p99 latency | 167.9 ms | 7602.5 ms | 251.6 ms |
| Correctness | 99.99% | 97.48% | 100.00% |
| Head lag | 0.36 blocks | 0.91 blocks | no cohort |
| Rate limited | 624 | 17,260 | 96 |
| Unsupported | 0 | 0 | 2,956 |
| Samples | 98,900 | 21,177 | 100,371 |
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 dRPC, the highest scorer of those selected.
dRPCvs1RPC
+30.0points
- Latency+23.0
- Availability+5.9
- Head freshness+0.6
- Correctness+0.5
The parts add to +30.0, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+37.4points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency+0.3
The parts add to +37.4, exactly — the score is a weighted sum, so it comes apart. Components marked * were measured for only one of the two; the other’s weight is spread across what it does have, which is why the two sides can carry different weights for the same row.