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 10:14:03 UTC
| Metric | dRPC | Blast API | Merkle |
|---|---|---|---|
| Rank | 3 | 5 | 6 |
| Score | 90.0 | 83.7 | 77.7 |
| Status | Good | Good | Good |
| Availability | 99.97% | 99.97% | 100.00% |
| p50 latency | 33.2 ms | 106.2 ms | 107.5 ms |
| p95 latency | 75.1 ms | 122.4 ms | 193.5 ms |
| p99 latency | 195.3 ms | 149.2 ms | 252.5 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.37 blocks | 0.41 blocks | 0.53 blocks |
| Rate limited | 76 | 351 | 6,046 |
| Unsupported | 0 | 0 | 75 |
| Samples | 37,048 | 37,637 | 8,827 |
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
+6.3points
- Latency+6.2
- Head freshness+0.1
- Correctness−0.0
- Availability−0.0
The parts add to +6.3, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+12.3points
- Latency+12.1
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +12.3, exactly — the score is a weighted sum, so it comes apart.