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
7d window · 2.0 days observed · generated 2026-08-26 20:53:29 UTC
| Metric | dRPC | Blast API | 1RPC |
|---|---|---|---|
| Rank | 2 | 5 | 8 |
| Score | 93.6 | 85.6 | 63.9 |
| Status | Excellent | Good | Degraded |
| Availability | 99.93% | 99.98% | 88.60% |
| p50 latency | 34.1 ms | 104.6 ms | 189.3 ms |
| p95 latency | 72.9 ms | 122.5 ms | 2922.0 ms |
| p99 latency | 168.3 ms | 144.6 ms | 6561.8 ms |
| Correctness | 99.99% | 99.99% | 97.72% |
| Head lag | 0.36 blocks | 0.42 blocks | 0.90 blocks |
| Rate limited | 532 | 915 | 13,423 |
| Unsupported | 0 | 0 | 0 |
| Samples | 76,848 | 77,642 | 16,424 |
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
+8.0points
- Latency+7.9
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +8.0, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+29.6points
- Latency+24.0
- Availability+4.5
- Head freshness+0.6
- Correctness+0.5
The parts add to +29.6, exactly — the score is a weighted sum, so it comes apart.