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
24h window · 24 hours observed · generated 2026-08-28 01:23:26 UTC
| Metric | dRPC | MEV Blocker | Cloudflare |
|---|---|---|---|
| Rank | 3 | 7 | 9 |
| Score | 91.5 | 76.8 | 53.4 |
| Status | Excellent | Good | Degraded |
| Availability | 99.96% | 99.92% | 23.12% |
| p50 latency | 33.2 ms | 122.0 ms | 15.0 ms |
| p95 latency | 68.3 ms | 213.8 ms | 87.0 ms |
| p99 latency | 174.1 ms | 235.0 ms | 242.7 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.36 blocks | 0.40 blocks | no cohort |
| Rate limited | 111 | 1 | 34 |
| Unsupported | 0 | 0 | 1,116 |
| Samples | 37,274 | 37,827 | 37,913 |
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.6
- 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
+38.0points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency+1.0
The parts add to +38.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.