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
- 1RPC
- Cloudflare
Side by side
6h window · 6.0 hours observed · generated 2026-08-28 00:24:56 UTC
| Metric | PublicNode | NodeReal | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 4 | 6 | 8 |
| Score | 97.8 | 86.4 | 78.0 | 59.4 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 100.00% | 99.97% | 100.00% | 77.43% |
| p50 latency | 21.0 ms | 87.1 ms | 106.7 ms | 1291.3 ms |
| p95 latency | 39.4 ms | 99.0 ms | 189.8 ms | 7517.0 ms |
| p99 latency | 92.9 ms | 117.0 ms | 278.7 ms | 9776.0 ms |
| Correctness | 100.00% | 99.97% | 100.00% | 97.48% |
| Head lag | 0.47 blocks | 0.35 blocks | 0.52 blocks | 0.91 blocks |
| Rate limited | 0 | 0 | 1,426 | 1,415 |
| Unsupported | 0 | 0 | 16 | 0 |
| Samples | 8,864 | 8,615 | 2,106 | 1,971 |
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.
PublicNodevsNodeReal
+11.4points
- Latency+11.6
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +11.4, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+19.8points
- Latency+19.7
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +19.8, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+38.5points
- Latency+28.4
- Availability+9.0
- Correctness+0.5
- Head freshness+0.5
The parts add to +38.5, exactly — the score is a weighted sum, so it comes apart.