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 10:15:04 UTC
| Metric | Tenderly | PublicNode | Cloudflare |
|---|---|---|---|
| Rank | 1 | 2 | 9 |
| Score | 99.4 | 97.8 | 53.0 |
| Status | Excellent | Excellent | Degraded |
| Availability | 99.99% | 99.98% | 23.12% |
| p50 latency | 19.0 ms | 22.2 ms | 14.4 ms |
| p95 latency | 32.3 ms | 40.2 ms | 87.7 ms |
| p99 latency | 56.5 ms | 89.8 ms | 209.8 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.47 blocks | 0.48 blocks | no cohort |
| Rate limited | 0 | 0 | 21 |
| Unsupported | 0 | 0 | 1,106 |
| Samples | 37,691 | 38,016 | 37,694 |
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.6points
- Latency+1.6
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +1.6, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+46.4points
- Availability+29.7
- Latency+9.5
- Head freshness*+9.4
- Correctness−2.2
The parts add to +46.4, 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.