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 22:12:10 UTC
| Metric | dRPC | Blast API | Merkle |
|---|---|---|---|
| Rank | 3 | 5 | 6 |
| Score | 88.4 | 78.1 | 69.9 |
| Status | Good | Good | Degraded |
| Availability | 99.99% | 99.99% | 100.00% |
| p50 latency | 35.1 ms | 107.4 ms | 108.2 ms |
| p95 latency | 67.2 ms | 123.5 ms | 201.2 ms |
| p99 latency | 175.1 ms | 139.8 ms | 241.7 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.39 blocks | 0.43 blocks | 0.46 blocks |
| Rate limited | 13 | 4 | 1,343 |
| Unsupported | 0 | 0 | 13 |
| Samples | 8,286 | 8,435 | 1,962 |
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.3points
- Latency+10.2
- Head freshness+0.0
- Correctness+0.0
- Availability+0.0
The parts add to +10.3, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+18.5points
- Latency+18.4
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +18.5, exactly — the score is a weighted sum, so it comes apart.