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
30d window · 47 hours observed · generated 2026-08-26 19:44:16 UTC
| Metric | dRPC | 1RPC | Cloudflare |
|---|---|---|---|
| Rank | 2 | 8 | 9 |
| Score | 93.6 | 63.9 | 55.3 |
| Status | Excellent | Degraded | Degraded |
| Availability | 99.94% | 88.60% | 23.09% |
| p50 latency | 34.0 ms | 189.3 ms | 15.4 ms |
| p95 latency | 72.5 ms | 2922.0 ms | 91.3 ms |
| p99 latency | 167.8 ms | 6561.8 ms | 254.2 ms |
| Correctness | 99.99% | 97.72% | 100.00% |
| Head lag | 0.36 blocks | 0.90 blocks | no cohort |
| Rate limited | 526 | 13,112 | 60 |
| Unsupported | 0 | 0 | 2,243 |
| Samples | 75,009 | 16,069 | 76,078 |
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.
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.
dRPCvsCloudflare
+38.3points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency+1.2
The parts add to +38.3, exactly — the score is a weighted sum, so it comes apart. Components marked * were measured for only one of the two; the other’s weight is spread across what it does have, which is why the two sides can carry different weights for the same row.