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 23:59:17 UTC
| Metric | dRPC | Cloudflare | 1RPC |
|---|---|---|---|
| Rank | 3 | 8 | 9 |
| Score | 88.7 | 48.9 | 0.0 |
| Status | Good | Poor | Poor |
| Availability | 99.99% | 23.12% | 0.00% |
| p50 latency | 33.3 ms | 15.3 ms | 0.0 ms |
| p95 latency | 67.3 ms | 87.0 ms | 0.0 ms |
| p99 latency | 183.3 ms | 267.1 ms | 0.0 ms |
| Correctness | 100.00% | 100.00% | not measured |
| Head lag | 0.36 blocks | no cohort | no cohort |
| Rate limited | 15 | 15 | 1,673 |
| Unsupported | 0 | 282 | 0 |
| Samples | 9,538 | 9,696 | 1,924 |
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
+39.8points
- Availability+29.7
- Head freshness*+9.6
- Latency+2.7
- Correctness−2.2
The parts add to +39.8, 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
+88.7points
- Availability+40.0
- Correctness*+20.0
- Latency*+19.2
- Head freshness*+9.6
The parts add to +88.7, 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.