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
6h window · 6.0 hours observed · generated 2026-08-28 01:24:04 UTC
| Metric | dRPC | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 5 | 6 | 8 |
| Score | 91.8 | 83.8 | 77.9 | 60.3 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.97% | 99.99% | 100.00% | 79.94% |
| p50 latency | 32.4 ms | 104.7 ms | 106.2 ms | 1326.0 ms |
| p95 latency | 62.8 ms | 120.7 ms | 193.4 ms | 7406.7 ms |
| p99 latency | 168.4 ms | 148.6 ms | 281.6 ms | 9776.0 ms |
| Correctness | 99.98% | 99.99% | 100.00% | 96.96% |
| Head lag | 0.37 blocks | 0.41 blocks | 0.49 blocks | 0.94 blocks |
| Rate limited | 13 | 32 | 1,425 | 1,481 |
| Unsupported | 0 | 0 | 15 | 0 |
| Samples | 8,595 | 8,746 | 2,100 | 2,044 |
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
+8.0points
- Latency+8.0
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +8.0, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+13.8points
- Latency+13.7
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +13.8, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+31.5points
- Latency+22.2
- Availability+8.0
- Head freshness+0.7
- Correctness+0.6
The parts add to +31.5, exactly — the score is a weighted sum, so it comes apart.