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
24h window · 24 hours observed · generated 2026-08-26 21:10:42 UTC
| Metric | dRPC | Blast API | Merkle |
|---|---|---|---|
| Rank | 3 | 5 | 6 |
| Score | 91.5 | 84.2 | 78.0 |
| Status | Excellent | Good | Good |
| Availability | 99.94% | 99.98% | 100.00% |
| p50 latency | 34.1 ms | 104.1 ms | 106.8 ms |
| p95 latency | 67.9 ms | 120.6 ms | 195.8 ms |
| p99 latency | 165.4 ms | 138.3 ms | 241.2 ms |
| Correctness | 99.99% | 99.98% | 100.00% |
| Head lag | 0.37 blocks | 0.42 blocks | 0.46 blocks |
| Rate limited | 112 | 363 | 6,073 |
| Unsupported | 0 | 0 | 78 |
| Samples | 36,965 | 37,384 | 8,780 |
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
+7.3points
- Latency+7.2
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +7.3, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+13.4points
- Latency+13.3
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +13.4, exactly — the score is a weighted sum, so it comes apart.