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
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-27 13:40:45 UTC
| Metric | PublicNode | dRPC | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 2 | 3 | 5 | 6 |
| Score | 96.4 | 88.3 | 78.7 | 70.2 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.98% | 99.94% | 99.99% | 100.00% |
| p50 latency | 23.7 ms | 33.7 ms | 107.7 ms | 108.7 ms |
| p95 latency | 46.0 ms | 73.1 ms | 124.8 ms | 200.3 ms |
| p99 latency | 125.1 ms | 173.7 ms | 153.3 ms | 230.9 ms |
| Correctness | 99.99% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.35 blocks | 0.41 blocks | 0.48 blocks |
| Rate limited | 0 | 42 | 78 | 1,449 |
| Unsupported | 0 | 0 | 0 | 18 |
| Samples | 9,286 | 9,053 | 9,208 | 2,166 |
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.
PublicNodevsdRPC
+8.1points
- Latency+8.3
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +8.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsBlast API
+17.7points
- Latency+17.8
- Head freshness−0.1
- Availability−0.0
- Correctness−0.0
The parts add to +17.7, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+26.2points
- Latency+26.2
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +26.2, exactly — the score is a weighted sum, so it comes apart.