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 09:13:39 UTC
| Metric | Tenderly | PublicNode | dRPC | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 2 | 3 | 8 |
| Score | 99.4 | 99.3 | 90.7 | 58.2 |
| Status | Excellent | Excellent | Excellent | Degraded |
| Availability | 99.98% | 99.98% | 99.91% | 74.93% |
| p50 latency | 19.3 ms | 18.6 ms | 34.2 ms | 2024.4 ms |
| p95 latency | 35.2 ms | 35.6 ms | 71.1 ms | 6590.4 ms |
| p99 latency | 122.4 ms | 74.9 ms | 176.6 ms | 9196.2 ms |
| Correctness | 99.99% | 100.00% | 99.99% | 96.63% |
| Head lag | 0.49 blocks | 0.48 blocks | 0.38 blocks | 0.95 blocks |
| Rate limited | 0 | 0 | 154 | 6,449 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 37,584 | 37,932 | 37,010 | 7,745 |
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.1points
- Latency+0.1
- Head freshness−0.0
- Correctness−0.0
- Availability+0.0
The parts add to +0.1, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsdRPC
+8.7points
- Latency+8.8
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.7, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+41.2points
- Latency+30.0
- Availability+10.0
- Correctness+0.7
- Head freshness+0.5
The parts add to +41.2, exactly — the score is a weighted sum, so it comes apart.