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 09:09:01 UTC
| Metric | dRPC | NodeReal | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 4 | 6 | 9 |
| Score | 86.1 | 78.7 | 69.5 | 0.0 |
| Status | Good | Good | Degraded | Poor |
| Availability | 99.96% | 100.00% | 100.00% | 0.00% |
| p50 latency | 31.2 ms | 87.3 ms | 105.0 ms | 0.0 ms |
| p95 latency | 72.5 ms | 115.7 ms | 204.6 ms | 0.0 ms |
| p99 latency | 223.0 ms | 160.7 ms | 252.5 ms | 0.0 ms |
| Correctness | 99.99% | 100.00% | 100.00% | not measured |
| Head lag | 0.38 blocks | 0.34 blocks | 0.52 blocks | no cohort |
| Rate limited | 15 | 0 | 1,379 | 1,445 |
| Unsupported | 0 | 0 | 19 | 0 |
| Samples | 8,212 | 8,204 | 1,988 | 1,653 |
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
+7.3points
- Latency+7.4
- Head freshness−0.1
- Availability−0.0
- Correctness−0.0
The parts add to +7.3, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+16.5points
- Latency+16.4
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +16.5, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+86.1points
- Availability+40.0
- Correctness*+20.0
- Latency*+16.5
- Head freshness*+9.5
The parts add to +86.1, exactly — the score is a weighted sum, so it comes apart. Components marked * were measured for only one of the two; the other’s weight is spread across what it does have, which is why the two sides can carry different weights for the same row.