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 15:09:26 UTC
| Metric | dRPC | NodeReal | Blast API |
|---|---|---|---|
| Rank | 3 | 4 | 5 |
| Score | 88.7 | 82.9 | 78.4 |
| Status | Good | Good | Good |
| Availability | 99.95% | 100.00% | 99.99% |
| p50 latency | 34.3 ms | 87.6 ms | 108.5 ms |
| p95 latency | 71.7 ms | 99.3 ms | 126.7 ms |
| p99 latency | 183.9 ms | 127.1 ms | 152.8 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.36 blocks | 0.33 blocks | 0.41 blocks |
| Rate limited | 30 | 0 | 45 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,220 | 8,215 | 8,353 |
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.8points
- Latency+5.9
- Head freshness−0.0
- Availability−0.0
- Correctness+0.0
The parts add to +5.8, exactly — the score is a weighted sum, so it comes apart.
dRPCvsBlast API
+10.3points
- Latency+10.3
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +10.3, exactly — the score is a weighted sum, so it comes apart.