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-27 07:33:47 UTC
| Metric | dRPC | Blast API | 1RPC |
|---|---|---|---|
| Rank | 3 | 5 | 9 |
| Score | 87.9 | 78.0 | 0.0 |
| Status | Good | Good | Poor |
| Availability | 99.95% | 99.99% | 0.00% |
| p50 latency | 31.3 ms | 103.7 ms | 0.0 ms |
| p95 latency | 63.4 ms | 117.7 ms | 0.0 ms |
| p99 latency | 157.3 ms | 145.3 ms | 0.0 ms |
| Correctness | 99.99% | 99.99% | not measured |
| Head lag | 0.37 blocks | 0.42 blocks | no cohort |
| Rate limited | 35 | 90 | 1,549 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,855 | 9,002 | 1,776 |
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
+9.8points
- Latency+9.8
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +9.8, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+87.9points
- Availability+40.0
- Correctness*+20.0
- Latency*+18.3
- Head freshness*+9.5
The parts add to +87.9, 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.