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-28 11:16:58 UTC
| Metric | PublicNode | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 2 | 5 | 8 |
| Score | 99.1 | 77.9 | 48.7 |
| Status | Excellent | Good | Poor |
| Availability | 100.00% | 100.00% | 23.46% |
| p50 latency | 20.6 ms | 105.4 ms | 13.4 ms |
| p95 latency | 33.7 ms | 121.6 ms | 84.5 ms |
| p99 latency | 83.0 ms | 133.7 ms | 107.2 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.44 blocks | no cohort |
| Rate limited | 0 | 56 | 0 |
| Unsupported | 0 | 0 | 49 |
| Samples | 1,623 | 1,612 | 1,611 |
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.
PublicNodevsBlast API
+21.2points
- Latency+21.3
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +21.2, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+50.4points
- Availability+29.6
- Latency+13.7
- Head freshness*+9.4
- Correctness−2.2
The parts add to +50.4, exactly — the score is a weighted sum, so it comes apart. Components marked * were measured for only one of the two; the other’s weight is spread across what it does have, which is why the two sides can carry different weights for the same row.