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 · 3.0 days observed · generated 2026-08-27 21:37:41 UTC
| Metric | dRPC | Cloudflare |
|---|---|---|
| Rank | 3 | 9 |
| Score | 91.9 | 54.1 |
| Status | Excellent | Degraded |
| Availability | 99.94% | 23.11% |
| p50 latency | 33.9 ms | 15.4 ms |
| p95 latency | 71.8 ms | 89.5 ms |
| p99 latency | 170.8 ms | 253.8 ms |
| Correctness | 99.99% | 100.00% |
| Head lag | 0.36 blocks | no cohort |
| Rate limited | 669 | 96 |
| Unsupported | 0 | 3,477 |
| Samples | 116,277 | 118,040 |
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.8points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency+0.8
The parts add to +37.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.