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-28 21:12:25 UTC
| Metric | dRPC | NodeReal | Merkle |
|---|---|---|---|
| Rank | 3 | 4 | 6 |
| Score | 88.1 | 82.0 | 70.1 |
| Status | Good | Good | Degraded |
| Availability | 99.99% | 100.00% | 100.00% |
| p50 latency | 35.6 ms | 87.2 ms | 108.9 ms |
| p95 latency | 69.0 ms | 99.4 ms | 198.8 ms |
| p99 latency | 177.3 ms | 120.0 ms | 241.7 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.37 blocks | 0.35 blocks | 0.44 blocks |
| Rate limited | 28 | 0 | 1,334 |
| Unsupported | 0 | 0 | 15 |
| Samples | 8,285 | 8,295 | 1,954 |
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
+6.2points
- Latency+6.2
- Head freshness−0.0
- Availability−0.0
- Correctness+0.0
The parts add to +6.2, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+18.0points
- Latency+18.0
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +18.0, exactly — the score is a weighted sum, so it comes apart.