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 22:19:37 UTC
| Metric | PublicNode | Blast API | Merkle | MEV Blocker |
|---|---|---|---|---|
| Rank | 2 | 5 | 6 | 7 |
| Score | 95.2 | 78.4 | 70.8 | 69.5 |
| Status | Excellent | Good | Degraded | Degraded |
| Availability | 100.00% | 99.92% | 100.00% | 99.94% |
| p50 latency | 24.3 ms | 107.9 ms | 109.2 ms | 124.3 ms |
| p95 latency | 48.4 ms | 125.5 ms | 191.2 ms | 216.4 ms |
| p99 latency | 108.2 ms | 152.4 ms | 231.9 ms | 239.1 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 99.98% |
| Head lag | 0.47 blocks | 0.41 blocks | 0.57 blocks | 0.39 blocks |
| Rate limited | 0 | 44 | 1,384 | 0 |
| Unsupported | 0 | 0 | 14 | 0 |
| Samples | 8,706 | 8,618 | 2,055 | 8,618 |
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
+16.8points
- Latency+16.8
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +16.8, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+24.4points
- Latency+24.3
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +24.4, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+25.7points
- Latency+25.8
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +25.7, exactly — the score is a weighted sum, so it comes apart.