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
24h window · 24 hours observed · generated 2026-08-28 23:54:21 UTC
| Metric | dRPC | Cloudflare |
|---|---|---|
| Rank | 3 | 9 |
| Score | 89.3 | 53.4 |
| Status | Good | Degraded |
| Availability | 99.98% | 23.13% |
| p50 latency | 33.8 ms | 13.0 ms |
| p95 latency | 76.8 ms | 83.3 ms |
| p99 latency | 190.3 ms | 141.8 ms |
| Correctness | 99.99% | 100.00% |
| Head lag | 0.38 blocks | no cohort |
| Rate limited | 95 | 11 |
| Unsupported | 0 | 1,148 |
| Samples | 38,101 | 38,788 |
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
+35.9points
- Availability+29.7
- Head freshness*+9.5
- Correctness−2.2
- Latency−1.1
The parts add to +35.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.