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
- Merkle
- MEV Blocker
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-28 13:15:43 UTC
| Metric | PublicNode | dRPC | Blast API |
|---|---|---|---|
| Rank | 2 | 4 | 5 |
| Score | 98.8 | 78.7 | 78.1 |
| Status | Excellent | Good | Good |
| Availability | 99.98% | 99.96% | 99.96% |
| p50 latency | 21.2 ms | 33.9 ms | 106.1 ms |
| p95 latency | 34.7 ms | 117.9 ms | 121.6 ms |
| p99 latency | 70.2 ms | 199.4 ms | 133.4 ms |
| Correctness | 99.98% | 99.99% | 99.98% |
| Head lag | 0.49 blocks | 0.37 blocks | 0.41 blocks |
| Rate limited | 0 | 18 | 175 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,603 | 8,386 | 8,535 |
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
+20.1points
- Latency+20.3
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +20.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsBlast API
+20.7points
- Latency+20.8
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +20.7, exactly — the score is a weighted sum, so it comes apart.