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
6h window · 6.0 hours observed · generated 2026-08-27 23:23:57 UTC
| Metric | Tenderly | PublicNode | dRPC | Merkle |
|---|---|---|---|---|
| Rank | 1 | 2 | 3 | 6 |
| Score | 99.4 | 96.2 | 88.7 | 71.0 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 100.00% | 100.00% | 99.99% | 100.00% |
| p50 latency | 18.7 ms | 22.7 ms | 33.6 ms | 107.6 ms |
| p95 latency | 32.2 ms | 43.8 ms | 68.0 ms | 187.6 ms |
| p99 latency | 53.9 ms | 100.2 ms | 189.9 ms | 236.0 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.47 blocks | 0.47 blocks | 0.36 blocks | 0.51 blocks |
| Rate limited | 0 | 0 | 14 | 1,407 |
| Unsupported | 0 | 0 | 0 | 15 |
| Samples | 8,746 | 8,830 | 8,605 | 2,094 |
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.2points
- Latency+3.2
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +3.2, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsdRPC
+10.7points
- Latency+10.9
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +10.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+28.4points
- Latency+28.4
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +28.4, exactly — the score is a weighted sum, so it comes apart.