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
- Cloudflare
- 1RPC
Side by side
1h window · 60 minutes observed · generated 2026-08-27 20:17:31 UTC
| Metric | Tenderly | PublicNode | dRPC | Blast API |
|---|---|---|---|---|
| Rank | 1 | 2 | 3 | 5 |
| Score | 99.4 | 92.9 | 86.7 | 77.8 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 100.00% | 100.00% | 99.94% | 100.00% |
| p50 latency | 17.5 ms | 25.6 ms | 35.6 ms | 108.8 ms |
| p95 latency | 31.4 ms | 56.4 ms | 78.7 ms | 125.2 ms |
| p99 latency | 61.0 ms | 119.9 ms | 195.8 ms | 153.0 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.51 blocks | 0.49 blocks | 0.34 blocks | 0.42 blocks |
| Rate limited | 0 | 0 | 5 | 16 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 1,598 | 1,624 | 1,583 | 1,604 |
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
+6.4points
- Latency+6.5
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +6.4, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsdRPC
+12.6points
- Latency+12.8
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +12.6, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+21.5points
- Latency+21.7
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +21.5, exactly — the score is a weighted sum, so it comes apart.