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
- Blast API
- dRPC
- Merkle
- MEV Blocker
- Cloudflare
- 1RPC
Side by side
1h window · 60 minutes observed · generated 2026-08-28 09:59:42 UTC
| Metric | PublicNode | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 2 | 4 | 8 |
| Score | 99.3 | 77.9 | 48.2 |
| Status | Excellent | Good | Poor |
| Availability | 100.00% | 100.00% | 23.13% |
| p50 latency | 21.1 ms | 106.2 ms | 14.0 ms |
| p95 latency | 33.5 ms | 120.8 ms | 86.1 ms |
| p99 latency | 60.0 ms | 130.6 ms | 110.4 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.52 blocks | 0.42 blocks | no cohort |
| Rate limited | 0 | 19 | 0 |
| Unsupported | 0 | 0 | 48 |
| Samples | 1,621 | 1,613 | 1,608 |
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.4points
- Latency+21.5
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +21.4, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+51.1points
- Availability+29.7
- Latency+14.2
- Head freshness*+9.4
- Correctness−2.2
The parts add to +51.1, 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.