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
1h window · 60 minutes observed · generated 2026-08-28 00:19:58 UTC
| Metric | PublicNode | Tenderly | dRPC | Merkle |
|---|---|---|---|---|
| Rank | 1 | 2 | 3 | 6 |
| Score | 99.4 | 99.2 | 91.4 | 77.8 |
| Status | Excellent | Excellent | Excellent | Good |
| Availability | 100.00% | 100.00% | 100.00% | 100.00% |
| p50 latency | 17.6 ms | 17.2 ms | 31.7 ms | 107.0 ms |
| p95 latency | 29.7 ms | 30.8 ms | 61.4 ms | 201.7 ms |
| p99 latency | 66.7 ms | 54.4 ms | 148.1 ms | 301.3 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.47 blocks | 0.46 blocks | 0.39 blocks | 0.35 blocks |
| Rate limited | 0 | 0 | 1 | 258 |
| Unsupported | 0 | 0 | 0 | 5 |
| Samples | 1,634 | 1,623 | 1,581 | 388 |
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
+0.2points
- Latency+0.2
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +0.2, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsdRPC
+8.1points
- Latency+8.2
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+21.7points
- Latency+21.8
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +21.7, exactly — the score is a weighted sum, so it comes apart.