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 07:57:53 UTC
| Metric | dRPC | NodeReal | Blast API |
|---|---|---|---|
| Rank | 3 | 4 | 5 |
| Score | 87.8 | 80.0 | 78.0 |
| Status | Good | Good | Good |
| Availability | 99.96% | 100.00% | 99.99% |
| p50 latency | 31.3 ms | 87.4 ms | 103.8 ms |
| p95 latency | 63.8 ms | 104.4 ms | 118.0 ms |
| p99 latency | 157.1 ms | 140.0 ms | 145.3 ms |
| Correctness | 99.99% | 100.00% | 99.99% |
| Head lag | 0.37 blocks | 0.35 blocks | 0.42 blocks |
| Rate limited | 37 | 0 | 109 |
| Unsupported | 0 | 0 | 0 |
| Samples | 9,497 | 9,521 | 9,648 |
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
+7.7points
- Latency+7.8
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +7.7, exactly — the score is a weighted sum, so it comes apart.
dRPCvsBlast API
+9.7points
- Latency+9.7
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +9.7, exactly — the score is a weighted sum, so it comes apart.