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-27 22:08:04 UTC
| Metric | dRPC | NodeReal | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 4 | 6 | 8 |
| Score | 91.3 | 86.7 | 78.0 | 57.5 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.96% | 99.99% | 100.00% | 73.21% |
| p50 latency | 33.4 ms | 87.3 ms | 107.3 ms | 2024.4 ms |
| p95 latency | 69.3 ms | 99.9 ms | 192.8 ms | 6590.4 ms |
| p99 latency | 175.1 ms | 129.0 ms | 235.0 ms | 9196.2 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 96.63% |
| Head lag | 0.36 blocks | 0.34 blocks | 0.54 blocks | 0.95 blocks |
| Rate limited | 123 | 0 | 5,938 | 6,434 |
| Unsupported | 0 | 0 | 73 | 0 |
| Samples | 36,879 | 36,893 | 8,665 | 7,737 |
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.6points
- Latency+4.7
- Head freshness−0.0
- Availability−0.0
- Correctness+0.0
The parts add to +4.6, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+13.3points
- Latency+13.1
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +13.3, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+33.8points
- Latency+21.8
- Availability+10.7
- Head freshness+0.7
- Correctness+0.7
The parts add to +33.8, exactly — the score is a weighted sum, so it comes apart.