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 09:14:37 UTC
| Metric | dRPC | MEV Blocker | Cloudflare |
|---|---|---|---|
| Rank | 3 | 7 | 8 |
| Score | 88.3 | 69.4 | 50.5 |
| Status | Good | Degraded | Degraded |
| Availability | 99.94% | 99.91% | 23.07% |
| p50 latency | 31.4 ms | 119.6 ms | 13.3 ms |
| p95 latency | 64.0 ms | 208.4 ms | 74.8 ms |
| p99 latency | 157.9 ms | 227.8 ms | 116.8 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.36 blocks | 0.42 blocks | no cohort |
| Rate limited | 37 | 1 | 7 |
| Unsupported | 0 | 0 | 254 |
| Samples | 8,347 | 8,472 | 8,498 |
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
+18.9points
- Latency+18.8
- Head freshness+0.1
- Availability+0.0
- Correctness−0.0
The parts add to +18.9, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+37.8points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency+0.7
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.