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 02:05:59 UTC
| Metric | PublicNode | Tenderly | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 2 | 6 | 8 |
| Score | 99.4 | 99.3 | 77.8 | 60.3 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 99.99% | 100.00% | 100.00% | 79.94% |
| p50 latency | 19.1 ms | 18.5 ms | 106.4 ms | 1326.0 ms |
| p95 latency | 31.1 ms | 31.9 ms | 192.9 ms | 7406.7 ms |
| p99 latency | 63.3 ms | 54.8 ms | 281.6 ms | 9776.0 ms |
| Correctness | 99.99% | 100.00% | 100.00% | 96.96% |
| Head lag | 0.48 blocks | 0.46 blocks | 0.46 blocks | 0.94 blocks |
| Rate limited | 0 | 0 | 1,342 | 1,388 |
| Unsupported | 0 | 0 | 17 | 0 |
| Samples | 8,332 | 8,266 | 1,967 | 1,942 |
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.
PublicNodevsMerkle
+21.6points
- Latency+21.6
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +21.6, 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.