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-28 00:03:18 UTC
| Metric | dRPC | NodeReal | Blast API |
|---|---|---|---|
| Rank | 3 | 4 | 5 |
| Score | 92.0 | 86.4 | 83.6 |
| Status | Excellent | Good | Good |
| Availability | 99.99% | 99.96% | 99.96% |
| p50 latency | 32.8 ms | 87.1 ms | 105.8 ms |
| p95 latency | 64.0 ms | 99.0 ms | 122.9 ms |
| p99 latency | 166.0 ms | 117.4 ms | 150.6 ms |
| Correctness | 100.00% | 99.96% | 100.00% |
| Head lag | 0.36 blocks | 0.35 blocks | 0.42 blocks |
| Rate limited | 11 | 0 | 19 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,048 | 8,042 | 8,181 |
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.5
- 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
+8.3points
- Latency+8.3
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.3, exactly — the score is a weighted sum, so it comes apart.