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
- Tenderly
- PublicNode
- dRPC
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-28 22:34:18 UTC
| Metric | dRPC | MEV Blocker | Cloudflare |
|---|---|---|---|
| Rank | 3 | 7 | 8 |
| Score | 88.4 | 69.5 | 48.9 |
| Status | Good | Degraded | Poor |
| Availability | 99.99% | 99.93% | 23.16% |
| p50 latency | 35.0 ms | 122.8 ms | 13.6 ms |
| p95 latency | 66.8 ms | 210.1 ms | 85.9 ms |
| p99 latency | 174.0 ms | 229.4 ms | 172.6 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.39 blocks | 0.39 blocks | no cohort |
| Rate limited | 13 | 0 | 5 |
| Unsupported | 0 | 0 | 271 |
| Samples | 8,878 | 9,011 | 9,029 |
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.9
- Availability+0.0
- Head freshness−0.0
- Correctness+0.0
The parts add to +18.9, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+39.6points
- Availability+29.7
- Head freshness*+9.5
- Latency+2.6
- Correctness−2.2
The parts add to +39.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.