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 · 3.8 days observed · generated 2026-08-28 14:42:04 UTC
| Metric | dRPC | Blast API | 1RPC |
|---|---|---|---|
| Rank | 3 | 5 | 8 |
| Score | 91.0 | 84.2 | 61.7 |
| Status | Excellent | Good | Degraded |
| Availability | 99.94% | 99.98% | 83.16% |
| p50 latency | 33.7 ms | 105.1 ms | 265.3 ms |
| p95 latency | 72.7 ms | 122.2 ms | 4975.4 ms |
| p99 latency | 174.6 ms | 146.7 ms | 8455.9 ms |
| Correctness | 99.99% | 99.99% | 97.38% |
| Head lag | 0.36 blocks | 0.42 blocks | 0.91 blocks |
| Rate limited | 711 | 1,545 | 25,034 |
| Unsupported | 0 | 0 | 0 |
| Samples | 143,498 | 145,320 | 30,448 |
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.8points
- Latency+6.7
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +6.8, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+29.3points
- Latency+21.5
- Availability+6.7
- Head freshness+0.6
- Correctness+0.5
The parts add to +29.3, exactly — the score is a weighted sum, so it comes apart.