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
- PublicNode
- Tenderly
- dRPC
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- 1RPC
- Cloudflare
Side by side
30d window · 2.5 days observed · generated 2026-08-27 09:49:05 UTC
| Metric | Tenderly | dRPC | Merkle | MEV Blocker |
|---|---|---|---|---|
| Rank | 2 | 3 | 6 | 7 |
| Score | 95.3 | 92.6 | 78.6 | 77.8 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 99.96% | 99.93% | 99.98% | 99.89% |
| p50 latency | 19.8 ms | 33.8 ms | 106.4 ms | 118.6 ms |
| p95 latency | 58.7 ms | 71.9 ms | 196.0 ms | 209.3 ms |
| p99 latency | 812.7 ms | 167.7 ms | 243.1 ms | 232.6 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 99.99% |
| Head lag | 0.50 blocks | 0.36 blocks | 0.48 blocks | 0.40 blocks |
| Rate limited | 0 | 615 | 15,937 | 3 |
| Unsupported | 0 | 0 | 197 | 0 |
| Samples | 99,074 | 97,446 | 22,941 | 98,904 |
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.
TenderlyvsdRPC
+2.7points
- Latency+2.8
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +2.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+16.6points
- Latency+16.7
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +16.6, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMEV Blocker
+17.5points
- Latency+17.6
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +17.5, exactly — the score is a weighted sum, so it comes apart.