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
6h window · 6.0 hours observed · generated 2026-08-28 03:30:33 UTC
| Metric | Tenderly | NodeReal | Cloudflare |
|---|---|---|---|
| Rank | 2 | 4 | 9 |
| Score | 99.1 | 85.6 | 55.8 |
| Status | Excellent | Good | Degraded |
| Availability | 100.00% | 99.61% | 23.11% |
| p50 latency | 18.5 ms | 87.6 ms | 12.4 ms |
| p95 latency | 31.7 ms | 99.2 ms | 66.0 ms |
| p99 latency | 54.5 ms | 116.3 ms | 131.7 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.47 blocks | 0.34 blocks | no cohort |
| Rate limited | 0 | 0 | 15 |
| Unsupported | 0 | 0 | 261 |
| Samples | 8,938 | 8,757 | 8,933 |
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
+13.5points
- Latency+13.5
- Availability+0.2
- Head freshness−0.2
- Correctness+0.0
The parts add to +13.5, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+43.3points
- Availability+29.7
- Head freshness*+9.4
- Latency+6.4
- Correctness−2.2
The parts add to +43.3, 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.