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
6h window · 6.0 hours observed · generated 2026-08-28 03:07:44 UTC
| Metric | PublicNode | Tenderly | NodeReal | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 2 | 4 | 8 |
| Score | 99.4 | 99.1 | 85.6 | 60.3 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 99.95% | 100.00% | 99.58% | 79.94% |
| p50 latency | 18.6 ms | 18.2 ms | 87.7 ms | 1326.0 ms |
| p95 latency | 30.4 ms | 31.6 ms | 99.2 ms | 7406.7 ms |
| p99 latency | 55.8 ms | 54.4 ms | 117.0 ms | 9776.0 ms |
| Correctness | 99.96% | 100.00% | 99.99% | 96.96% |
| Head lag | 0.48 blocks | 0.47 blocks | 0.34 blocks | 0.94 blocks |
| Rate limited | 0 | 0 | 0 | 1,389 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 8,388 | 8,325 | 8,155 | 1,941 |
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.3
- Availability−0.0
- Head freshness−0.0
- Correctness−0.0
The parts add to +0.2, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsNodeReal
+13.8points
- Latency+13.8
- Head freshness−0.2
- Availability+0.1
- Correctness−0.0
The parts add to +13.8, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+39.1points
- Latency+30.0
- Availability+8.0
- Correctness+0.6
- Head freshness+0.5
The parts add to +39.1, exactly — the score is a weighted sum, so it comes apart.