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
30d window · 2.5 days observed · generated 2026-08-27 08:03:19 UTC
| Metric | dRPC | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 5 | 6 | 8 |
| Score | 92.7 | 85.3 | 78.7 | 62.5 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.93% | 99.98% | 99.98% | 85.27% |
| p50 latency | 33.8 ms | 104.5 ms | 106.4 ms | 225.7 ms |
| p95 latency | 71.8 ms | 122.0 ms | 195.6 ms | 4391.3 ms |
| p99 latency | 167.2 ms | 144.6 ms | 243.2 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 | 599 | 1,076 | 15,481 | 16,512 |
| Unsupported | 0 | 0 | 187 | 0 |
| Samples | 94,637 | 95,661 | 22,244 | 20,323 |
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.4points
- Latency+7.4
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +7.4, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+14.0points
- Latency+13.9
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +14.0, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+30.2points
- Latency+23.2
- Availability+5.9
- Head freshness+0.6
- Correctness+0.5
The parts add to +30.2, exactly — the score is a weighted sum, so it comes apart.