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 · 4.2 days observed · generated 2026-08-29 01:26:33 UTC
| Metric | dRPC | Merkle | 1RPC |
|---|---|---|---|
| Rank | 3 | 6 | 8 |
| Score | 90.9 | 78.0 | 61.7 |
| Status | Excellent | Good | Degraded |
| Availability | 99.95% | 99.99% | 83.07% |
| p50 latency | 33.8 ms | 107.0 ms | 320.2 ms |
| p95 latency | 72.1 ms | 196.0 ms | 4778.7 ms |
| p99 latency | 174.6 ms | 244.3 ms | 8408.8 ms |
| Correctness | 99.99% | 100.00% | 97.52% |
| Head lag | 0.36 blocks | 0.49 blocks | 0.90 blocks |
| Rate limited | 766 | 26,249 | 28,012 |
| Unsupported | 0 | 319 | 0 |
| Samples | 160,603 | 37,926 | 34,189 |
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.0points
- Latency+12.8
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +13.0, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+29.3points
- Latency+21.4
- Availability+6.8
- Head freshness+0.6
- Correctness+0.5
The parts add to +29.3, exactly — the score is a weighted sum, so it comes apart.