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
- NodeReal
- dRPC
- Blast API
- MEV Blocker
- Merkle
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-28 14:46:57 UTC
| Metric | dRPC | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 4 | 7 | 8 |
| Score | 79.4 | 69.3 | 47.7 |
| Status | Good | Degraded | Poor |
| Availability | 99.99% | 100.00% | 23.20% |
| p50 latency | 35.2 ms | 109.0 ms | 13.9 ms |
| p95 latency | 115.0 ms | 208.2 ms | 91.5 ms |
| p99 latency | 197.7 ms | 332.7 ms | 136.5 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.36 blocks | 0.56 blocks | no cohort |
| Rate limited | 19 | 1,479 | 6 |
| Unsupported | 0 | 14 | 277 |
| Samples | 9,217 | 2,134 | 9,370 |
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.
dRPCvsMerkle
+10.1points
- Latency+9.8
- Head freshness+0.2
- Availability−0.0
- Correctness+0.0
The parts add to +10.1, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+31.7points
- Availability+29.7
- Head freshness*+9.6
- Latency−5.3
- Correctness−2.2
The parts add to +31.7, 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.