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 10:06:19 UTC
| Metric | Tenderly | PublicNode | dRPC | Blast API |
|---|---|---|---|---|
| Rank | 1 | 2 | 3 | 5 |
| Score | 99.4 | 99.1 | 87.8 | 78.2 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 99.93% | 99.98% | 99.94% | 99.99% |
| p50 latency | 19.1 ms | 20.0 ms | 32.0 ms | 105.6 ms |
| p95 latency | 34.1 ms | 35.1 ms | 69.3 ms | 121.9 ms |
| p99 latency | 138.3 ms | 84.9 ms | 160.5 ms | 150.6 ms |
| Correctness | 100.00% | 99.99% | 99.99% | 99.99% |
| Head lag | 0.49 blocks | 0.49 blocks | 0.35 blocks | 0.41 blocks |
| Rate limited | 0 | 0 | 37 | 132 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 8,256 | 8,324 | 8,128 | 8,251 |
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
+0.3points
- Latency+0.3
- Availability−0.0
- Head freshness+0.0
- Correctness+0.0
The parts add to +0.3, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsdRPC
+11.6points
- Latency+11.7
- Head freshness−0.2
- Availability−0.0
- Correctness+0.0
The parts add to +11.6, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+21.1points
- Latency+21.2
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +21.1, exactly — the score is a weighted sum, so it comes apart.