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
- PublicNode
- Tenderly
- dRPC
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- 1RPC
- Cloudflare
Side by side
1h window · 60 minutes observed · generated 2026-08-28 00:25:45 UTC
| Metric | dRPC | NodeReal | Cloudflare |
|---|---|---|---|
| Rank | 3 | 4 | 9 |
| Score | 91.3 | 85.9 | 56.2 |
| Status | Excellent | Good | Degraded |
| Availability | 100.00% | 100.00% | 23.36% |
| p50 latency | 31.6 ms | 87.5 ms | 12.6 ms |
| p95 latency | 61.6 ms | 98.8 ms | 64.3 ms |
| p99 latency | 150.1 ms | 110.8 ms | 124.5 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.40 blocks | 0.38 blocks | no cohort |
| Rate limited | 1 | 0 | 0 |
| Unsupported | 0 | 0 | 47 |
| Samples | 1,578 | 1,577 | 1,610 |
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.4points
- Latency+5.4
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +5.4, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+35.0points
- Availability+29.6
- Head freshness*+9.5
- Correctness−2.2
- Latency−1.9
The parts add to +35.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.