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-28 01:29:00 UTC
| Metric | dRPC | NodeReal | Blast API |
|---|---|---|---|
| Rank | 3 | 4 | 5 |
| Score | 91.5 | 86.6 | 83.8 |
| Status | Excellent | Good | Good |
| Availability | 99.96% | 99.99% | 99.97% |
| p50 latency | 33.2 ms | 87.4 ms | 106.2 ms |
| p95 latency | 68.3 ms | 99.9 ms | 123.6 ms |
| p99 latency | 174.6 ms | 128.6 ms | 151.0 ms |
| Correctness | 99.99% | 99.99% | 99.99% |
| Head lag | 0.36 blocks | 0.34 blocks | 0.41 blocks |
| Rate limited | 112 | 0 | 295 |
| Unsupported | 0 | 0 | 0 |
| Samples | 37,424 | 37,417 | 38,026 |
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.8points
- Latency+4.9
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +4.8, exactly — the score is a weighted sum, so it comes apart.
dRPCvsBlast API
+7.6points
- Latency+7.6
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +7.6, exactly — the score is a weighted sum, so it comes apart.