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 16:02:10 UTC
| Metric | PublicNode | dRPC | Blast API | MEV Blocker |
|---|---|---|---|---|
| Rank | 2 | 3 | 5 | 7 |
| Score | 95.2 | 89.0 | 78.4 | 69.5 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.99% | 99.94% | 99.99% | 99.88% |
| p50 latency | 25.3 ms | 34.4 ms | 108.7 ms | 124.8 ms |
| p95 latency | 49.4 ms | 70.3 ms | 127.4 ms | 217.2 ms |
| p99 latency | 111.5 ms | 185.3 ms | 153.4 ms | 242.4 ms |
| Correctness | 100.00% | 99.99% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.36 blocks | 0.42 blocks | 0.40 blocks |
| Rate limited | 0 | 20 | 42 | 0 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 8,234 | 8,013 | 8,143 | 8,146 |
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
+6.2points
- Latency+6.3
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +6.2, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsBlast API
+16.8points
- Latency+16.9
- 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.
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.