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 00:02:00 UTC
| Metric | dRPC | Blast API | 1RPC |
|---|---|---|---|
| Rank | 3 | 5 | 9 |
| Score | 91.4 | 83.8 | 33.3 |
| Status | Excellent | Good | Poor |
| Availability | 99.97% | 99.97% | 11.11% |
| p50 latency | 33.1 ms | 106.3 ms | 7517.0 ms |
| p95 latency | 68.9 ms | 123.6 ms | 8458.8 ms |
| p99 latency | 173.1 ms | 151.1 ms | 8458.8 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.36 blocks | 0.41 blocks | 1.00 blocks |
| Rate limited | 116 | 270 | 6,430 |
| Unsupported | 0 | 0 | 0 |
| Samples | 36,709 | 37,295 | 7,381 |
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
+7.6points
- Latency+7.5
- 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.
dRPCvs1RPC
+58.1points
- Availability+35.5
- Latency+21.8
- Head freshness+0.7
- Correctness−0.0
The parts add to +58.1, exactly — the score is a weighted sum, so it comes apart.