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 · 47 hours observed · generated 2026-08-26 19:57:42 UTC
| Metric | dRPC | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 2 | 6 | 9 |
| Score | 93.6 | 78.4 | 55.3 |
| Status | Excellent | Good | Degraded |
| Availability | 99.94% | 99.97% | 23.09% |
| p50 latency | 34.0 ms | 106.7 ms | 15.5 ms |
| p95 latency | 72.5 ms | 196.2 ms | 91.3 ms |
| p99 latency | 167.4 ms | 244.4 ms | 254.1 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.36 blocks | 0.46 blocks | no cohort |
| Rate limited | 527 | 12,386 | 60 |
| Unsupported | 0 | 151 | 2,254 |
| Samples | 75,367 | 17,844 | 76,436 |
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
+15.2points
- Latency+15.1
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +15.2, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+38.3points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency+1.2
The parts add to +38.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.