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
1h window · 60 minutes observed · generated 2026-08-28 00:04:25 UTC
| Metric | dRPC | NodeReal | Blast API | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 4 | 5 | 9 |
| Score | 91.3 | 85.7 | 83.4 | 48.8 |
| Status | Excellent | Good | Good | Poor |
| Availability | 100.00% | 100.00% | 100.00% | 50.00% |
| p50 latency | 31.7 ms | 87.3 ms | 103.5 ms | 4375.0 ms |
| p95 latency | 61.1 ms | 98.9 ms | 119.7 ms | 9140.1 ms |
| p99 latency | 147.6 ms | 111.4 ms | 148.9 ms | 9140.1 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.40 blocks | 0.36 blocks | 0.45 blocks | 1.00 blocks |
| Rate limited | 2 | 0 | 0 | 256 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 1,569 | 1,567 | 1,594 | 315 |
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.6points
- Latency+5.6
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +5.6, exactly — the score is a weighted sum, so it comes apart.
dRPCvsBlast API
+7.9points
- Latency+7.9
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +7.9, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+42.4points
- Latency+21.7
- Availability+20.0
- Head freshness+0.7
- Correctness+0.0
The parts add to +42.4, exactly — the score is a weighted sum, so it comes apart.