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-28 03:08:08 UTC
| Metric | dRPC | Merkle | 1RPC |
|---|---|---|---|
| Rank | 3 | 6 | 8 |
| Score | 91.5 | 78.0 | 58.7 |
| Status | Excellent | Good | Degraded |
| Availability | 99.96% | 100.00% | 75.93% |
| p50 latency | 33.3 ms | 107.5 ms | 1326.0 ms |
| p95 latency | 68.0 ms | 192.5 ms | 7406.7 ms |
| p99 latency | 173.7 ms | 238.0 ms | 9776.0 ms |
| Correctness | 99.99% | 100.00% | 96.96% |
| Head lag | 0.36 blocks | 0.54 blocks | 0.94 blocks |
| Rate limited | 101 | 5,970 | 6,424 |
| Unsupported | 0 | 70 | 0 |
| Samples | 36,870 | 8,763 | 7,717 |
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.5points
- Latency+13.3
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +13.5, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+32.9points
- Latency+22.0
- Availability+9.6
- Head freshness+0.7
- Correctness+0.6
The parts add to +32.9, exactly — the score is a weighted sum, so it comes apart.