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
30d window · 2.8 days observed · generated 2026-08-27 16:08:50 UTC
| Metric | dRPC | NodeReal | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 3 | 4 | 5 | 6 |
| Score | 92.2 | 87.7 | 84.9 | 78.5 |
| Status | Excellent | Good | Good | Good |
| Availability | 99.93% | 99.83% | 99.98% | 99.98% |
| p50 latency | 33.8 ms | 87.4 ms | 105.0 ms | 106.7 ms |
| p95 latency | 71.9 ms | 100.0 ms | 122.5 ms | 195.9 ms |
| p99 latency | 169.6 ms | 126.3 ms | 147.0 ms | 243.3 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 100.00% |
| Head lag | 0.36 blocks | 0.35 blocks | 0.42 blocks | 0.48 blocks |
| Rate limited | 645 | 0 | 1,180 | 17,570 |
| Unsupported | 0 | 0 | 0 | 216 |
| Samples | 107,534 | 107,493 | 108,772 | 25,328 |
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.
dRPCvsNodeReal
+4.5points
- Latency+4.5
- Availability+0.0
- Head freshness−0.0
- Correctness−0.0
The parts add to +4.5, exactly — the score is a weighted sum, so it comes apart.
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.7points
- Latency+13.6
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +13.7, exactly — the score is a weighted sum, so it comes apart.