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
24h window · 24 hours observed · generated 2026-08-27 23:46:19 UTC
| Metric | dRPC | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 5 | 6 | 8 |
| Score | 91.3 | 83.8 | 78.0 | 57.5 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.97% | 99.97% | 100.00% | 73.21% |
| p50 latency | 33.2 ms | 106.2 ms | 107.4 ms | 2024.4 ms |
| p95 latency | 68.9 ms | 123.3 ms | 192.9 ms | 6590.4 ms |
| p99 latency | 172.8 ms | 150.9 ms | 236.0 ms | 9196.2 ms |
| Correctness | 99.99% | 100.00% | 100.00% | 96.63% |
| Head lag | 0.36 blocks | 0.42 blocks | 0.53 blocks | 0.95 blocks |
| Rate limited | 121 | 293 | 6,152 | 6,615 |
| Unsupported | 0 | 0 | 77 | 0 |
| Samples | 37,889 | 38,487 | 8,986 | 7,944 |
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.5points
- Latency+7.4
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +7.5, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+13.4points
- Latency+13.2
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +13.4, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+33.9points
- Latency+21.8
- Availability+10.7
- Head freshness+0.7
- Correctness+0.7
The parts add to +33.9, exactly — the score is a weighted sum, so it comes apart.