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
- NodeReal
- dRPC
- Blast API
- MEV Blocker
- Merkle
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-28 14:48:01 UTC
| Metric | PublicNode | dRPC | Blast API |
|---|---|---|---|
| Rank | 2 | 4 | 5 |
| Score | 98.5 | 79.4 | 78.2 |
| Status | Excellent | Good | Good |
| Availability | 99.98% | 99.99% | 99.99% |
| p50 latency | 21.6 ms | 35.2 ms | 106.9 ms |
| p95 latency | 35.9 ms | 115.0 ms | 122.8 ms |
| p99 latency | 75.7 ms | 197.7 ms | 135.7 ms |
| Correctness | 99.98% | 100.00% | 99.99% |
| Head lag | 0.51 blocks | 0.36 blocks | 0.42 blocks |
| Rate limited | 0 | 20 | 102 |
| Unsupported | 0 | 0 | 0 |
| Samples | 9,473 | 9,246 | 9,388 |
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
+19.1points
- Latency+19.3
- Head freshness−0.2
- Correctness−0.0
- Availability−0.0
The parts add to +19.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsBlast API
+20.3points
- Latency+20.4
- Head freshness−0.1
- Availability−0.0
- Correctness−0.0
The parts add to +20.3, exactly — the score is a weighted sum, so it comes apart.