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
7d window · 2.5 days observed · generated 2026-08-27 08:09:52 UTC
| Metric | dRPC | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 3 | 6 | 9 |
| Score | 92.7 | 78.7 | 55.3 |
| Status | Excellent | Good | Degraded |
| Availability | 99.93% | 99.98% | 23.10% |
| p50 latency | 33.8 ms | 106.4 ms | 15.0 ms |
| p95 latency | 71.8 ms | 195.6 ms | 87.0 ms |
| p99 latency | 167.0 ms | 243.2 ms | 252.4 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.36 blocks | 0.48 blocks | no cohort |
| Rate limited | 600 | 15,506 | 77 |
| Unsupported | 0 | 187 | 2,836 |
| Samples | 94,808 | 22,281 | 96,214 |
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
+14.1points
- Latency+13.9
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +14.1, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+37.4points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency+0.4
The parts add to +37.4, 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.