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 09:48:04 UTC
| Metric | dRPC | NodeReal | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 3 | 4 | 5 | 6 |
| Score | 88.1 | 80.6 | 78.1 | 70.1 |
| Status | Good | Good | Good | Degraded |
| Availability | 99.93% | 100.00% | 99.99% | 100.00% |
| p50 latency | 31.6 ms | 87.7 ms | 105.1 ms | 105.1 ms |
| p95 latency | 66.3 ms | 104.5 ms | 120.8 ms | 194.3 ms |
| p99 latency | 160.2 ms | 139.7 ms | 148.5 ms | 228.8 ms |
| Correctness | 99.99% | 100.00% | 99.99% | 100.00% |
| Head lag | 0.35 blocks | 0.36 blocks | 0.41 blocks | 0.60 blocks |
| Rate limited | 40 | 0 | 127 | 1,478 |
| Unsupported | 0 | 0 | 0 | 18 |
| Samples | 9,238 | 9,251 | 9,379 | 2,161 |
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
+7.5points
- Latency+7.5
- Availability−0.0
- Head freshness+0.0
- Correctness−0.0
The parts add to +7.5, exactly — the score is a weighted sum, so it comes apart.
dRPCvsBlast API
+9.9points
- Latency+9.9
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +9.9, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+18.0points
- Latency+17.7
- Head freshness+0.3
- Availability−0.0
- Correctness−0.0
The parts add to +18.0, exactly — the score is a weighted sum, so it comes apart.