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 11:42:44 UTC
| Metric | dRPC | NodeReal | Blast API | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 4 | 5 | 8 |
| Score | 90.4 | 86.4 | 83.7 | 58.2 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.91% | 100.00% | 99.99% | 74.93% |
| p50 latency | 34.2 ms | 87.2 ms | 105.6 ms | 2024.4 ms |
| p95 latency | 72.5 ms | 100.1 ms | 122.9 ms | 6590.4 ms |
| p99 latency | 172.9 ms | 128.3 ms | 147.8 ms | 9196.2 ms |
| Correctness | 99.99% | 100.00% | 100.00% | 96.63% |
| Head lag | 0.38 blocks | 0.34 blocks | 0.41 blocks | 0.95 blocks |
| Rate limited | 163 | 0 | 342 | 6,575 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 37,792 | 37,781 | 38,185 | 7,893 |
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
+4.0points
- Latency+4.1
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +4.0, exactly — the score is a weighted sum, so it comes apart.
dRPCvsBlast API
+6.7points
- Latency+6.7
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +6.7, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+32.3points
- Latency+20.9
- Availability+10.0
- Correctness+0.7
- Head freshness+0.7
The parts add to +32.3, exactly — the score is a weighted sum, so it comes apart.