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
Side by side
6h window · 6.0 hours observed · generated 2026-08-27 19:59:05 UTC
| Metric | dRPC | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 3 | 6 | 8 |
| Score | 88.7 | 70.9 | 46.5 |
| Status | Good | Degraded | Poor |
| Availability | 99.98% | 100.00% | 23.20% |
| p50 latency | 35.2 ms | 110.4 ms | 17.7 ms |
| p95 latency | 72.5 ms | 191.2 ms | 104.0 ms |
| p99 latency | 200.7 ms | 236.0 ms | 273.0 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.36 blocks | 0.57 blocks | no cohort |
| Rate limited | 20 | 1,502 | 0 |
| Unsupported | 0 | 22 | 287 |
| Samples | 9,543 | 2,240 | 9,695 |
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
+17.8points
- Latency+17.6
- Head freshness+0.3
- Availability−0.0
- Correctness−0.0
The parts add to +17.8, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+42.2points
- Availability+29.7
- Head freshness*+9.6
- Latency+5.1
- Correctness−2.2
The parts add to +42.2, 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.