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 12:26:26 UTC
| Metric | dRPC | Blast API | Merkle |
|---|---|---|---|
| Rank | 4 | 5 | 6 |
| Score | 78.6 | 78.2 | 69.5 |
| Status | Good | Good | Degraded |
| Availability | 99.97% | 99.96% | 100.00% |
| p50 latency | 33.5 ms | 105.7 ms | 107.4 ms |
| p95 latency | 118.2 ms | 120.6 ms | 202.7 ms |
| p99 latency | 209.5 ms | 132.5 ms | 232.6 ms |
| Correctness | 99.99% | 99.98% | 100.00% |
| Head lag | 0.37 blocks | 0.42 blocks | 0.58 blocks |
| Rate limited | 18 | 265 | 1,408 |
| Unsupported | 0 | 0 | 15 |
| Samples | 8,664 | 8,809 | 2,020 |
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
+0.4points
- Latency+0.3
- Head freshness+0.1
- Correctness+0.0
- Availability+0.0
The parts add to +0.4, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+9.1points
- Latency+8.9
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +9.1, exactly — the score is a weighted sum, so it comes apart.