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 · 2.1 days observed · generated 2026-08-26 23:26:45 UTC
| Metric | dRPC | NodeReal | Cloudflare |
|---|---|---|---|
| Rank | 2 | 4 | 9 |
| Score | 93.7 | 88.9 | 55.8 |
| Status | Excellent | Good | Degraded |
| Availability | 99.93% | 99.77% | 23.09% |
| p50 latency | 34.1 ms | 87.4 ms | 15.4 ms |
| p95 latency | 72.7 ms | 99.9 ms | 90.4 ms |
| p99 latency | 169.2 ms | 123.9 ms | 255.0 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.36 blocks | 0.35 blocks | no cohort |
| Rate limited | 547 | 0 | 71 |
| Unsupported | 0 | 0 | 2,420 |
| Samples | 80,916 | 80,862 | 82,084 |
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.8points
- Latency+4.7
- Availability+0.1
- Head freshness−0.0
- Correctness−0.0
The parts add to +4.8, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+38.0points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency+0.9
The parts add to +38.0, 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.