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-26 10:46:00 UTC
| Metric | dRPC | NodeReal | Cloudflare |
|---|---|---|---|
| Rank | 2 | 3 | 9 |
| Score | 93.8 | 88.5 | 55.6 |
| Status | Excellent | Good | Degraded |
| Availability | 99.96% | 99.98% | 23.10% |
| p50 latency | 34.2 ms | 87.5 ms | 15.4 ms |
| p95 latency | 69.9 ms | 99.9 ms | 88.0 ms |
| p99 latency | 167.5 ms | 124.7 ms | 260.3 ms |
| Correctness | 99.99% | 99.98% | 100.00% |
| Head lag | 0.35 blocks | 0.35 blocks | no cohort |
| Rate limited | 91 | 0 | 9 |
| Unsupported | 0 | 0 | 1,141 |
| Samples | 37,922 | 37,896 | 38,513 |
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.3points
- Latency+5.3
- Availability−0.0
- Head freshness+0.0
- Correctness+0.0
The parts add to +5.3, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+38.1points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency+1.1
The parts add to +38.1, 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.