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 13:21:45 UTC
| Metric | NodeReal | dRPC | Blast API |
|---|---|---|---|
| Rank | 3 | 4 | 5 |
| Score | 81.5 | 78.8 | 78.1 |
| Status | Good | Good | Good |
| Availability | 99.99% | 99.96% | 99.96% |
| p50 latency | 87.3 ms | 34.0 ms | 106.2 ms |
| p95 latency | 99.6 ms | 117.2 ms | 121.7 ms |
| p99 latency | 126.2 ms | 198.9 ms | 133.7 ms |
| Correctness | 99.99% | 99.99% | 99.98% |
| Head lag | 0.34 blocks | 0.37 blocks | 0.41 blocks |
| Rate limited | 0 | 18 | 175 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,549 | 8,544 | 8,692 |
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 NodeReal, the highest scorer of those selected.
NodeRealvsdRPC
+2.7points
- Latency+2.7
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +2.7, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsBlast API
+3.4points
- Latency+3.3
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +3.4, exactly — the score is a weighted sum, so it comes apart.