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 01:23:24 UTC
| Metric | dRPC | NodeReal | Blast API | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 4 | 5 | 8 |
| Score | 91.2 | 85.7 | 83.2 | 61.4 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.87% | 100.00% | 99.94% | 85.37% |
| p50 latency | 32.9 ms | 87.5 ms | 103.4 ms | 1296.5 ms |
| p95 latency | 60.7 ms | 98.1 ms | 119.3 ms | 5509.5 ms |
| p99 latency | 186.6 ms | 116.3 ms | 145.3 ms | 5816.5 ms |
| Correctness | 99.87% | 100.00% | 99.94% | 92.11% |
| Head lag | 0.39 blocks | 0.31 blocks | 0.41 blocks | 1.00 blocks |
| Rate limited | 2 | 0 | 21 | 337 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 1,566 | 1,569 | 1,609 | 416 |
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.7
- Head freshness−0.1
- Availability−0.1
- Correctness−0.0
The parts add to +5.6, exactly — the score is a weighted sum, so it comes apart.
dRPCvsBlast API
+8.1points
- Latency+8.1
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +8.1, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+29.8points
- Latency+21.8
- Availability+5.8
- Correctness+1.6
- Head freshness+0.7
The parts add to +29.8, exactly — the score is a weighted sum, so it comes apart.