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-27 12:17:12 UTC
| Metric | dRPC | Blast API | 1RPC |
|---|---|---|---|
| Rank | 3 | 5 | 8 |
| Score | 90.3 | 83.7 | 58.0 |
| Status | Excellent | Good | Degraded |
| Availability | 99.91% | 99.99% | 74.55% |
| p50 latency | 34.2 ms | 105.6 ms | 2024.4 ms |
| p95 latency | 73.2 ms | 122.8 ms | 6590.4 ms |
| p99 latency | 173.1 ms | 148.8 ms | 9196.2 ms |
| Correctness | 99.99% | 100.00% | 96.63% |
| Head lag | 0.38 blocks | 0.41 blocks | 0.95 blocks |
| Rate limited | 161 | 331 | 6,461 |
| Unsupported | 0 | 0 | 0 |
| Samples | 37,108 | 37,501 | 7,762 |
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
+6.6points
- Latency+6.6
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +6.6, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+32.3points
- Latency+20.8
- Availability+10.1
- Correctness+0.7
- Head freshness+0.7
The parts add to +32.3, exactly — the score is a weighted sum, so it comes apart.