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-27 01:50:44 UTC
| Metric | dRPC | NodeReal | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 4 | 6 | 8 |
| Score | 89.8 | 86.1 | 77.6 | 58.7 |
| Status | Good | Good | Good | Degraded |
| Availability | 99.86% | 99.99% | 100.00% | 76.33% |
| p50 latency | 34.1 ms | 87.0 ms | 105.9 ms | 2024.4 ms |
| p95 latency | 73.6 ms | 99.3 ms | 193.5 ms | 6590.4 ms |
| p99 latency | 179.6 ms | 121.6 ms | 220.4 ms | 9196.2 ms |
| Correctness | 99.98% | 99.99% | 100.00% | 96.63% |
| Head lag | 0.39 blocks | 0.33 blocks | 0.51 blocks | 0.95 blocks |
| Rate limited | 33 | 0 | 1,475 | 1,597 |
| Unsupported | 0 | 0 | 17 | 0 |
| Samples | 9,310 | 9,307 | 2,111 | 2,193 |
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.1
- Availability−0.1
- 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.1
- Head freshness+0.1
- Availability−0.1
- Correctness−0.0
The parts add to +12.2, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+31.0points
- Latency+20.3
- Availability+9.4
- Correctness+0.7
- Head freshness+0.6
The parts add to +31.0, exactly — the score is a weighted sum, so it comes apart.