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:40:12 UTC
| Metric | dRPC | MEV Blocker | Cloudflare |
|---|---|---|---|
| Rank | 3 | 7 | 8 |
| Score | 88.0 | 69.5 | 46.7 |
| Status | Good | Degraded | Poor |
| Availability | 99.94% | 100.00% | 23.04% |
| p50 latency | 34.7 ms | 125.1 ms | 17.8 ms |
| p95 latency | 73.3 ms | 216.6 ms | 100.8 ms |
| p99 latency | 191.2 ms | 247.2 ms | 269.5 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.34 blocks | 0.40 blocks | no cohort |
| Rate limited | 7 | 0 | 0 |
| Unsupported | 0 | 0 | 48 |
| Samples | 1,562 | 1,597 | 1,593 |
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.5points
- Latency+18.5
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +18.5, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+41.3points
- Availability+29.7
- Head freshness*+9.6
- Latency+4.2
- Correctness−2.2
The parts add to +41.3, 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.