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
30d window · 2.9 days observed · generated 2026-08-27 19:11:17 UTC
| Metric | PublicNode | Tenderly | NodeReal | Merkle |
|---|---|---|---|---|
| Rank | 1 | 2 | 4 | 6 |
| Score | 99.4 | 96.9 | 87.5 | 78.4 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 99.98% | 99.96% | 99.84% | 99.98% |
| p50 latency | 19.3 ms | 19.8 ms | 87.4 ms | 107.0 ms |
| p95 latency | 35.6 ms | 49.4 ms | 100.0 ms | 195.7 ms |
| p99 latency | 76.4 ms | 729.3 ms | 125.9 ms | 242.7 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.50 blocks | 0.34 blocks | 0.48 blocks |
| Rate limited | 0 | 0 | 0 | 18,337 |
| Unsupported | 0 | 0 | 0 | 224 |
| Samples | 115,160 | 114,272 | 112,346 | 26,484 |
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
+2.5points
- Latency+2.5
- Head freshness+0.0
- Availability+0.0
- Correctness−0.0
The parts add to +2.5, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsNodeReal
+11.9points
- Latency+12.0
- Head freshness−0.2
- Availability+0.1
- Correctness−0.0
The parts add to +11.9, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+21.0points
- Latency+21.0
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +21.0, exactly — the score is a weighted sum, so it comes apart.