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 07:25:47 UTC
| Metric | dRPC | NodeReal | Merkle |
|---|---|---|---|
| Rank | 3 | 4 | 6 |
| Score | 87.9 | 79.9 | 70.0 |
| Status | Good | Good | Degraded |
| Availability | 99.95% | 100.00% | 100.00% |
| p50 latency | 31.3 ms | 87.4 ms | 105.1 ms |
| p95 latency | 63.3 ms | 105.3 ms | 192.8 ms |
| p99 latency | 157.4 ms | 142.0 ms | 268.8 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.37 blocks | 0.35 blocks | 0.58 blocks |
| Rate limited | 34 | 0 | 1,391 |
| Unsupported | 0 | 0 | 15 |
| Samples | 8,641 | 8,666 | 1,965 |
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
+8.0points
- Latency+8.0
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +8.0, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+17.8points
- Latency+17.6
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +17.8, exactly — the score is a weighted sum, so it comes apart.