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
1h window · 60 minutes observed · generated 2026-08-27 20:20:10 UTC
| Metric | PublicNode | dRPC | Blast API |
|---|---|---|---|
| Rank | 2 | 3 | 5 |
| Score | 93.0 | 86.2 | 77.9 |
| Status | Excellent | Good | Good |
| Availability | 100.00% | 99.94% | 100.00% |
| p50 latency | 25.5 ms | 35.6 ms | 108.8 ms |
| p95 latency | 56.0 ms | 81.0 ms | 124.9 ms |
| p99 latency | 121.4 ms | 195.8 ms | 152.8 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.34 blocks | 0.41 blocks |
| Rate limited | 0 | 7 | 16 |
| Unsupported | 0 | 0 | 0 |
| Samples | 1,614 | 1,567 | 1,594 |
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.8points
- Latency+6.9
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +6.8, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsBlast API
+15.0points
- Latency+15.1
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +15.0, exactly — the score is a weighted sum, so it comes apart.