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 00:02:47 UTC
| Metric | dRPC | Cloudflare | 1RPC |
|---|---|---|---|
| Rank | 3 | 8 | 9 |
| Score | 92.0 | 53.7 | 39.7 |
| Status | Excellent | Degraded | Poor |
| Availability | 99.99% | 23.07% | 27.27% |
| p50 latency | 32.8 ms | 14.9 ms | 3241.1 ms |
| p95 latency | 64.0 ms | 83.4 ms | 8458.8 ms |
| p99 latency | 166.1 ms | 261.4 ms | 8458.8 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.36 blocks | no cohort | 1.00 blocks |
| Rate limited | 11 | 15 | 1,398 |
| Unsupported | 0 | 239 | 0 |
| Samples | 8,035 | 8,170 | 1,623 |
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.
dRPCvsCloudflare
+38.3points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency+1.2
The parts add to +38.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.
dRPCvs1RPC
+52.2points
- Availability+29.1
- Latency+22.4
- Head freshness+0.7
- Correctness+0.0
The parts add to +52.2, exactly — the score is a weighted sum, so it comes apart.