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
6h window · 6.0 hours observed · generated 2026-08-27 02:16:22 UTC
| Metric | Tenderly | PublicNode | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 2 | 6 | 8 |
| Score | 99.4 | 98.7 | 77.7 | 58.7 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 100.00% | 99.99% | 100.00% | 76.33% |
| p50 latency | 19.0 ms | 17.1 ms | 105.8 ms | 2024.4 ms |
| p95 latency | 32.3 ms | 35.4 ms | 193.2 ms | 6590.4 ms |
| p99 latency | 70.5 ms | 93.0 ms | 229.0 ms | 9196.2 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 96.63% |
| Head lag | 0.49 blocks | 0.49 blocks | 0.45 blocks | 0.95 blocks |
| Rate limited | 0 | 0 | 1,345 | 1,439 |
| Unsupported | 0 | 0 | 19 | 0 |
| Samples | 8,516 | 8,618 | 1,904 | 2,008 |
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.7points
- Latency+0.7
- Availability+0.0
- Head freshness+0.0
- Correctness+0.0
The parts add to +0.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+21.7points
- Latency+21.7
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +21.7, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+40.7points
- Latency+30.0
- Availability+9.5
- Correctness+0.7
- Head freshness+0.5
The parts add to +40.7, exactly — the score is a weighted sum, so it comes apart.