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 17:32:13 UTC
| Metric | dRPC | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 3 | 6 | 8 |
| Score | 86.5 | 69.6 | 47.6 |
| Status | Good | Degraded | Poor |
| Availability | 99.99% | 100.00% | 23.12% |
| p50 latency | 36.1 ms | 110.7 ms | 14.3 ms |
| p95 latency | 77.0 ms | 207.7 ms | 93.7 ms |
| p99 latency | 178.8 ms | 293.9 ms | 161.8 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.36 blocks | 0.45 blocks | no cohort |
| Rate limited | 52 | 1,446 | 0 |
| Unsupported | 0 | 15 | 266 |
| Samples | 8,816 | 2,067 | 8,993 |
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
+16.9points
- Latency+16.8
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +16.9, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+38.9points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency+1.8
The parts add to +38.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.