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 22:34:46 UTC
| Metric | dRPC | Blast API | Merkle |
|---|---|---|---|
| Rank | 3 | 5 | 6 |
| Score | 87.9 | 77.7 | 70.8 |
| Status | Good | Good | Degraded |
| Availability | 100.00% | 100.00% | 100.00% |
| p50 latency | 33.8 ms | 105.3 ms | 105.1 ms |
| p95 latency | 64.4 ms | 120.1 ms | 181.9 ms |
| p99 latency | 204.6 ms | 139.1 ms | 231.6 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.46 blocks | 0.45 blocks | 0.56 blocks |
| Rate limited | 0 | 10 | 272 |
| Unsupported | 0 | 0 | 3 |
| Samples | 1,589 | 1,601 | 389 |
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
+10.2points
- Latency+10.2
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +10.2, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+17.2points
- Latency+17.0
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +17.2, exactly — the score is a weighted sum, so it comes apart.