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 · 2.9 days observed · generated 2026-08-27 19:24:39 UTC
| Metric | PublicNode | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 5 | 6 | 8 |
| Score | 99.4 | 84.7 | 78.4 | 62.4 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.98% | 99.98% | 99.98% | 84.99% |
| p50 latency | 19.3 ms | 105.2 ms | 107.0 ms | 225.7 ms |
| p95 latency | 35.7 ms | 122.7 ms | 195.6 ms | 4391.3 ms |
| p99 latency | 76.4 ms | 147.8 ms | 242.6 ms | 7602.5 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 97.48% |
| Head lag | 0.49 blocks | 0.42 blocks | 0.48 blocks | 0.91 blocks |
| Rate limited | 0 | 1,218 | 18,387 | 19,691 |
| Unsupported | 0 | 0 | 225 | 0 |
| Samples | 115,523 | 114,050 | 26,554 | 23,964 |
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.
PublicNodevsBlast API
+14.7points
- Latency+14.7
- Head freshness−0.1
- Availability−0.0
- Correctness−0.0
The parts add to +14.7, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+21.0points
- Latency+21.0
- Availability−0.0
- Head freshness−0.0
- Correctness−0.0
The parts add to +21.0, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+37.0points
- Latency+30.0
- Availability+6.0
- Correctness+0.5
- Head freshness+0.5
The parts add to +37.0, exactly — the score is a weighted sum, so it comes apart.