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
24h window · 24 hours observed · generated 2026-08-28 11:56:07 UTC
| Metric | dRPC | NodeReal | Merkle |
|---|---|---|---|
| Rank | 3 | 4 | 6 |
| Score | 89.9 | 86.2 | 77.6 |
| Status | Good | Good | Good |
| Availability | 99.97% | 99.91% | 100.00% |
| p50 latency | 33.2 ms | 87.4 ms | 107.4 ms |
| p95 latency | 75.1 ms | 100.2 ms | 193.8 ms |
| p99 latency | 193.9 ms | 135.8 ms | 252.5 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.37 blocks | 0.34 blocks | 0.54 blocks |
| Rate limited | 74 | 0 | 6,223 |
| Unsupported | 0 | 0 | 77 |
| Samples | 38,153 | 38,117 | 9,090 |
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
+3.6points
- Latency+3.7
- Head freshness−0.0
- Availability+0.0
- Correctness−0.0
The parts add to +3.6, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+12.2points
- Latency+12.0
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +12.2, exactly — the score is a weighted sum, so it comes apart.