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
24h window · 24 hours observed · generated 2026-08-26 22:14:26 UTC
| Metric | dRPC | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 3 | 6 | 9 |
| Score | 91.4 | 78.0 | 52.3 |
| Status | Excellent | Good | Degraded |
| Availability | 99.93% | 100.00% | 23.09% |
| p50 latency | 34.1 ms | 107.1 ms | 16.1 ms |
| p95 latency | 68.4 ms | 196.8 ms | 94.1 ms |
| p99 latency | 167.9 ms | 241.2 ms | 247.6 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.37 blocks | 0.46 blocks | no cohort |
| Rate limited | 120 | 6,064 | 39 |
| Unsupported | 0 | 79 | 1,113 |
| Samples | 37,054 | 8,753 | 37,567 |
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
+13.4points
- Latency+13.3
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +13.4, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+39.0points
- Availability+29.7
- Head freshness*+9.5
- Correctness−2.2
- Latency+2.0
The parts add to +39.0, 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.