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 18:59:16 UTC
| Metric | Tenderly | PublicNode | MEV Blocker | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 2 | 7 | 8 |
| Score | 99.4 | 98.0 | 76.9 | 57.8 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 99.98% | 99.99% | 99.93% | 73.97% |
| p50 latency | 19.3 ms | 20.7 ms | 121.3 ms | 2024.4 ms |
| p95 latency | 33.8 ms | 40.7 ms | 212.6 ms | 6590.4 ms |
| p99 latency | 75.3 ms | 97.5 ms | 235.3 ms | 9196.2 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 96.63% |
| Head lag | 0.48 blocks | 0.48 blocks | 0.40 blocks | 0.95 blocks |
| Rate limited | 0 | 0 | 3 | 6,670 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 38,833 | 39,202 | 38,778 | 8,001 |
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.4points
- Latency+1.4
- Availability−0.0
- Head freshness+0.0
- Correctness−0.0
The parts add to +1.4, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMEV Blocker
+22.5points
- Latency+22.5
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +22.5, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+41.6points
- Latency+30.0
- Availability+10.4
- Correctness+0.7
- Head freshness+0.5
The parts add to +41.6, exactly — the score is a weighted sum, so it comes apart.