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-27 12:04:34 UTC
| Metric | dRPC | NodeReal | Merkle |
|---|---|---|---|
| Rank | 3 | 4 | 6 |
| Score | 85.1 | 83.2 | 69.9 |
| Status | Good | Good | Degraded |
| Availability | 99.94% | 100.00% | 100.00% |
| p50 latency | 34.6 ms | 86.7 ms | 112.4 ms |
| p95 latency | 87.6 ms | 98.3 ms | 209.2 ms |
| p99 latency | 190.8 ms | 125.2 ms | 407.4 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.39 blocks | 0.34 blocks | 0.38 blocks |
| Rate limited | 5 | 0 | 248 |
| Unsupported | 0 | 0 | 1 |
| Samples | 1,577 | 1,575 | 349 |
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
+2.0points
- Latency+2.0
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +2.0, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+15.2points
- Latency+15.3
- Availability−0.0
- Head freshness−0.0
- Correctness+0.0
The parts add to +15.2, exactly — the score is a weighted sum, so it comes apart.