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 15:48:18 UTC
| Metric | dRPC | NodeReal | Blast API |
|---|---|---|---|
| Rank | 3 | 4 | 5 |
| Score | 89.4 | 86.1 | 83.6 |
| Status | Good | Good | Good |
| Availability | 99.98% | 99.90% | 99.97% |
| p50 latency | 33.4 ms | 87.3 ms | 105.7 ms |
| p95 latency | 77.2 ms | 100.1 ms | 121.9 ms |
| p99 latency | 191.2 ms | 135.2 ms | 146.6 ms |
| Correctness | 99.99% | 99.99% | 99.99% |
| Head lag | 0.37 blocks | 0.34 blocks | 0.41 blocks |
| Rate limited | 89 | 0 | 373 |
| Unsupported | 0 | 0 | 0 |
| Samples | 37,951 | 37,911 | 38,583 |
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
+3.3points
- Latency+3.3
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +3.3, exactly — the score is a weighted sum, so it comes apart.
dRPCvsBlast API
+5.8points
- Latency+5.7
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +5.8, exactly — the score is a weighted sum, so it comes apart.