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 10:35:38 UTC
| Metric | dRPC | NodeReal | 1RPC |
|---|---|---|---|
| Rank | 3 | 4 | 9 |
| Score | 87.7 | 80.8 | 0.0 |
| Status | Good | Good | Poor |
| Availability | 99.94% | 100.00% | 0.00% |
| p50 latency | 32.1 ms | 88.0 ms | 0.0 ms |
| p95 latency | 70.0 ms | 105.3 ms | 0.0 ms |
| p99 latency | 163.0 ms | 142.5 ms | 0.0 ms |
| Correctness | 99.99% | 100.00% | not measured |
| Head lag | 0.35 blocks | 0.35 blocks | no cohort |
| Rate limited | 43 | 0 | 1,558 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,912 | 8,919 | 1,784 |
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
+6.9points
- Latency+6.9
- Availability−0.0
- Head freshness−0.0
- Correctness−0.0
The parts add to +6.9, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+87.7points
- Availability+40.0
- Correctness*+20.0
- Latency*+18.2
- Head freshness*+9.6
The parts add to +87.7, 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.