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
6h window · 6.0 hours observed · generated 2026-08-28 11:17:58 UTC
| Metric | dRPC | Blast API | 1RPC |
|---|---|---|---|
| Rank | 4 | 5 | 9 |
| Score | 78.3 | 78.3 | 0.0 |
| Status | Good | Good | Poor |
| Availability | 99.95% | 99.98% | 0.00% |
| p50 latency | 32.6 ms | 105.0 ms | 0.0 ms |
| p95 latency | 119.4 ms | 119.5 ms | 0.0 ms |
| p99 latency | 214.8 ms | 131.4 ms | 0.0 ms |
| Correctness | 99.99% | 99.99% | not measured |
| Head lag | 0.38 blocks | 0.42 blocks | no cohort |
| Rate limited | 21 | 265 | 1,475 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,441 | 8,584 | 1,695 |
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.
dRPCvsBlast API
+0.1points
- Head freshness+0.1
- Latency+0.0
- Availability−0.0
- Correctness+0.0
The parts add to +0.1, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+78.3points
- Availability+40.0
- Correctness*+20.0
- Head freshness*+9.5
- Latency*+8.8
The parts add to +78.3, exactly — the score is a weighted sum, so it comes apart. Components marked * were measured for only one of the two; the other’s weight is spread across what it does have, which is why the two sides can carry different weights for the same row.