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 · 2.6 days observed · generated 2026-08-27 11:34:32 UTC
| Metric | dRPC | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 5 | 6 | 8 |
| Score | 92.5 | 85.2 | 78.6 | 62.5 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.93% | 99.98% | 99.98% | 85.27% |
| p50 latency | 33.8 ms | 104.7 ms | 106.5 ms | 225.7 ms |
| p95 latency | 72.0 ms | 122.1 ms | 196.1 ms | 4391.3 ms |
| p99 latency | 167.8 ms | 145.8 ms | 243.6 ms | 7602.5 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 97.48% |
| Head lag | 0.36 blocks | 0.42 blocks | 0.48 blocks | 0.91 blocks |
| Rate limited | 628 | 1,150 | 16,387 | 17,494 |
| Unsupported | 0 | 0 | 199 | 0 |
| Samples | 100,246 | 101,370 | 23,598 | 21,447 |
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.
dRPCvsBlast API
+7.3points
- Latency+7.3
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +7.3, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+13.9points
- Latency+13.8
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +13.9, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+29.9points
- Latency+22.9
- Availability+5.9
- Head freshness+0.6
- Correctness+0.5
The parts add to +29.9, exactly — the score is a weighted sum, so it comes apart.