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
6h window · 6.0 hours observed · generated 2026-08-27 12:28:27 UTC
| Metric | dRPC | Cloudflare | 1RPC |
|---|---|---|---|
| Rank | 3 | 8 | 9 |
| Score | 86.9 | 49.9 | 0.0 |
| Status | Good | Poor | Poor |
| Availability | 99.95% | 23.20% | 0.00% |
| p50 latency | 33.2 ms | 15.3 ms | 0.0 ms |
| p95 latency | 77.6 ms | 85.5 ms | 0.0 ms |
| p99 latency | 175.7 ms | 119.2 ms | 0.0 ms |
| Correctness | 100.00% | 100.00% | not measured |
| Head lag | 0.36 blocks | no cohort | no cohort |
| Rate limited | 45 | 19 | 1,529 |
| Unsupported | 0 | 259 | 0 |
| Samples | 8,731 | 8,872 | 1,750 |
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.
dRPCvsCloudflare
+37.0points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency−0.1
The parts add to +37.0, 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.
dRPCvs1RPC
+86.9points
- Availability+40.0
- Correctness*+20.0
- Latency*+17.4
- Head freshness*+9.6
The parts add to +86.9, 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.