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
1h window · 60 minutes observed · generated 2026-08-28 11:40:39 UTC
| Metric | dRPC | Blast API | Merkle |
|---|---|---|---|
| Rank | 3 | 5 | 6 |
| Score | 87.2 | 78.0 | 70.0 |
| Status | Good | Good | Degraded |
| Availability | 100.00% | 100.00% | 100.00% |
| p50 latency | 33.7 ms | 106.3 ms | 107.3 ms |
| p95 latency | 70.0 ms | 121.6 ms | 194.0 ms |
| p99 latency | 162.1 ms | 133.4 ms | 1194.0 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.35 blocks | 0.42 blocks | 0.58 blocks |
| Rate limited | 2 | 24 | 273 |
| Unsupported | 0 | 0 | 2 |
| Samples | 1,574 | 1,608 | 403 |
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
+9.3points
- Latency+9.2
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +9.3, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+17.2points
- Latency+17.0
- Head freshness+0.3
- Availability+0.0
- Correctness+0.0
The parts add to +17.2, exactly — the score is a weighted sum, so it comes apart.