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-28 23:00:11 UTC
| Metric | PublicNode | NodeReal | Blast API |
|---|---|---|---|
| Rank | 2 | 4 | 5 |
| Score | 98.1 | 81.8 | 78.1 |
| Status | Excellent | Good | Good |
| Availability | 99.99% | 100.00% | 99.99% |
| p50 latency | 21.5 ms | 87.0 ms | 106.6 ms |
| p95 latency | 36.5 ms | 99.2 ms | 122.8 ms |
| p99 latency | 78.1 ms | 117.3 ms | 138.8 ms |
| Correctness | 99.99% | 100.00% | 99.99% |
| Head lag | 0.50 blocks | 0.34 blocks | 0.44 blocks |
| Rate limited | 0 | 0 | 11 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,161 | 7,958 | 8,108 |
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.
PublicNodevsNodeReal
+16.4points
- Latency+16.6
- Head freshness−0.2
- Availability−0.0
- Correctness−0.0
The parts add to +16.4, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsBlast API
+20.0points
- Latency+20.1
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +20.0, exactly — the score is a weighted sum, so it comes apart.