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
1h window · 60 minutes observed · generated 2026-08-28 14:26:24 UTC
| Metric | dRPC | NodeReal | Blast API |
|---|---|---|---|
| Rank | 3 | 4 | 5 |
| Score | 86.7 | 84.1 | 80.5 |
| Status | Good | Good | Good |
| Availability | 100.00% | 100.00% | 100.00% |
| p50 latency | 37.9 ms | 87.4 ms | 108.5 ms |
| p95 latency | 83.0 ms | 98.7 ms | 124.2 ms |
| p99 latency | 184.0 ms | 114.3 ms | 137.9 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.37 blocks | 0.37 blocks | 0.43 blocks |
| Rate limited | 4 | 0 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 1,577 | 1,576 | 1,604 |
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
+2.6points
- Latency+2.6
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +2.6, exactly — the score is a weighted sum, so it comes apart.
dRPCvsBlast API
+6.2points
- Latency+6.1
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +6.2, exactly — the score is a weighted sum, so it comes apart.