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
- PublicNode
- Tenderly
- dRPC
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- 1RPC
- Cloudflare
Side by side
1h window · 60 minutes observed · generated 2026-08-28 00:24:29 UTC
| Metric | Tenderly | 1RPC | Cloudflare |
|---|---|---|---|
| Rank | 2 | 8 | 9 |
| Score | 99.2 | 60.3 | 56.3 |
| Status | Excellent | Degraded | Degraded |
| Availability | 100.00% | 79.64% | 23.46% |
| p50 latency | 17.1 ms | 1299.9 ms | 12.6 ms |
| p95 latency | 30.9 ms | 7517.0 ms | 64.3 ms |
| p99 latency | 56.7 ms | 9776.0 ms | 124.5 ms |
| Correctness | 100.00% | 97.76% | 100.00% |
| Head lag | 0.46 blocks | 0.92 blocks | no cohort |
| Rate limited | 0 | 180 | 0 |
| Unsupported | 0 | 0 | 47 |
| Samples | 1,614 | 537 | 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.
Tenderlyvs1RPC
+38.8points
- Latency+29.7
- Availability+8.1
- Head freshness+0.5
- Correctness+0.4
The parts add to +38.8, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+42.8points
- Availability+29.6
- Head freshness*+9.4
- Latency+6.1
- Correctness−2.2
The parts add to +42.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.