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
24h window · 24 hours observed · generated 2026-08-27 07:27:49 UTC
| Metric | PublicNode | Tenderly | NodeReal | Merkle |
|---|---|---|---|---|
| Rank | 1 | 2 | 4 | 6 |
| Score | 99.4 | 99.4 | 86.4 | 77.9 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 99.97% | 99.98% | 100.00% | 100.00% |
| p50 latency | 18.3 ms | 19.5 ms | 87.1 ms | 107.3 ms |
| p95 latency | 35.3 ms | 35.4 ms | 100.3 ms | 193.3 ms |
| p99 latency | 74.1 ms | 128.1 ms | 129.3 ms | 240.0 ms |
| Correctness | 100.00% | 99.99% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.49 blocks | 0.34 blocks | 0.49 blocks |
| Rate limited | 0 | 0 | 0 | 6,067 |
| Unsupported | 0 | 0 | 0 | 73 |
| Samples | 38,314 | 37,975 | 37,392 | 8,676 |
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.0points
- Latency+0.0
- Head freshness+0.0
- Availability−0.0
- Correctness+0.0
The parts add to +0.0, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsNodeReal
+13.0points
- Latency+13.2
- Head freshness−0.2
- Availability−0.0
- Correctness+0.0
The parts add to +13.0, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+21.5points
- Latency+21.5
- Availability−0.0
- Head freshness+0.0
- Correctness−0.0
The parts add to +21.5, exactly — the score is a weighted sum, so it comes apart.