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
- Merkle
- MEV Blocker
- 1RPC
- Cloudflare
Side by side
24h window · 24 hours observed · generated 2026-08-28 18:44:48 UTC
| Metric | dRPC | NodeReal | Cloudflare |
|---|---|---|---|
| Rank | 3 | 4 | 9 |
| Score | 89.2 | 86.0 | 53.2 |
| Status | Good | Good | Degraded |
| Availability | 99.98% | 99.90% | 23.13% |
| p50 latency | 33.7 ms | 87.3 ms | 13.3 ms |
| p95 latency | 77.2 ms | 100.2 ms | 84.0 ms |
| p99 latency | 189.8 ms | 135.4 ms | 144.0 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.37 blocks | 0.35 blocks | no cohort |
| Rate limited | 100 | 0 | 21 |
| Unsupported | 0 | 0 | 1,132 |
| Samples | 37,837 | 37,812 | 38,506 |
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
+3.3points
- Latency+3.2
- Availability+0.0
- Head freshness−0.0
- Correctness+0.0
The parts add to +3.3, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+36.0points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency−1.0
The parts add to +36.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.