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
1h window · 60 minutes observed · generated 2026-08-28 00:16:55 UTC
| Metric | dRPC | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 5 | 6 | 8 |
| Score | 91.4 | 83.6 | 77.8 | 56.6 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 100.00% | 100.00% | 100.00% | 70.42% |
| p50 latency | 31.6 ms | 103.4 ms | 107.0 ms | 2778.6 ms |
| p95 latency | 60.8 ms | 119.8 ms | 202.2 ms | 8458.8 ms |
| p99 latency | 148.1 ms | 147.2 ms | 301.3 ms | 9776.0 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 98.04% |
| Head lag | 0.39 blocks | 0.41 blocks | 0.30 blocks | 1.00 blocks |
| Rate limited | 1 | 0 | 254 | 202 |
| Unsupported | 0 | 0 | 5 | 0 |
| Samples | 1,584 | 1,614 | 385 | 378 |
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.7points
- Latency+7.7
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +7.7, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+13.6points
- Latency+13.7
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +13.6, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+34.8points
- Latency+21.9
- Availability+11.8
- Head freshness+0.7
- Correctness+0.4
The parts add to +34.8, exactly — the score is a weighted sum, so it comes apart.