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
30d window · 4.1 days observed · generated 2026-08-28 22:20:34 UTC
| Metric | dRPC | NodeReal | Merkle |
|---|---|---|---|
| Rank | 3 | 4 | 6 |
| Score | 90.9 | 86.8 | 78.0 |
| Status | Excellent | Good | Good |
| Availability | 99.95% | 99.86% | 99.99% |
| p50 latency | 33.9 ms | 87.4 ms | 107.0 ms |
| p95 latency | 72.6 ms | 100.0 ms | 196.1 ms |
| p99 latency | 175.1 ms | 128.2 ms | 244.7 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.36 blocks | 0.35 blocks | 0.49 blocks |
| Rate limited | 765 | 0 | 25,446 |
| Unsupported | 0 | 0 | 305 |
| Samples | 155,668 | 155,579 | 36,756 |
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
+4.1points
- Latency+4.1
- Availability+0.0
- Head freshness−0.0
- Correctness−0.0
The parts add to +4.1, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+13.0points
- Latency+12.8
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +13.0, exactly — the score is a weighted sum, so it comes apart.