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 · 45 hours observed · generated 2026-08-26 18:02:04 UTC
| Metric | dRPC | Cloudflare |
|---|---|---|
| Rank | 2 | 9 |
| Score | 93.5 | 55.5 |
| Status | Excellent | Degraded |
| Availability | 99.93% | 23.09% |
| p50 latency | 33.9 ms | 15.4 ms |
| p95 latency | 72.7 ms | 90.3 ms |
| p99 latency | 167.9 ms | 254.6 ms |
| Correctness | 99.99% | 100.00% |
| Head lag | 0.36 blocks | no cohort |
| Rate limited | 516 | 60 |
| Unsupported | 0 | 2,160 |
| Samples | 72,306 | 73,323 |
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
+38.0points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency+1.0
The parts add to +38.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.