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
- 1RPC
- Cloudflare
Side by side
24h window · 24 hours observed · generated 2026-08-28 00:21:44 UTC
| Metric | dRPC | MEV Blocker | Cloudflare |
|---|---|---|---|
| Rank | 3 | 7 | 9 |
| Score | 91.4 | 76.8 | 53.5 |
| Status | Excellent | Good | Degraded |
| Availability | 99.97% | 99.93% | 23.13% |
| p50 latency | 33.1 ms | 122.1 ms | 15.0 ms |
| p95 latency | 68.7 ms | 213.7 ms | 86.8 ms |
| p99 latency | 173.1 ms | 235.2 ms | 244.2 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.36 blocks | 0.40 blocks | no cohort |
| Rate limited | 116 | 1 | 34 |
| Unsupported | 0 | 0 | 1,114 |
| Samples | 37,235 | 37,770 | 37,862 |
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.9points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency+0.9
The parts add to +37.9, 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.