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
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-27 09:18:22 UTC
| Metric | PublicNode | Tenderly | dRPC | Merkle |
|---|---|---|---|---|
| Rank | 1 | 2 | 3 | 6 |
| Score | 99.4 | 99.1 | 88.3 | 69.9 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 99.99% | 99.98% | 99.93% | 100.00% |
| p50 latency | 19.1 ms | 18.5 ms | 31.4 ms | 105.3 ms |
| p95 latency | 31.8 ms | 32.7 ms | 64.2 ms | 196.0 ms |
| p99 latency | 67.3 ms | 105.1 ms | 159.2 ms | 228.8 ms |
| Correctness | 100.00% | 100.00% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.48 blocks | 0.36 blocks | 0.61 blocks |
| Rate limited | 0 | 0 | 39 | 1,358 |
| Unsupported | 0 | 0 | 0 | 14 |
| Samples | 8,658 | 8,582 | 8,445 | 1,968 |
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.3points
- Latency+0.3
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +0.3, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsdRPC
+11.1points
- Latency+11.2
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +11.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+29.5points
- Latency+29.3
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +29.5, exactly — the score is a weighted sum, so it comes apart.