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
1h window · 60 minutes observed · generated 2026-08-27 00:43:05 UTC
| Metric | dRPC | NodeReal | Cloudflare |
|---|---|---|---|
| Rank | 3 | 4 | 9 |
| Score | 90.8 | 86.1 | 55.6 |
| Status | Excellent | Good | Degraded |
| Availability | 99.94% | 100.00% | 23.28% |
| p50 latency | 33.7 ms | 87.2 ms | 11.4 ms |
| p95 latency | 66.9 ms | 98.5 ms | 69.8 ms |
| p99 latency | 159.7 ms | 122.4 ms | 134.1 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.37 blocks | 0.33 blocks | no cohort |
| Rate limited | 4 | 0 | 6 |
| Unsupported | 0 | 0 | 46 |
| Samples | 1,576 | 1,575 | 1,602 |
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.6points
- Latency+4.7
- Head freshness−0.0
- Availability−0.0
- Correctness+0.0
The parts add to +4.6, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+35.2points
- Availability+29.6
- Head freshness*+9.5
- Correctness−2.2
- Latency−1.8
The parts add to +35.2, 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.