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
7d window · 2.4 days observed · generated 2026-08-27 06:54:33 UTC
| Metric | dRPC | NodeReal | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 3 | 4 | 5 | 6 |
| Score | 92.9 | 88.2 | 85.4 | 78.8 |
| Status | Excellent | Good | Good | Good |
| Availability | 99.93% | 99.80% | 99.98% | 99.98% |
| p50 latency | 33.8 ms | 87.3 ms | 104.4 ms | 106.5 ms |
| p95 latency | 71.7 ms | 100.1 ms | 122.0 ms | 195.5 ms |
| p99 latency | 167.3 ms | 125.9 ms | 144.3 ms | 243.2 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 100.00% |
| Head lag | 0.36 blocks | 0.35 blocks | 0.42 blocks | 0.47 blocks |
| Rate limited | 591 | 0 | 1,046 | 15,157 |
| Unsupported | 0 | 0 | 0 | 183 |
| Samples | 92,810 | 92,782 | 93,809 | 21,793 |
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.7points
- Latency+4.7
- Availability+0.1
- Head freshness−0.0
- Correctness−0.0
The parts add to +4.7, exactly — the score is a weighted sum, so it comes apart.
dRPCvsBlast API
+7.5points
- Latency+7.4
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +7.5, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+14.2points
- Latency+14.0
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +14.2, exactly — the score is a weighted sum, so it comes apart.