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-29 02:28:10 UTC
| Metric | dRPC | Merkle | 1RPC |
|---|---|---|---|
| Rank | 3 | 6 | 8 |
| Score | 90.8 | 77.6 | 61.7 |
| Status | Excellent | Good | Degraded |
| Availability | 99.99% | 100.00% | 82.57% |
| p50 latency | 32.3 ms | 106.2 ms | 647.0 ms |
| p95 latency | 64.4 ms | 199.4 ms | 4257.4 ms |
| p99 latency | 180.7 ms | 236.2 ms | 7627.6 ms |
| Correctness | 99.99% | 100.00% | 98.30% |
| Head lag | 0.40 blocks | 0.44 blocks | 0.85 blocks |
| Rate limited | 3 | 1,400 | 1,501 |
| Unsupported | 0 | 20 | 0 |
| Samples | 8,694 | 2,056 | 2,053 |
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.2points
- Latency+13.2
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +13.2, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+29.1points
- Latency+21.3
- Availability+7.0
- Head freshness+0.5
- Correctness+0.3
The parts add to +29.1, exactly — the score is a weighted sum, so it comes apart.