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 · 2.8 days observed · generated 2026-08-27 16:06:19 UTC
| Metric | dRPC | MEV Blocker | Cloudflare |
|---|---|---|---|
| Rank | 3 | 7 | 9 |
| Score | 92.2 | 77.6 | 54.6 |
| Status | Excellent | Good | Degraded |
| Availability | 99.93% | 99.89% | 23.11% |
| p50 latency | 33.8 ms | 119.0 ms | 15.2 ms |
| p95 latency | 71.8 ms | 210.0 ms | 88.1 ms |
| p99 latency | 169.5 ms | 233.8 ms | 251.3 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.36 blocks | 0.40 blocks | no cohort |
| Rate limited | 645 | 3 | 96 |
| Unsupported | 0 | 0 | 3,214 |
| Samples | 107,462 | 109,069 | 109,098 |
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.
dRPCvsMEV Blocker
+14.6points
- Latency+14.5
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +14.6, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+37.6points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency+0.6
The parts add to +37.6, 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.