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 14:01:21 UTC
| Metric | dRPC | NodeReal | Blast API | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 4 | 5 | 9 |
| Score | 88.4 | 82.9 | 78.6 | 0.0 |
| Status | Good | Good | Good | Poor |
| Availability | 99.95% | 100.00% | 99.99% | 0.00% |
| p50 latency | 33.8 ms | 87.8 ms | 108.0 ms | 0.0 ms |
| p95 latency | 72.8 ms | 99.4 ms | 125.7 ms | 0.0 ms |
| p99 latency | 171.5 ms | 127.1 ms | 153.7 ms | 0.0 ms |
| Correctness | 100.00% | 100.00% | 100.00% | not measured |
| Head lag | 0.35 blocks | 0.33 blocks | 0.41 blocks | no cohort |
| Rate limited | 37 | 0 | 58 | 1,400 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 8,006 | 7,993 | 8,133 | 1,605 |
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
+5.5points
- Latency+5.6
- Head freshness−0.0
- Availability−0.0
- Correctness+0.0
The parts add to +5.5, exactly — the score is a weighted sum, so it comes apart.
dRPCvsBlast API
+9.9points
- Latency+9.8
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +9.9, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+88.4points
- Availability+40.0
- Correctness*+20.0
- Latency*+18.9
- Head freshness*+9.6
The parts add to +88.4, 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.