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
1h window · 60 minutes observed · generated 2026-08-28 00:00:53 UTC
| Metric | PublicNode | dRPC | Blast API | MEV Blocker |
|---|---|---|---|---|
| Rank | 1 | 3 | 5 | 7 |
| Score | 99.4 | 91.5 | 83.4 | 76.8 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 100.00% | 100.00% | 100.00% | 100.00% |
| p50 latency | 17.8 ms | 31.8 ms | 103.5 ms | 120.3 ms |
| p95 latency | 29.4 ms | 59.9 ms | 119.2 ms | 213.5 ms |
| p99 latency | 56.8 ms | 147.6 ms | 146.5 ms | 225.4 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.39 blocks | 0.45 blocks | 0.36 blocks |
| Rate limited | 0 | 2 | 0 | 0 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 1,639 | 1,577 | 1,608 | 1,606 |
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
+7.9points
- Latency+8.0
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +7.9, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsBlast API
+16.0points
- Latency+16.0
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +16.0, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+22.7points
- Latency+22.8
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +22.7, exactly — the score is a weighted sum, so it comes apart.