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
6h window · 6.0 hours observed · generated 2026-08-27 12:54:03 UTC
| Metric | dRPC | NodeReal | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 3 | 4 | 5 | 6 |
| Score | 87.3 | 82.5 | 78.6 | 69.9 |
| Status | Good | Good | Good | Degraded |
| Availability | 99.95% | 100.00% | 100.00% | 100.00% |
| p50 latency | 33.2 ms | 87.8 ms | 107.2 ms | 107.3 ms |
| p95 latency | 75.7 ms | 99.8 ms | 124.5 ms | 202.1 ms |
| p99 latency | 174.2 ms | 123.3 ms | 152.8 ms | 231.3 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.35 blocks | 0.34 blocks | 0.40 blocks | 0.51 blocks |
| Rate limited | 47 | 0 | 108 | 1,561 |
| Unsupported | 0 | 0 | 0 | 19 |
| Samples | 9,409 | 9,396 | 9,558 | 2,299 |
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.8points
- Latency+4.8
- Availability−0.0
- Head freshness−0.0
- Correctness+0.0
The parts add to +4.8, exactly — the score is a weighted sum, so it comes apart.
dRPCvsBlast API
+8.7points
- Latency+8.7
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +8.7, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+17.3points
- Latency+17.2
- Head freshness+0.2
- Availability−0.0
- Correctness+0.0
The parts add to +17.3, exactly — the score is a weighted sum, so it comes apart.