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-27 14:21:35 UTC
| Metric | Tenderly | PublicNode | Cloudflare |
|---|---|---|---|
| Rank | 1 | 2 | 9 |
| Score | 99.4 | 98.6 | 53.3 |
| Status | Excellent | Excellent | Degraded |
| Availability | 99.98% | 99.97% | 23.15% |
| p50 latency | 19.2 ms | 19.5 ms | 15.0 ms |
| p95 latency | 34.1 ms | 37.8 ms | 86.6 ms |
| p99 latency | 76.9 ms | 88.2 ms | 224.2 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.49 blocks | no cohort |
| Rate limited | 0 | 0 | 55 |
| Unsupported | 0 | 0 | 1,113 |
| Samples | 37,802 | 38,164 | 37,797 |
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
+0.8points
- Latency+0.8
- Availability+0.0
- Head freshness−0.0
- Correctness+0.0
The parts add to +0.8, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+46.1points
- Availability+29.7
- Head freshness*+9.4
- Latency+9.2
- Correctness−2.2
The parts add to +46.1, 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.