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-28 07:47:52 UTC
| Metric | Tenderly | PublicNode | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 2 | 6 | 8 |
| Score | 99.4 | 97.7 | 78.0 | 59.0 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 99.98% | 99.98% | 100.00% | 76.74% |
| p50 latency | 19.1 ms | 22.4 ms | 107.4 ms | 1326.0 ms |
| p95 latency | 32.6 ms | 41.1 ms | 193.2 ms | 7406.7 ms |
| p99 latency | 61.9 ms | 95.1 ms | 252.5 ms | 9776.0 ms |
| Correctness | 100.00% | 99.98% | 100.00% | 96.96% |
| Head lag | 0.47 blocks | 0.48 blocks | 0.53 blocks | 0.94 blocks |
| Rate limited | 0 | 0 | 6,194 | 6,616 |
| Unsupported | 0 | 0 | 80 | 0 |
| Samples | 38,574 | 38,905 | 9,087 | 7,932 |
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.7points
- Latency+1.7
- Head freshness+0.0
- Correctness+0.0
- Availability+0.0
The parts add to +1.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+21.4points
- Latency+21.4
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +21.4, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+40.4points
- Latency+30.0
- Availability+9.3
- Correctness+0.6
- Head freshness+0.5
The parts add to +40.4, exactly — the score is a weighted sum, so it comes apart.