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
- Merkle
- MEV Blocker
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-28 13:22:19 UTC
| Metric | dRPC | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 4 | 6 | 8 |
| Score | 78.8 | 69.5 | 47.5 |
| Status | Good | Degraded | Poor |
| Availability | 99.96% | 100.00% | 23.19% |
| p50 latency | 34.0 ms | 108.4 ms | 13.5 ms |
| p95 latency | 117.3 ms | 202.3 ms | 91.0 ms |
| p99 latency | 199.7 ms | 237.7 ms | 134.8 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.37 blocks | 0.57 blocks | no cohort |
| Rate limited | 18 | 1,379 | 6 |
| Unsupported | 0 | 14 | 260 |
| Samples | 8,563 | 1,991 | 8,705 |
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
+9.3points
- Latency+9.0
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +9.3, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+31.3points
- Availability+29.7
- Head freshness*+9.5
- Latency−5.7
- Correctness−2.2
The parts add to +31.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.