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 09:13:09 UTC
| Metric | dRPC | NodeReal | Blast API |
|---|---|---|---|
| Rank | 3 | 4 | 5 |
| Score | 90.7 | 86.4 | 83.8 |
| Status | Excellent | Good | Good |
| Availability | 99.91% | 100.00% | 99.99% |
| p50 latency | 34.2 ms | 87.2 ms | 105.3 ms |
| p95 latency | 71.2 ms | 100.3 ms | 122.4 ms |
| p99 latency | 176.6 ms | 128.9 ms | 146.1 ms |
| Correctness | 99.99% | 100.00% | 99.99% |
| Head lag | 0.38 blocks | 0.34 blocks | 0.42 blocks |
| Rate limited | 154 | 0 | 350 |
| Unsupported | 0 | 0 | 0 |
| Samples | 36,997 | 36,999 | 37,380 |
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.2points
- Latency+4.3
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +4.2, exactly — the score is a weighted sum, so it comes apart.
dRPCvsBlast API
+6.8points
- Latency+6.8
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +6.8, exactly — the score is a weighted sum, so it comes apart.