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
- MEV Blocker
- Merkle
- Cloudflare
- 1RPC
Side by side
1h window · 60 minutes observed · generated 2026-08-28 09:13:40 UTC
| Metric | Tenderly | NodeReal | Cloudflare |
|---|---|---|---|
| Rank | 1 | 3 | 8 |
| Score | 99.4 | 81.5 | 47.4 |
| Status | Excellent | Good | Poor |
| Availability | 99.94% | 100.00% | 23.43% |
| p50 latency | 18.6 ms | 86.3 ms | 13.5 ms |
| p95 latency | 33.0 ms | 99.5 ms | 91.8 ms |
| p99 latency | 56.3 ms | 126.1 ms | 131.8 ms |
| Correctness | 99.94% | 100.00% | 100.00% |
| Head lag | 0.46 blocks | 0.35 blocks | no cohort |
| Rate limited | 0 | 0 | 0 |
| Unsupported | 0 | 0 | 48 |
| Samples | 1,607 | 1,588 | 1,605 |
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
+17.9points
- Latency+18.0
- Head freshness−0.1
- Availability−0.0
- Correctness−0.0
The parts add to +17.9, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+52.0points
- Availability+29.6
- Latency+15.2
- Head freshness*+9.4
- Correctness−2.2
The parts add to +52.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.