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 16:10:07 UTC
| Metric | dRPC | NodeReal | Merkle |
|---|---|---|---|
| Rank | 3 | 4 | 7 |
| Score | 86.7 | 82.3 | 69.4 |
| Status | Good | Good | Degraded |
| Availability | 99.99% | 99.99% | 100.00% |
| p50 latency | 35.7 ms | 87.3 ms | 110.9 ms |
| p95 latency | 76.4 ms | 99.4 ms | 216.0 ms |
| p99 latency | 176.8 ms | 125.5 ms | 332.7 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.36 blocks | 0.35 blocks | 0.49 blocks |
| Rate limited | 42 | 0 | 1,352 |
| Unsupported | 0 | 0 | 14 |
| Samples | 8,222 | 8,234 | 1,918 |
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.4points
- Latency+4.4
- Head freshness−0.0
- Correctness+0.0
- Availability−0.0
The parts add to +4.4, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+17.3points
- Latency+17.2
- Head freshness+0.2
- Availability−0.0
- Correctness+0.0
The parts add to +17.3, exactly — the score is a weighted sum, so it comes apart.