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 18:40:37 UTC
| Metric | dRPC | Blast API | Merkle |
|---|---|---|---|
| Rank | 3 | 5 | 6 |
| Score | 86.4 | 78.1 | 70.0 |
| Status | Good | Good | Degraded |
| Availability | 99.98% | 99.99% | 100.00% |
| p50 latency | 36.5 ms | 108.6 ms | 109.0 ms |
| p95 latency | 77.5 ms | 125.6 ms | 201.2 ms |
| p99 latency | 184.3 ms | 143.0 ms | 293.9 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.35 blocks | 0.41 blocks | 0.39 blocks |
| Rate limited | 57 | 1 | 1,500 |
| Unsupported | 0 | 0 | 17 |
| Samples | 9,037 | 9,204 | 2,130 |
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.4points
- Latency+8.3
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +8.4, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+16.4points
- Latency+16.4
- Head freshness+0.0
- Availability−0.0
- Correctness+0.0
The parts add to +16.4, exactly — the score is a weighted sum, so it comes apart.