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
- MEV Blocker
- Merkle
- Cloudflare
- 1RPC
Side by side
1h window · 60 minutes observed · generated 2026-08-28 14:25:50 UTC
| Metric | Tenderly | PublicNode | dRPC |
|---|---|---|---|
| Rank | 1 | 2 | 3 |
| Score | 99.4 | 98.1 | 85.7 |
| Status | Excellent | Excellent | Good |
| Availability | 100.00% | 100.00% | 100.00% |
| p50 latency | 19.5 ms | 22.7 ms | 37.9 ms |
| p95 latency | 34.1 ms | 38.4 ms | 82.6 ms |
| p99 latency | 89.2 ms | 78.0 ms | 186.0 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.55 blocks | 0.37 blocks |
| Rate limited | 0 | 0 | 4 |
| Unsupported | 0 | 0 | 0 |
| Samples | 1,622 | 1,619 | 1,586 |
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.3points
- Latency+1.2
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +1.3, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsdRPC
+13.7points
- Latency+13.8
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +13.7, exactly — the score is a weighted sum, so it comes apart.