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
7d window · 2.8 days observed · generated 2026-08-27 16:07:55 UTC
| Metric | PublicNode | Tenderly | Merkle | MEV Blocker |
|---|---|---|---|---|
| Rank | 1 | 2 | 6 | 7 |
| Score | 99.4 | 96.4 | 78.5 | 77.6 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 99.98% | 99.96% | 99.98% | 99.89% |
| p50 latency | 19.0 ms | 19.8 ms | 106.7 ms | 119.0 ms |
| p95 latency | 34.9 ms | 51.9 ms | 196.0 ms | 210.0 ms |
| p99 latency | 74.4 ms | 758.7 ms | 243.3 ms | 233.8 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 99.99% |
| Head lag | 0.49 blocks | 0.50 blocks | 0.48 blocks | 0.40 blocks |
| Rate limited | 0 | 0 | 17,568 | 3 |
| Unsupported | 0 | 0 | 216 | 0 |
| Samples | 110,158 | 109,320 | 25,325 | 109,119 |
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 PublicNode, the highest scorer of those selected.
PublicNodevsTenderly
+3.0points
- Latency+3.0
- Head freshness+0.0
- Availability+0.0
- Correctness−0.0
The parts add to +3.0, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+20.9points
- Latency+21.0
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +20.9, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+21.8points
- Latency+21.9
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +21.8, exactly — the score is a weighted sum, so it comes apart.