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:47:54 UTC
| Metric | Tenderly | Blast API | Merkle | MEV Blocker |
|---|---|---|---|---|
| Rank | 1 | 5 | 6 | 7 |
| Score | 99.4 | 84.0 | 77.7 | 76.9 |
| Status | Excellent | Good | Good | Good |
| Availability | 100.00% | 99.99% | 100.00% | 99.96% |
| p50 latency | 18.9 ms | 103.9 ms | 105.7 ms | 118.0 ms |
| p95 latency | 32.4 ms | 118.2 ms | 196.0 ms | 209.3 ms |
| p99 latency | 70.1 ms | 141.7 ms | 229.0 ms | 229.6 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.42 blocks | 0.46 blocks | 0.40 blocks |
| Rate limited | 0 | 71 | 1,466 | 2 |
| Unsupported | 0 | 0 | 21 | 0 |
| Samples | 9,370 | 9,331 | 2,070 | 9,380 |
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.
TenderlyvsBlast API
+15.4points
- Latency+15.5
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +15.4, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+21.7points
- Latency+21.8
- 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.
TenderlyvsMEV Blocker
+22.5points
- Latency+22.6
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +22.5, exactly — the score is a weighted sum, so it comes apart.