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
- Tenderly
- PublicNode
- dRPC
- NodeReal
- Blast API
- MEV Blocker
- Merkle
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-28 16:09:28 UTC
| Metric | dRPC | NodeReal | Cloudflare |
|---|---|---|---|
| Rank | 3 | 4 | 8 |
| Score | 86.7 | 82.3 | 47.3 |
| Status | Good | Good | Poor |
| Availability | 99.99% | 99.99% | 23.11% |
| p50 latency | 35.8 ms | 87.3 ms | 14.1 ms |
| p95 latency | 76.3 ms | 99.4 ms | 96.1 ms |
| p99 latency | 176.2 ms | 125.6 ms | 154.7 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.36 blocks | 0.35 blocks | no cohort |
| Rate limited | 42 | 0 | 0 |
| Unsupported | 0 | 0 | 247 |
| Samples | 8,201 | 8,217 | 8,362 |
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.4points
- Latency+4.4
- Head freshness−0.0
- Correctness+0.0
- Availability−0.0
The parts add to +4.4, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+39.4points
- Availability+29.7
- Head freshness*+9.6
- Latency+2.3
- Correctness−2.2
The parts add to +39.4, 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.