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 04:46:12 UTC
| Metric | dRPC | Merkle | 1RPC |
|---|---|---|---|
| Rank | 3 | 6 | 8 |
| Score | 87.4 | 77.4 | 61.9 |
| Status | Good | Good | Degraded |
| Availability | 99.99% | 100.00% | 83.05% |
| p50 latency | 31.3 ms | 105.5 ms | 647.0 ms |
| p95 latency | 82.8 ms | 191.1 ms | 4257.4 ms |
| p99 latency | 174.3 ms | 232.0 ms | 7627.6 ms |
| Correctness | 99.99% | 100.00% | 98.30% |
| Head lag | 0.38 blocks | 0.48 blocks | 0.85 blocks |
| Rate limited | 4 | 1,524 | 1,583 |
| Unsupported | 0 | 23 | 0 |
| Samples | 9,187 | 2,239 | 2,147 |
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
+10.0points
- Latency+9.8
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +10.0, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+25.5points
- Latency+17.8
- Availability+6.8
- Head freshness+0.5
- Correctness+0.3
The parts add to +25.5, exactly — the score is a weighted sum, so it comes apart.