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
6h window · 6.0 hours observed · generated 2026-08-28 00:15:56 UTC
| Metric | dRPC | NodeReal | Blast API | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 4 | 5 | 9 |
| Score | 91.9 | 86.4 | 83.6 | 53.2 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.99% | 99.96% | 99.96% | 61.54% |
| p50 latency | 32.8 ms | 87.1 ms | 105.7 ms | 2668.5 ms |
| p95 latency | 64.1 ms | 99.0 ms | 122.8 ms | 8458.8 ms |
| p99 latency | 166.6 ms | 117.2 ms | 150.5 ms | 12423.1 ms |
| Correctness | 100.00% | 99.96% | 100.00% | 98.77% |
| Head lag | 0.36 blocks | 0.34 blocks | 0.41 blocks | 0.96 blocks |
| Rate limited | 11 | 0 | 19 | 1,403 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 8,382 | 8,381 | 8,523 | 1,739 |
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.
dRPCvsNodeReal
+5.5points
- Latency+5.5
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +5.5, exactly — the score is a weighted sum, so it comes apart.
dRPCvsBlast API
+8.3points
- Latency+8.2
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.3, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+38.6points
- Latency+22.3
- Availability+15.4
- Head freshness+0.7
- Correctness+0.2
The parts add to +38.6, exactly — the score is a weighted sum, so it comes apart.