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
7d window · 2.6 days observed · generated 2026-08-27 11:42:24 UTC
| Metric | dRPC | NodeReal | Cloudflare |
|---|---|---|---|
| Rank | 3 | 4 | 9 |
| Score | 92.4 | 87.9 | 55.1 |
| Status | Excellent | Good | Degraded |
| Availability | 99.93% | 99.82% | 23.11% |
| p50 latency | 33.8 ms | 87.4 ms | 15.0 ms |
| p95 latency | 72.0 ms | 100.1 ms | 86.8 ms |
| p99 latency | 168.1 ms | 125.9 ms | 250.9 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.36 blocks | 0.35 blocks | no cohort |
| Rate limited | 628 | 0 | 96 |
| Unsupported | 0 | 0 | 3,003 |
| Samples | 100,460 | 100,423 | 101,961 |
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.5points
- Latency+4.5
- Availability+0.0
- Head freshness−0.0
- Correctness−0.0
The parts add to +4.5, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+37.3points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency+0.3
The parts add to +37.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.