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
1h window · 60 minutes observed · generated 2026-08-28 01:23:54 UTC
| Metric | PublicNode | Blast API | Merkle | MEV Blocker |
|---|---|---|---|---|
| Rank | 1 | 5 | 6 | 7 |
| Score | 99.3 | 83.2 | 77.6 | 76.2 |
| Status | Excellent | Good | Good | Good |
| Availability | 99.94% | 99.94% | 100.00% | 99.81% |
| p50 latency | 18.9 ms | 103.4 ms | 104.4 ms | 120.4 ms |
| p95 latency | 29.2 ms | 119.2 ms | 187.6 ms | 213.9 ms |
| p99 latency | 53.6 ms | 145.3 ms | 260.1 ms | 226.8 ms |
| Correctness | 99.94% | 99.94% | 100.00% | 99.94% |
| Head lag | 0.51 blocks | 0.41 blocks | 0.62 blocks | 0.37 blocks |
| Rate limited | 0 | 21 | 250 | 0 |
| Unsupported | 0 | 0 | 3 | 0 |
| Samples | 1,629 | 1,620 | 370 | 1,620 |
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.1points
- Latency+16.3
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +16.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+21.8points
- Latency+21.7
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +21.8, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+23.1points
- Latency+23.2
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +23.1, exactly — the score is a weighted sum, so it comes apart.