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
1h window · 60 minutes observed · generated 2026-08-27 20:41:15 UTC
| Metric | dRPC | Cloudflare |
|---|---|---|
| Rank | 3 | 8 |
| Score | 88.9 | 46.9 |
| Status | Good | Poor |
| Availability | 99.94% | 23.16% |
| p50 latency | 34.5 ms | 17.8 ms |
| p95 latency | 69.4 ms | 99.7 ms |
| p99 latency | 181.4 ms | 264.6 ms |
| Correctness | 100.00% | 100.00% |
| Head lag | 0.34 blocks | no cohort |
| Rate limited | 7 | 0 |
| Unsupported | 0 | 47 |
| Samples | 1,565 | 1,596 |
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
+42.0points
- Availability+29.7
- Head freshness*+9.6
- Latency+4.9
- Correctness−2.2
The parts add to +42.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.