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 21:30:05 UTC
| Metric | dRPC | Blast API | Merkle |
|---|---|---|---|
| Rank | 3 | 5 | 6 |
| Score | 88.1 | 78.0 | 70.1 |
| Status | Good | Good | Degraded |
| Availability | 99.99% | 99.99% | 100.00% |
| p50 latency | 35.5 ms | 108.1 ms | 108.9 ms |
| p95 latency | 68.7 ms | 124.7 ms | 198.8 ms |
| p99 latency | 177.5 ms | 142.3 ms | 241.7 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.37 blocks | 0.42 blocks | 0.44 blocks |
| Rate limited | 28 | 2 | 1,434 |
| Unsupported | 0 | 0 | 15 |
| Samples | 8,756 | 8,922 | 2,069 |
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.1points
- Latency+10.1
- Head freshness+0.1
- Correctness+0.0
- Availability+0.0
The parts add to +10.1, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+18.1points
- Latency+18.0
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +18.1, exactly — the score is a weighted sum, so it comes apart.