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 12:03:59 UTC
| Metric | Tenderly | PublicNode | dRPC | Merkle |
|---|---|---|---|---|
| Rank | 1 | 2 | 3 | 6 |
| Score | 99.4 | 95.7 | 85.2 | 69.9 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 100.00% | 99.94% | 99.94% | 100.00% |
| p50 latency | 20.9 ms | 23.8 ms | 34.4 ms | 112.0 ms |
| p95 latency | 33.7 ms | 47.3 ms | 87.1 ms | 209.2 ms |
| p99 latency | 58.1 ms | 95.7 ms | 190.8 ms | 407.4 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.46 blocks | 0.51 blocks | 0.39 blocks | 0.38 blocks |
| Rate limited | 0 | 0 | 5 | 254 |
| Unsupported | 0 | 0 | 0 | 1 |
| Samples | 1,621 | 1,634 | 1,589 | 354 |
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
+3.7points
- Latency+3.6
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +3.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsdRPC
+14.2points
- Latency+14.3
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +14.2, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+29.5points
- Latency+29.6
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +29.5, exactly — the score is a weighted sum, so it comes apart.