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
7d window · 3.2 days observed · generated 2026-08-28 00:24:55 UTC
| Metric | PublicNode | Tenderly | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 2 | 6 | 8 |
| Score | 99.4 | 97.4 | 78.3 | 61.8 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 99.98% | 99.97% | 99.98% | 83.55% |
| p50 latency | 19.4 ms | 19.7 ms | 106.9 ms | 262.2 ms |
| p95 latency | 35.8 ms | 46.2 ms | 195.0 ms | 4929.2 ms |
| p99 latency | 77.4 ms | 686.1 ms | 243.2 ms | 8455.9 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 97.47% |
| Head lag | 0.49 blocks | 0.50 blocks | 0.49 blocks | 0.91 blocks |
| Rate limited | 0 | 0 | 19,710 | 20,988 |
| Unsupported | 0 | 0 | 239 | 0 |
| Samples | 123,715 | 122,752 | 28,512 | 25,798 |
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.0points
- Latency+1.9
- Head freshness+0.0
- Availability+0.0
- Correctness−0.0
The parts add to +2.0, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+21.1points
- Latency+21.1
- Availability−0.0
- Correctness−0.0
- Head freshness+0.0
The parts add to +21.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+37.6points
- Latency+30.0
- Availability+6.6
- Correctness+0.5
- Head freshness+0.5
The parts add to +37.6, exactly — the score is a weighted sum, so it comes apart.