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
30d window · 2.6 days observed · generated 2026-08-27 10:07:35 UTC
| Metric | dRPC | NodeReal | Blast API | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 4 | 5 | 8 |
| Score | 92.6 | 88.0 | 85.2 | 62.5 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.93% | 99.81% | 99.98% | 85.27% |
| p50 latency | 33.8 ms | 87.4 ms | 104.6 ms | 225.7 ms |
| p95 latency | 71.9 ms | 100.1 ms | 122.0 ms | 4391.3 ms |
| p99 latency | 167.7 ms | 125.9 ms | 145.5 ms | 7602.5 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 97.48% |
| Head lag | 0.36 blocks | 0.35 blocks | 0.42 blocks | 0.91 blocks |
| Rate limited | 616 | 0 | 1,131 | 17,097 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 97,941 | 97,910 | 99,023 | 20,993 |
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.6
- Availability+0.0
- Head freshness−0.0
- Correctness−0.0
The parts add to +4.6, exactly — the score is a weighted sum, so it comes apart.
dRPCvsBlast API
+7.3points
- Latency+7.3
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +7.3, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+30.1points
- Latency+23.1
- Availability+5.9
- Head freshness+0.6
- Correctness+0.5
The parts add to +30.1, exactly — the score is a weighted sum, so it comes apart.