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
24h window · 24 hours observed · generated 2026-08-27 05:41:01 UTC
| Metric | dRPC | NodeReal | Blast API |
|---|---|---|---|
| Rank | 3 | 4 | 5 |
| Score | 91.0 | 86.5 | 84.0 |
| Status | Excellent | Good | Good |
| Availability | 99.92% | 100.00% | 99.98% |
| p50 latency | 34.1 ms | 87.1 ms | 104.8 ms |
| p95 latency | 69.7 ms | 99.8 ms | 121.5 ms |
| p99 latency | 172.0 ms | 124.2 ms | 143.6 ms |
| Correctness | 99.99% | 100.00% | 99.99% |
| Head lag | 0.38 blocks | 0.34 blocks | 0.41 blocks |
| Rate limited | 135 | 0 | 320 |
| Unsupported | 0 | 0 | 0 |
| Samples | 37,747 | 37,749 | 38,146 |
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
+4.5points
- Latency+4.5
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +4.5, exactly — the score is a weighted sum, so it comes apart.
dRPCvsBlast API
+7.0points
- Latency+7.0
- Head freshness+0.0
- Availability−0.0
- Correctness+0.0
The parts add to +7.0, exactly — the score is a weighted sum, so it comes apart.