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
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-28 21:12:25 UTC
| Metric | Tenderly | PublicNode | Cloudflare |
|---|---|---|---|
| Rank | 1 | 2 | 8 |
| Score | 99.4 | 97.9 | 48.5 |
| Status | Excellent | Excellent | Poor |
| Availability | 99.99% | 99.99% | 23.15% |
| p50 latency | 19.2 ms | 22.5 ms | 14.0 ms |
| p95 latency | 33.5 ms | 38.4 ms | 88.2 ms |
| p99 latency | 71.4 ms | 81.5 ms | 171.3 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.50 blocks | 0.50 blocks | no cohort |
| Rate limited | 0 | 0 | 5 |
| Unsupported | 0 | 0 | 254 |
| Samples | 8,445 | 8,495 | 8,450 |
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 Tenderly, the highest scorer of those selected.
TenderlyvsPublicNode
+1.5points
- Latency+1.5
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +1.5, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+50.9points
- Availability+29.7
- Latency+14.0
- Head freshness*+9.4
- Correctness−2.2
The parts add to +50.9, 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.