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-27 03:15:19 UTC
| Metric | dRPC | 1RPC | Cloudflare |
|---|---|---|---|
| Rank | 3 | 8 | 9 |
| Score | 90.6 | 58.7 | 56.0 |
| Status | Excellent | Degraded | Degraded |
| Availability | 99.94% | 76.33% | 23.19% |
| p50 latency | 33.2 ms | 2024.4 ms | 12.6 ms |
| p95 latency | 69.7 ms | 6590.4 ms | 69.4 ms |
| p99 latency | 167.2 ms | 9196.2 ms | 247.4 ms |
| Correctness | 99.99% | 96.63% | 100.00% |
| Head lag | 0.38 blocks | 0.95 blocks | no cohort |
| Rate limited | 27 | 1,438 | 6 |
| Unsupported | 0 | 0 | 247 |
| Samples | 8,381 | 2,008 | 8,519 |
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
+31.8points
- Latency+21.1
- Availability+9.4
- Correctness+0.7
- Head freshness+0.7
The parts add to +31.8, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+34.6points
- Availability+29.7
- Head freshness*+9.5
- Latency−2.4
- Correctness−2.2
The parts add to +34.6, 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.