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-28 00:15:23 UTC
| Metric | Tenderly | PublicNode | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 1 | 2 | 5 | 6 |
| Score | 99.4 | 97.8 | 83.6 | 78.1 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 100.00% | 100.00% | 99.96% | 100.00% |
| p50 latency | 18.3 ms | 21.1 ms | 105.7 ms | 106.9 ms |
| p95 latency | 31.7 ms | 39.8 ms | 122.8 ms | 187.6 ms |
| p99 latency | 54.2 ms | 93.6 ms | 150.5 ms | 230.5 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.46 blocks | 0.48 blocks | 0.41 blocks | 0.52 blocks |
| Rate limited | 0 | 0 | 19 | 1,395 |
| Unsupported | 0 | 0 | 0 | 16 |
| Samples | 8,525 | 8,600 | 8,508 | 2,051 |
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
+1.7points
- Latency+1.6
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +1.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+15.9points
- Latency+15.9
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +15.9, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+21.4points
- Latency+21.3
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +21.4, exactly — the score is a weighted sum, so it comes apart.