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 17:58:41 UTC
| Metric | PublicNode | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 2 | 5 | 8 |
| Score | 98.0 | 78.1 | 47.6 |
| Status | Excellent | Good | Poor |
| Availability | 99.99% | 99.98% | 23.12% |
| p50 latency | 22.5 ms | 108.4 ms | 14.2 ms |
| p95 latency | 38.8 ms | 125.2 ms | 93.4 ms |
| p99 latency | 75.9 ms | 142.9 ms | 164.0 ms |
| Correctness | 99.99% | 99.98% | 100.00% |
| Head lag | 0.50 blocks | 0.40 blocks | no cohort |
| Rate limited | 0 | 1 | 0 |
| Unsupported | 0 | 0 | 287 |
| Samples | 9,783 | 9,691 | 9,704 |
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
+19.8points
- Latency+19.9
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +19.8, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+50.3points
- Availability+29.7
- Latency+13.4
- Head freshness*+9.4
- Correctness−2.2
The parts add to +50.3, 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.