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 11:19:49 UTC
| Metric | dRPC | Blast API | 1RPC |
|---|---|---|---|
| Rank | 3 | 5 | 8 |
| Score | 89.8 | 83.6 | 58.4 |
| Status | Good | Good | Degraded |
| Availability | 99.97% | 99.97% | 75.33% |
| p50 latency | 33.1 ms | 106.1 ms | 1326.0 ms |
| p95 latency | 75.4 ms | 122.2 ms | 7406.7 ms |
| p99 latency | 194.4 ms | 148.7 ms | 9776.0 ms |
| Correctness | 99.99% | 99.99% | 96.96% |
| Head lag | 0.37 blocks | 0.41 blocks | 0.94 blocks |
| Rate limited | 74 | 391 | 6,474 |
| Unsupported | 0 | 0 | 0 |
| Samples | 37,190 | 37,786 | 7,778 |
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.2points
- Latency+6.2
- Head freshness+0.1
- Correctness−0.0
- Availability+0.0
The parts add to +6.2, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+31.4points
- Latency+20.3
- Availability+9.9
- Head freshness+0.7
- Correctness+0.6
The parts add to +31.4, exactly — the score is a weighted sum, so it comes apart.