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:09:48 UTC
| Metric | dRPC | Cloudflare |
|---|---|---|
| Rank | 3 | 8 |
| Score | 88.6 | 48.7 |
| Status | Good | Poor |
| Availability | 99.99% | 23.12% |
| p50 latency | 33.7 ms | 15.8 ms |
| p95 latency | 68.5 ms | 88.9 ms |
| p99 latency | 189.9 ms | 271.2 ms |
| Correctness | 100.00% | 100.00% |
| Head lag | 0.36 blocks | no cohort |
| Rate limited | 13 | 15 |
| Unsupported | 0 | 244 |
| Samples | 8,228 | 8,363 |
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
+40.0points
- Availability+29.7
- Head freshness*+9.6
- Latency+2.9
- Correctness−2.2
The parts add to +40.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.