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-28 17:12:46 UTC
| Metric | dRPC | Blast API | Merkle |
|---|---|---|---|
| Rank | 3 | 5 | 6 |
| Score | 89.1 | 83.5 | 77.4 |
| Status | Good | Good | Good |
| Availability | 99.98% | 99.97% | 100.00% |
| p50 latency | 33.5 ms | 105.4 ms | 107.2 ms |
| p95 latency | 78.3 ms | 121.9 ms | 196.4 ms |
| p99 latency | 192.9 ms | 145.0 ms | 265.9 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.37 blocks | 0.41 blocks | 0.52 blocks |
| Rate limited | 97 | 353 | 6,062 |
| Unsupported | 0 | 0 | 72 |
| Samples | 36,992 | 37,618 | 8,799 |
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
+5.6points
- Latency+5.5
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +5.6, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+11.7points
- Latency+11.5
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +11.7, exactly — the score is a weighted sum, so it comes apart.