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
- NodeReal
- dRPC
- Blast API
- Merkle
- MEV Blocker
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-28 11:54:49 UTC
| Metric | Tenderly | NodeReal | Cloudflare |
|---|---|---|---|
| Rank | 1 | 3 | 8 |
| Score | 99.4 | 79.9 | 48.6 |
| Status | Excellent | Good | Poor |
| Availability | 99.99% | 100.00% | 23.17% |
| p50 latency | 18.9 ms | 87.6 ms | 12.9 ms |
| p95 latency | 32.8 ms | 109.0 ms | 84.7 ms |
| p99 latency | 60.8 ms | 160.5 ms | 134.6 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.34 blocks | no cohort |
| Rate limited | 0 | 0 | 6 |
| Unsupported | 0 | 0 | 283 |
| Samples | 9,580 | 9,426 | 9,565 |
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.
TenderlyvsNodeReal
+19.5points
- Latency+19.6
- Head freshness−0.2
- Availability−0.0
- Correctness−0.0
The parts add to +19.5, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+50.8points
- Availability+29.7
- Latency+13.9
- Head freshness*+9.4
- Correctness−2.2
The parts add to +50.8, 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.