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
1h window · 60 minutes observed · generated 2026-08-28 11:55:39 UTC
| Metric | dRPC | NodeReal | Merkle |
|---|---|---|---|
| Rank | 3 | 4 | 6 |
| Score | 87.2 | 81.5 | 69.8 |
| Status | Good | Good | Degraded |
| Availability | 100.00% | 100.00% | 100.00% |
| p50 latency | 33.8 ms | 87.9 ms | 105.0 ms |
| p95 latency | 69.9 ms | 99.0 ms | 196.1 ms |
| p99 latency | 164.6 ms | 125.4 ms | 238.8 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.35 blocks | 0.35 blocks | 0.65 blocks |
| Rate limited | 0 | 0 | 260 |
| Unsupported | 0 | 0 | 2 |
| Samples | 1,573 | 1,587 | 387 |
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
+5.8points
- Latency+5.8
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +5.8, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+17.4points
- Latency+17.1
- Head freshness+0.3
- Availability+0.0
- Correctness+0.0
The parts add to +17.4, exactly — the score is a weighted sum, so it comes apart.