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 21:56:05 UTC
| Metric | PublicNode | dRPC | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 2 | 3 | 5 | 6 |
| Score | 94.8 | 89.0 | 78.4 | 70.8 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 100.00% | 99.99% | 99.92% | 100.00% |
| p50 latency | 24.7 ms | 34.8 ms | 108.3 ms | 109.4 ms |
| p95 latency | 50.3 ms | 70.4 ms | 126.3 ms | 191.2 ms |
| p99 latency | 112.0 ms | 191.1 ms | 153.6 ms | 231.9 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.47 blocks | 0.36 blocks | 0.41 blocks | 0.58 blocks |
| Rate limited | 0 | 24 | 65 | 1,524 |
| Unsupported | 0 | 0 | 0 | 16 |
| Samples | 9,697 | 9,460 | 9,602 | 2,270 |
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
+5.9points
- Latency+6.0
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +5.9, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsBlast API
+16.5points
- Latency+16.5
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +16.5, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+24.1points
- Latency+23.9
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +24.1, exactly — the score is a weighted sum, so it comes apart.